Mac Mini Behind Router

My current network setup is a modem from Time Warner with 2 separate ethernet ports. 1 Port is assigned to our Lynksis router which gives out DCHP addresses to the network. The Mac Mini is on a separate port of the modem and has a public static IP address. Is there any way to set up the Mini Server to have a local address as well as be visible publicly? I would like to be able to achieve network speed to the server as well as have access to it from the outside for hosting email and other services.
Any help would be greatly appreciated.
Thanks.

Your gateway gets the static IP, and gets configured to port-forward specific traffic to a private static IP address on your server; get the LAN into a subnet in the 172.16.0.0/12 or 10.0.0.0/8 private blocks (to make VPNs easier; it's really ugly to have both ends of a VPN in 192.168.0.0/16 or 192.168.1.0/16 or one of the other common subnets.
This presumes you don't have enough public static addresses to pass those out to all the hosts.
Read up on "port forwarding" and read the documentation on whichever of the gazillion different Linksys boxes this is, and definitely look around around for a server-grade gateway (firewall, NAT, VPN end-point, etc) from Linksys or from one of the other vendors (if this is one of the low-end Linksys boxes).
[More reading|http://labs.hoffmanlabs.com/node/275].

Similar Messages

Mac Mini vs router + server

Hi,
I'm doing some research about the benefits or the Mac Mini with server.
What im aiming for is buying a Mac mini, install OS X Server on it. Connect it directly to the modem and use the Mac mini as a wifi router with built in server options. Integrate it with a firewall and VPN with my devices.
Id like to have some opinion from the hardcore apple users.
Is the wireless card strong enough to compete with a router?
Would the security a router provides be stronger and safer than a server with additional firewall and antivirus software?
Is it possible to tunnel my VPN connection from my iDevices from outside the local network (like 4LTE, 3G, Wifi at a friends house) to my VPN server at home, continued by tunneling my VPN from the server at home (Mac Mini) to my paid VPN Server (company)
Would it be possible to connect with my iDevices to my Mac Mini and use it as a regular computer, even outside of the home network?
I assume that I can externally expand the storage capacity by plugging in an external HDD through USB or Thunderbolt, is this correct?
Can I setup Time Machine on the server to save backups from my MacBooks?
I want to setup my own cloud so I have all my photos, documents and videos in one place, compared to limited storage (unless paid) on Cloud companies. Is it possible to setup my iDevices so they store new pictures and videos in my cloud at home, instead of the iCloud Dive space
What I would like to accomplish with this is creating a single device that provides several purposes related with my iDevices, in and outside it's network.
Including:
Serve as a Wifi router to provide the SSID
VPN service (within and from outside the SSID)
Cloud Storage available to my iDevices (within and from outside the SSID)
Time Machine
Is all of this realistic? What are the downsides of setting it up like this, vs a router with a server connected to it.
Thanks in advance
Mark

I'll bite.
I will preface this by saying that I am not a fan of OS X as a NAT device. Apple removed all easy configuration back with the release of 10.7. While it still can be done, you really must have a passion for tinkering to make it work. Now, there is IceFloor. If you are considering using the Mac as the NAT device, then IceFloor can ease the pain of configuration. That being said, I still believe that it is best to isolate and separate your devices into distinct roles. A firewall is designed to be a firewall. It does that job and does it solely well. OS X Server is a general purpose server. It is capable of many things but it does not necessarily excel at being a NAT appliance. Also, firewalls are generally easier to setup and configure than OS X Server when considering NAT roles and policies.
All that being said, OS X Server is a capable and very affordable solution that works exceptionally well for all Apple environments.
Before continuing, I should point out that you should investigate your residential ISP's policies regarding hosting services. If you are in the US, there are many ISPs that block http and smtp on residential services. Some block additional ports. Plus, if you have a dynamic service then you likely should be looking at dynamic DNS to ensure that you can always reach your server. If you have a dynamic service, this is all the more reason to put OS X Server behind a firewall appliance. OS X, especially for services like Open Directory, Profile Manager, and others, really only work properly when the server has a fixed IP address. If this is not possible on primary route connection, you will struggle with certain services. Placing the device on a LAN and allowing a firewall to handle everything else is a much better solution.
1: Is the wireless card strong enough to compete with a router?
Get a $99 airport express. You will be happier.
2: Would the security a router provides be stronger and safer than a server with additional firewall and antivirus software?
This is arguing between 6 in one hand and a half dozen in the other. Two identically configured solutions result in the same level of security. Or lack thereof. The nice part about a firewall is that it assumes everything is bad unless you explicitly allow it. With OS X, it generally thinks everything is good unless you explicitly deny it. (this is a gross simplification of the situation so you weigh your options) A firewall appliance will likely provide additional services that are easy to configure and also provide more logging and reporting regarding what is happening. Again, I am partial to the firewall.
3: Is it possible to tunnel my VPN connection from my iDevices from outside the local network (like 4LTE, 3G, Wifi at a friends house) to my VPN server at home, continued by tunneling my VPN from the server at home (Mac Mini) to my paid VPN Server (company)
So, you want to be out of your house, create a VPN into your home network, and then be able to traverse to your office? Why not connect direct to the office? How does routing through your home benefit the situation? Regardless, anything is possible. But, the tunnel from your home to the office would need to be built and persistent. Thus, you can remote into your home network. Let's say your home network is 10.0.20.0/24 and your office is 172.16.0.1/24. Your home would build a tunnel to the office. Then the VPN service would advertise the 172.16.0.1/24 route (as well as the 10.0.20.0/24 network) to the client devices, allowing them to access resources on both networks. Then you can request resources on your company network because the route will be provided by the VPN connection.
4: Would it be possible to connect with my iDevices to my Mac Mini and use it as a regular computer, even outside of the home network?
This is another one of my dislikes. Everything has a role and a purpose. Your server is a server, not a workstations. Workstations get rebooted, generally are updated more frequently, run various software and perform varied tasks. Servers have a narrower purpose. I am not a fan of using a server as a workstation. This gets particularly muddy of you are doing file services or need services than must loop back to the server itself. Can you use the server as a workstation? Sure, what is stopping you. Should you? In my opinion, no. Let a Firewall be a firewall. Let a server be a server. Let a workstation be a workstation. Together, they will live in harmony.
5: I assume that I can externally expand the storage capacity by plugging in an external HDD through USB or Thunderbolt, is this correct?
Yes. Thunderbolt is fast. USB 3 is not terrible. Stay away from Firewire at this point. Get something that supports RAID. Remember, RAID is not backup. All it does is provide drive level redundancy.
6: Can I setup Time Machine on the server to save backups from my MacBooks?
Yes. OS X Server provides Time Machine server. Figure out what you want to backup (data only or the whole drive) and then calculate a capacity requirement. While not as critical as in the past, I still prefer isolating Time Machine backup volumes. I tend not to storage any other data there.
7: I want to setup my own cloud so I have all my photos, documents and videos in one place, compared to limited storage (unless paid) on Cloud companies. Is it possible to setup my iDevices so they store new pictures and videos in my cloud at home, instead of the iCloud Dive space
Hmm. So, ah. No. Yes. Well not really. Not easy like iCloud. That is integrated and generally "just works." There is nothing stopping you from manually storing all your content in this location and then sharing it out. But there is no way to redirect an image from your phone to magically appear on your own server. Unless you are using photo stream and you have iPhoto set up on the server. But then we get back to the workstation vs server argument I just had with myself and around I go in a circle. You can create your own storage. But there is effort here. You have WebDAV, Portfolio/Cumulus, and other services and solutions.
So to wrap up...
Serve as a Wifi router to provide the SSID
VPN service (within and from outside the SSID)
Cloud Storage available to my iDevices (within and from outside the SSID)
Time Machine
Using the internal WiFi will only frustrate you. Get an access point and you will get better coverage, better control, and more features. OS X supports two VPN types. PPTP and L2TP. Both will work through a NAT. Both are natively supported on OS X and iOS. Building your own Cloud is the most daunting and vague area. And Time Machine is cake.
Is all of this realistic? What are the downsides of setting it up like this, vs a router with a server connected to it.
Is building a server sitting on a LAN with a firewall realistic? It is done everyday and nearly every network is doing the same thing. All of the above is my take on the topic but I focus on businesses and organizations. These types of setups get a firewall. Then the server is protected behind an umbrella of protection. If you go the mini alone route, you have lower cost by higher difficulty. If you get the individual pieces then you have higher cost but simpler setup and management.
Hope this helps. Once again, too much information. Had a moment of quiet.
Reid
Apple Consultants Network
Author "Yosemite Server – Foundation Services" :: Exclusively available in Apple's iBooks Store
Author "Mavericks Server – Foundation Services" :: Exclusively available in Apple's iBooks Store
Author "Mavericks Server – Control and Collaboration" :: Exclusively available in Apple's iBooks Store

New Mac Mini Tiscali Router HELP!!!

Hi
My Dad has just bought his first Mac - a Mac Mini, presumably running Tiger. He is with Tiscali and had a USB modem (Sagem), but went to buy an ethernet adaptor today and the guy in the shop told him it was an old modem and sold him this new Router - an Edimax AR-7084gA. Consequently, any support I could find for Tiscali is now now good as it was concerning the Sagem modem. My Dad's getting very frustrated and I've tried to get him connected, but I'm doing it by phone as he lives miles away and I'm at work and I'm about to cry!!! I feel somewhat responsible as I told him to buy a Mac!
Please can someone tell me what to tell him to do over the phone - even the most obvious stuff. In the Network bit, he's selected the 'Built in Ethernet' option and in TCP/IP he's selected the Using DHCP etc and all the IP addresses and router things have come up, but he can't get any further. Are we doing something really stupid? Do we have to put in phone numbers or anything? The install disc for the router doesn't seem to work but I don't think he needs to do that anyway, as it's obviously seeing the router. It's really hard for me because I'm using an older OS than him and my windows don't come up with the same things.
I've used Macs for years and have set them all up in our office, but it's always been really easy.
Please, please help - no matter how obvious you think you're being, I'm sure it will help.

I would support the move away from the USB modem, but the new one needs some setting up. I just checked and you might like to look at this page, if you have not already done so.
I am pretty certain that all of these modem/routers have a configuration page hard wired into the device and this needs to be accessed using a browser. It may also be a good idea to try with an Ethernet cable before the WiFi as this is one element out of the equation.
Check with the manual, but the access to the configuration page is probably either at 10.0.0.2 (that is all that you need to put in the browser URL space) or at a number beginning with 192..
The 10 series or the 192 series are healthy: you are on the way. A series beginning 168 means that the IP number is self-assigned.
What you have here, "Built in Ethernet' option and in TCP/IP he's selected the Using DHCP etc and all the IP addresses and router things have come up, but he can't get any further" is right.
But it may be that he is not connected to the system without account details being entered: the method may depend on the particular IP.
You may also need DNS numbers for his connection.

Advice on Fixing/Setting Up Mac Server behind Router

I would like advice on how to setup/fix a Mac Snow Leopard (10.6.8) server running on an Xserve. The server is only used to to host network accounts / act as a remote drive for a Mac-based laboratory. It is not a mail server, web server, etc. The goal is to enable (i.e., force) students to keep all of their documents on the server while accessing them easily from any computer, ideally from any point in the world.
The current setup is:
Linksys router (192.168.1.1) connects WAN (address WWW.WW.WWW.WWW) to LAN with both DMZ and local DNS pointing to server address (192.168.1.55)
Snow leopard server at 192.168.1.55
Client macs and pcs with various local addresses 192.168.1.XXX
From the LAN side, this setup works well in that all of the client Macs (from PowerPCs running 10.5 to brand new machines running 10.8.4) have no problem accessing their network accounts. They can also access the outside world seamlessly. The server can be administered using Screen Sharing from client machines running recent versions of Mac OS (e.g., 10.8.4)
From WAN side, some things work but others don't:
          – Macs can access the server using AFP://WWW.WW.WWW.WWW, although VPN
                    needs to be running if we are off-campus
          – Macs CANNOT login to the Network Account Server when outside the LAN
                     If I go to "Users & Groups", "Login Options" and enter the server address
                    WWW.WW.WWW.WWW, I get unable to add server with a "Connection
                    failed to the directory server (2100) error message
          – I can no longer login to the server using Screen Sharing. (This worked a few months ago,
                    so I am not sure why this is failing.)
          – I worry that opening a DMZ to the server is unnecessary from a security standpoint, and
                    I would be better with port forwarding specific ports (but which ones?)
I am open to new configurations if necessary, but I suspect this is something straightforward. I am also happy to RTFM for either the server or the router, but I'd like some guidance as to what is feasible/preferred. Specifically, I would particularly like students to be able to login to the Network Account Server from outside the LAN.
The server does not do anything else (e.g., mail, web hosting).
Although we do have an IT support group in-house, their opinion seems to be that computers are security risks that should not fall into the hands of users. The mere mention of Apple products sets off a rant.
Thank you for your advice and suggestions.

I usually use either telnet (non-SSL/TLS ports) or openssl s_client (SSL/TLS ports) or maybe nc (for scanning ranges of TCP and UDP ports) to check access to specific ports from the command line, though it's very simple to run a port scan via Network Utility for this case. Launch that remotely, and see what your client can see.
Here is a list of the ports used by Apple (TS1629)   For Open Directory, you'll need at least TCP 389 or preferably 636 punched through your gateway and your local firewall, if you're not VPN'ing in.   If you're using your own DNS, you'll need TCP port 53 open (and this is mildly hazardous to your bandwidth, as more than a few folks are using DNS servers as part of DDoS attacks; they'll spoof queries and cause your DNS servers to send a reply at somebody else as part of the DDoS. The DNS servers really need to be locked down against this dreck.)
You may also need to aim your client's DNS explicitly at your own DNS server, if you're using a private domain and a private IP address space; if your servers don't have public IP addresses and public names.
Personally, I generally wouldn't expose the Open Directory ports to the 'net, or most anything else for that matter.   I'd usually VPN into the network, and "DMZ" the web-facing stuff where I can. Too much weird cruft is hitting the firewalls I'm monitoring, undoubtedly looking for weaknesses and vulnerabilities. Using the VPN services isn't a panacea, but does mean your traffic is hidden from most monitoring, your servers' ports and services are relatively protected, your DNS services are your own, and your exposure is largely limited to the VPN server access.
For the remote clients, I'd use Portable Home Directory for the wandering devices, or straight OD via VPN.

Mac Mini PPC and Usb wifi dongle?

So I have a ppc mac mini and I purchased a wifi dongle for it. (not the Belkin one)
I have drivers for it that appear to be correct, everything installs fine.
However when I go to network to configure the device there is no option to choose usb as a network interface. The only options are firewire, or internal modem.
I'm sure this has been addressed but I've searched and search.

Sorry wow been a long time since I was here, but things have progressed ... somewhat.
Turns out there were specific drivers that I was not in possession of. The manufacturer supplied them and I thought all was good.
Turns out I'm having another problem now that it took some time to figure out ...
The dongle works for a time, but seems to get booted from my router or something after going to sleep or rebooting.
The weird thing is that the dongle software itself and the mac os think its connected, it shows an IP address that isn't on my network.
If I reboot the router and then reset my IP on the mac mini it will work until it goes to sleep or reboots.
I updated my Linksys WRT54G to DDWRT to see if that would fix things but even with new firmware and reset settings only this mac is affected by this problem. Also the dongle doesn't do it on any other computer.
So its mac mini/dongle/router specific ...
thanks again for all the suggestions and help

Setup VPN on Mac Mini Server running OSX through a BT Hub Router

Hello everyone,
I know this question has been posted several times and I have looked at the suggested solutions, trying each of them. I think this is really down to my lack of knowledge hence hoping someone out there could point me to the right direction for more resources / information, please.
I am trying to setup a Mac Mini Server with VPN access. My server sits behind a BT Hub router. These are the steps that I have been through:
1. I am using the server app and after registering a free account with no-ip, I got myself a host name <myname>.ddns.net.
2. Then I setup the server using a domain name
3. I configured the DNS by first setting up a primary zone - zone: ddns.net. Then added machine record host name: <myname> pointing to my server which I have configured my router to assign a static ip address to it at 192.168.x.x
4. Then, I configured the VPN setting up for L2TP and PPTP, setup the shared secret, change the ip address range to match that of the DHCP range on my router. My router by default has a DHCP range between 64 - 253.
5. Then, I also configured my router to port forward 500, 1701, 1723, and 4500 to my server at 192.168.x.x (I selected both TCP and UDP).
6. Finally, setup a user account with account name test and password abcd12345
7. Gone on my "client" machine which is basically my Samsung S4 handphone, selected VPN -> PPTP -> server address: <myname>.ddns.net -> entered account name test and password abcd12345.
This didn't work.
Then, I read some post about manually configure DHCP on the server app. Went on the server app, turned on DHCP and setup a network named TestDHCP. Assigned ip address range between that of the default DHCP range on my BT Hub router.
This does not work either.
Could someone please kindly help me with it? I am completely lost.
Thank you in advance.

To run a public VPN server behind an NAT gateway, you need to do the following:
1. Give the gateway either a static external address or a dynamic DNS name. The latter must be a DNS record on a public DNS registrar, not on the server itself. Also in the latter case, you must run a background process to keep the DNS record up to date when your IP address changes.
2. Give the VPN server a static address on the local network, and a hostname that is not in the top-level domain "local" (which is reserved for Bonjour.)
3. Forward external UDP ports 500, 1701, and 4500 (for L2TP) and TCP port 1723 (for PPTP) to the corresponding ports on the VPN server.
If your router is an Apple device, select the Network tab in AirPort Utility and click Network Options. In the sheet that opens, check the box marked
Allow incoming IPSec authentication
if it's not already checked, and save the change.
With a third-party router, there may be a similar setting.
4. Configure any firewall in use to pass this traffic.
5. Each client must have an address on a netblock that doesn't overlap the one assigned by the VPN endpoint. For example, if the endpoint assigns addresses in the 10.0.0.0/24 range, and the client has an address on a local network in the 10.0.1.0/24 range, that's OK, but if the local network is 10.0.1.0/16, there will be a conflict. To lessen the chance of such conflicts, it's best to assign addresses in a random sub-block of 10.0.0.0./0 with a 24-bit netmask.
6. "Back to My Mac" is incompatible with the VPN service. It must be disabled both on the server and on an AirPort router, if applicable.
If the server is directly connected to the Internet, see this blog post.

I have a Time Capsule as my router. I can connect wirelessly to the network and internet with my MBPr, but my Mac Mini will only connect to the network wired or wirelessly. Airport on it sees the internet as green, but will not connect.

I have the Time Capsule hooked to a wireless modem. It uses a static IP, which is put in and running. The MBPr connects, as well as my iPhone 5, to the internet and network without problem. I can see the Mac Mini, external drive attached to it, and the Time Capsule. The Mac Mini connects to the network wired or wirelessly, but not to the internet. On wireless, using AirPort the Internet shows green, but no connection when I open Safari. The settings under network settings are identical except for LAN IP between the Mac Mini and the MBPr. I was hoping someone might have an idea of what was going on. Before I moved the Time Capsule was on Bridge mode from another router, now it is on DHCP and NAT for the internal network.

No, its is connected direct to the providers fiber box.

Mac mini server refuses to get DHCP address from router

Everything was going along fine. But after a power outage the server goes to a 169. address when the router puts out 198. addresses. If I put a static 198. address in it sees the network but won't connect to the internet. I've flashed the router (everything else sees the router fine, 3 computers and a time capsule). I've had the hardware checked at the Apple store - it picked up an address right away. After narrowing everything down the problem has to be in the operating system. I even did a full time machine restore to the day before the storm. No luck. Anyone heard of this problem.

Mauricette has a point.
A server function is not designed to accept a floating or dynamic IP address. If that is the case, how do you create firewall rules that prevent those unnnecessary ports being left opened from being attacked by rogue machines in Romania and China on a hourly basis when you announce to the world that your server is available if the server IP address keep changing due to the DHCP lease change? Yes, they do have bots that do this VERY EFFICIENTLY!
By changing the very nature of your firewall rules by working with DHCP, you are opening ports you do not know to accommodate DHCP dynamic addressing, which was the reason why your Mac Mini Server stopped working in the first place. It's ok for a client, since a client isn't serving any files to any one right.
By using client based firewall rules, you are exposing your server to attacks and when they get through your Mini server, which they can if they are persistent, they get into your home network and then whatever file server services you have opened and unprotected at the time WILL BE copied by these people easily.
I have a client once who did just that. She was attacked, the hacker went through her network like a rampaging bull. They were from China. My Synology RAID server gets this attack all the time, but I have a well establish IDS system and the Synology RAID has logs that tracks attacks.
For a server setup. Use static IP and then build a strong firewall around it and protect it and never compromise.
Recently, I just noticed someone somehow hacked and broke my WPA-PSK AES passkey for one of my Wireless N network router. It was not set up with a strong password though, but thankgod I had a firewall around that so my internal networks were safe. So this teaches you that if someone wants in bad, they will get in.
Hope this helps.

Cannot see Mac Mini Server from Internet: DynDNS alias gets thru cable modem to wireless router, not to the Mac Mini. How to configure?

I want to make my Mac Mini Server (Lion) visible to the Internet from my home LAN. I have followed the Lion server install wizards and also set up a dynamic DNS at DynDNS.com.
When I enter the Internet address with the proper alias from a web browser, I get dumped into the admin screen of the Linksys wireless router WRT300N. Hint: the WRT300N provides DHCP for the LAN, not the cable modem providing DHCP. The WRT300N has DDNS service set up. NAT and RIP are disabled. The Mac Mini DHCP is reserved.
Suggestions? I could use the Motorola Surfboard SB6121 to provide DHCP but have hesitations.
Point me to the right discussion/article and get me back on track, please.

This sounds like a simple port forwarding issue, but I don't understand your LAN setup.
The WRT300N has DDNS service set up. NAT and RIP are disabled.
The chances are, you're running NAT somewhere in your network. If not the WRT then what? If it's your cable modem then you must have port forwarding configured on the cable modem, and that's where you need to focus - change the port forwarding to point to your Mac Mini's address rather than the WRT.
HOWEVER, it is far more common to have the wireless router perform NAT and DHCP, which is why I question your setup.
Not directly related, but:
The Mac Mini DHCP is reserved
Nix this. Your server should be configured manually, with a static IP address, not DHCP, even with a reservation in the DHCP server. The only advantage of DHCP is for dynamic hosts (hence the 'D' in 'DHCP') or if you expect to change your entire local subnet on any kind of frequent basis. The reality is that you can't just change the IP address of Mac OS X Server like this - there are too many dependencies, so it's better to set it manually, knowing that there's a cost (and pain) to change the server's address.

Can't Connect to Router Using Airport Through Mac Mini

Hey guys.
I got a new 13" White MacBook in Jan. of this year (2009) and it hasn't given me any trouble, until now.
I've been able to connect to any wireless network before, both through modems and computer-to-computer.
However, my new router is giving me some trouble. It's a Tenda brand router connected via Ethernet cable to a new MacMini. The internet on the MacMini is working fine, but I can't seem to find the wireless network the modem should be giving off on my MacBook. As I said earlier, I've never had any problems with my airport before.
I have all the information needed to connect to the modem (IP, Subnet Mask, Router , and DNS Server) but I'm not sure where/how I'm supposed to enter them.
Can someone help?

Well, i fixed it! Thanks to other questions in the Mac Forums, i learned that if i turned on the Internet Sharing in my System Preferences i could use the Mac Mini as a sort of 'host' computer. For any having the same or similar problems, here's the thread:
http://discussions.apple.com/thread.jspa?threadID=1927510&tstart=0

Mac mini unable to connect to internet via router

I can't seem to connect to the internet using my mac mini.i use a netgear wireless router which has my imac,and 2 windowsxp PC and a maxtor network drive connected ,these all work on the network.
The macmini(no airport) is connected using an ethernet cable and a netgear powerline ethernet adaptor.
I cant solve the problem!Can anyone help me please?
Dan
themint

Hi Dan
Have you confirmed that the Netgear Powerline adaptor works fine with other computers on your network?
On your mini, if you go into System Preferences - Network - Built-in Ethernet, what are your TCP/IP settings? Are they the same as for the iMac?
Matt

Mac Mini doesn't reconnect to wifi router

I have 2 mac minis - a mark I running Tiger, and a newer dual-core running Snow Leopard. They connect to my network wirelessly through the airport. I usually switch my Netgear router off at night for security, but when I switch it back on, the Tiger mini will reconnect to the network OK, however the SnowLeopard mini will not, and requires a reboot.
This strikes me as a bit odd. Is there something I can do to encourage my newer mini to reconnect automatically? I have it set up to "ask to join new networks and to connect to known networks", but it's clearly not doing this.

Have you tried just turning the AirPort off and on rather than going for a full reboot? I know that isn't exactly the solution you were after but it's a lot faster if it works.
On this particular occasion I'd say you're too paranoid and that you can safely leave the router on to no ill effect although it wouldn't be a bad idea to change to WPA2 as all your equipment should be capable of it at a guess.

Connecting Mac mini to internet through Xfinity router

This one took me a couple weeks to figure out, and I've seen a couple of similar posts in the forums, so I decided to post my findings here in the hope that it will help someone else.
Short version of the problem: I have a Mac mini (mid-2010 server version) that would connect to the Technicolor TC8305C WiFi router that was supplied to me by Comcast, but it would not connect "through" to the internet.
Details: The Mac mini connected automatically to the Wi-Fi (via DHCP) of the router, but nothing would connect "through" to the internet -- not Chrome, not Safari, not Mail, not the App Store, nothing. This was baffling because every other device in the house (3 laptops, 2 iPhones, and an Apple TV) all connected just fine. I checked all of the settings in the Network pane of System Preferences, comparing the Mac mini's against each of the laptops; all of the settings were the same (default, "out-of-the-box" settings). I thought maybe the problem was something at the OS level because the Mac mini was running Snow Leopard server and the laptops were not (two were running Mavericks, and one was running Leopard).
Here's where it gets weird... I connected the Mac mini to the router using an ethernet cable and everything worked normally for the wired network device. I was able to use the App Store to update the OS on the Mac mini to Mavericks. However, after I disconnected the ethernet cable, the problem came back and the Wi-Fi would connect to the router but not to the internet.
I double-checked that any "server" software on the Mac mini was turned off -- e.g., that it was not trying to serve as its own DHCP server. As I suspected, none of these services were on, so that wasn't it either.
In that same vein, I tried setting a static IP for the Mac mini in the router's control interface. Again: no luck.
Lastly, I got this weird idea that the only remaining difference that I hadn't tried was the pre-configured IP address prefix octets.
Solution: I reconfigured the router to use 192.168.x.x (like my previous router did) as the network prefix instead of the 10.0.x.x prefix that it uses by default. After I made that change in the router, everything fell into place and the problem went away. I never did figure out the reason this change was significant, but as I said -- it was the only thing that worked.

Interesting, thanks for the report/tip!

Airport Express problems with new MAC MINI and DLINK router SOLVED

Hi just thought I would post this as it may well help others experiencing similar frustrations with new core duo mac mini and wireless connection or quality problems across the network / internet etc
I have a 3 week old, new mac mini core duo 1.8ghz 2gig ram, 120gb disk - First Mac, connecting to my exisiting wireless network via DLINK ADSL Router 2MB Broadband also one windows laptop and pc also wireless on the network and two airport express potins to stream itunes to
Problem was briefly
Mac worked fine, but the network connection just far too slow, laptop and pc, 1800+ kbps downstream mac mini 90 - 150kbps (http://www.adslguide.org/tools/speedtest.asp)
also if i ping the router directly from terminal (ping -c 20 192.168.1.1) average response 12+ ms with 20% packet loss, yet laptop and pc avg 2ms no losses
Spent 2 evenings on frustrating calls of more than 1 hour each (due to being cut off , then ring back and closed etc etc) and carrying out a the helpdesk troubleshooting (I am an IT consultant I think I am above this level), eventually an archive and install of the os as well
last night I call for the third time, insisting I dont wish to carry out any further troubleshooting, and want it replaced and resolved or my money back
I receive a call back from product specialist (not sure if thats mac mini specialist or airport) but we resolved the issue (his knowledge far superior to the help desk do this do this attitude)
between us we carried out the folowing and resolved the problem and I am now very happy
mac now downstreaming also in excess of 1800kbps (as expected for 2mb broadband)and no packet loss
This problem was resolved by switching off the turbo option hidden away in the routers settings, under wireless configuration
Supposed to improve performance, but its rubbish and will make hardly any difference under mac os to the speed but will certainly affect your mac mini performance(you may have a similar setting switched on in your routers and mac os dont like it)
We stumbled across this by first disconnecting one of the airport express devices from my dlink network, and using it on its own default apple wireless settings, effectively making it a standalone wireless network, and not via the dlink router
we then carried out the same ping with the ip address of this device (from airport admin utility default 10.0.1.1) and the results were fantastic 2ms avg no package loss
this established it was something with the router, and how we then interrogated the routers settings and found the turbo on option within wireless configuration
you may not be able to replicate this if you dont have an additional network you could join (such as airport express), but probably worth checking your own router settings for something similar
Hope that may be of assistance to others, sorry that its a bit long winded and garbled, but I'm just so excited to finally get my new mac working as i would expect it to
Also perhaps insist on speaking to a product specialist immediately that the helpdesk are unable to help you

Hello macfar14. Welcome to the Apple Discussions!
For just streaming iTunes and/or for sharing a USB printer, the AirPort Express Base Station (AX) just needs to be configured as a wireless client ... which you already attempted to do.
Just to be sure nothing was missed, here are the basic steps to do this:
Either connect to the AX's wireless network or connect directly, using an Ethernet cable, to the Ethernet port of the AX, and then using the AirPort Utility in "Manual Setup" mode, make the following changes:
AirPort > Wireless
o Wireless Mode: Join a wireless network
o Network Name: <existing wireless network's Network Name or SSID>
o Wireless Security: <select the encryption type of the existing wireless network>
o Wireless Password: <enter the existing wireless network password>
o Verify Password: <re-enter the existing wireless network password>
Music
o Enable AirTunes (checked)
o iTunes Speaker Name: <enter desired speaker name>
o iTunes Speaker Password: (optional)
o Verify Password: (optional)
o Click Update to write the new settings to the AX
In iTunes:
iTunes > Preferences... > Advanced > General
o Look for remote speakers connected with AirTunes (checked)

HT5390 What port should i forward in the router if I'm to connect to the mac server behind NAT?

I am trying to remote administrate a Mac Mini running Mac 10.8 server but couldn't figure out which port to use.
Tried the following but still woudn't connect unless DMZ is opened.
Remote Login (SSH) - 22
Screen Sharing Service (VNC) - 5900
Web Service - 80, 443
VPN Service (L2TP) - 500, 1701, 4500
VPN Service (PPTP) - 1723
Any clue?

When you say administer, do you mean something like control your parent's Mac remotely, or do you mean officially adminster a classroom full of Macs? If a classroom full of Macs, then you are most likely taking about using the Apple Remote Desktop software which you pay for.
If, as I suspect, you just want to control your own or a family member's Mac remotely, then you do not need to pay for anything.
If you need Screen Sharing, you open port 5900 (the VNC port)
If you need File Sharing, you open port 548 (AFP)
If you need access to the Unix command line, or you want to use the ssh 'scp' or 'sftp' file transfer commands, then you need to open port 22.
Visit <http://PortForward.com>, they will provide port forwarding instructions for just about every home router out there.
I would also suggest you get a free dynamic DNS name so you can address the remote Mac by a constant name instead of having to know the current IP address assigned to the home router, which the ISP can change anytime they want. No-IP.com or DynDNS.org offer free dynamic DNS names. You run one of their dynamic DNS updating clients on the remote Mac to keep the dynamic DNS name updated with the current ISP assigned IP address.
Once you have the port forwarding working, you connect for screen sharing using
Finder -> Go -> Connect to Server -> vnc://address.of.remote.mac
and for file sharing
Finder -> Go -> Connect to Server -> afp://address.of.remote.mac
If you are going to use ssh, scp, or sftp, then from an Applications -> utilities -> Terminal session you would do something like:
ssh [email protected]
scp local.file [email protected]:/path/where/to/put/the/file
scp [email protected]:/path/of/file/to/get /local/place/to/put/the/file
There are also sftp GUI clients you can use to make this part easier.
If you really cannot get this working, then consider using something like TeamViewer.com which deals with all the messy home router NAT navigation.

Mac Mini Behind Router

Similar Messages

Maybe you are looking for