Originally Posted by Lars99
Just to clarify, are you trying to run your WHS box over a wired or wireless connection?
The first thing you need to do is eliminate the multi router aspect and place your WHS box, configured with a private static IP, behind the closest router to your modem. Forward the appropriate ports and you should be in business. You said you had it working, so we know your ISP doesn't block it.
If upnp isn't enabled, WHS 2011 will still throw back some errors, but it should allow you to get to the phase of creating the homeserver.com domain. Wait an hour or so for DNS to propagate and profit. Then work on fixing your internal routing.
It is likely how I setup the network to start with.
AT&T U-Verse gives you a 2Wire 38xx Gateway/Router, it has four 10/100 ports. Like most over the counter ISP provided hardware, they haven't joined us in 2010 yet.
File Transfer Speeds were paramount. I had two options, Powerline and Wireless. I went with Wireless because Powerline seems iffy in some homes and didn't feel like being a test lap mouse. Wireless penetration in your home is great, I get full bars on everything.
So I went out and bought a TRENDnet 802.11n Wireless bridge for the Sony PS2 and the HTPC and a Buffalo entry level (10/100 ports, no USB) 802.11n WiFi certified wireless router.
Initially, I setup the older 3800 to be the modem (turned off Wireless, put in DMZ+ mode) and hooked up the Buffalo router. It worked fine, I was using the stock firmware because of reported problems with DD-WRT. WHS 2011 found the router, setup Remote Access and that was it.
I don't know if I can access outside the network, I haven't tried but when I setup my URL for the server, the DNS won't solve it. This was tried over several days, putting a hole in your propagate and profit theory. Wouldn't take my xxxx.homeserver.com, but would take 192.168xx.xx, put an X through HTTPS, say it was unsecured but give me the Remote Access page and all functions worked.
I tried the Microsoft WHS 2011 threads for answers and got nothing. Then while away from home, as I said my sister returned from school. Disconnected the Buffalo and turned the WiFI back on the 3800 because even though I had it in mixed mode (G/N), she said she couldn't connect too it, likely a lie. To keep from having a war in the house, I left it alone and just plugged my Buffalo back into the 3800. Then the old GV failed and was replaced with the new Black 3801 I believe. Was away again, came home, same thing, Buffalo disconnected and not reconnected and I had no access to anything. I plugged it back into the new 3801, everything was fine, but since no ports are forwarded on either router, all I get is internal access to the server and even Remote internally doesn't work (ports blocked on U-Verse router).
I went to school for A+ but yet being grown child, you are still viewed as being 10-12 years old as I'm sure most of you will contend, they don't trust me "messing" with the network. I know enough about it to do what I need or put it back if it doesn't work, so I don't understand the concern.
Like I said before, I will likely do what you suggested because I want to ensure I have Remote Access while overseas. I will run the Buffalo as an AP and connect my HTPC, Laptop and Phone too it, put it in N only mode, leave the G wireless on the 3801 and bridge it to the Buffalo.
That's basically how I have it now, but the server is connected to the Buffalo and not the 3801. The Buffalo can't access the ports needed for Remote Access because they are blocked (not forwarded) by the 3801.
This is why I was considering running router software on VM on the server or get a cheap Atom board ($70) and put a Intel NIC into it and use that as a PFSense router. Get a Gigabit 5-8 port switch and plug all the devices into that.
Seems to me PFSense has stronger routing abilities and optional real time virus protection. A UPnP stronger than the Buffalo and I know works with WHS 2011 without a static IP on the server.
I tried setting up a static IP at the router (Buffalo) and at the server itself.
Still no remote access.
If you say I can get it done with the hardware I got currently, then I'm all ears. I can get the IP of the 2Wire and start working with it tonight/tomorrow until it works.
This is the last thing on the server that doesn't work, it does everything else beautifully, I can't ask for more.