Windows Home Server Problems

Hey guys, I just installed WHS on my old Dell 4600C today, and it's working great, except it isn't. It's having issues with the network, and being connected to the network is an important part of being a server...Anyway, I have a monitor hooked up to the server for set up. So I go to the WHS console > Settings > Remote Access. When I push the setup button in the router category, it asks me if it wants to continue and automatically port forward stuff for me, and if I say yes then I'm presented with the Router details. Here's a picture.

http://s585.photobucket.com/albums/ss300/Insecur1tyGuard/?action=view&current=P8070043.jpg

My router is a Netgear WGr614V9 and UPnP is enabled, and the router recognizes that there is a physical connection to the server (at least the lights on it are lit up for that port).

 

First - unless you are accessing your WHS from outside your network, you don't have to worry about the router. Port forwarding is only necessary if you want to connect to your server while you are away from your house. UPnP is unreliable with WHS and some routers - and yours is probably one of them. You can go here to test your router's UPnP feature.

Second - you should go to forum.wegotserved.com. It's a pretty good WHS support website, and there are wiki entries on what ports you need to manually forward to enable remote access (443 for https access and 4125 for the web interface; 3389 to enable remote desktop to your WHS from outside your network, port 80 for http access - I personally don't recommend opening 3389 or 80). You should also check out the Microsoft Home Server support site that Microsoft runs. Make sure you are more specific about the "issues with the network" you are having when you post in those forums.

Third - connect a keyboard and mouse and log in directly to your WHS. It's a lot easier than using remote desktop. Also - when you reply, post more information about your network problems. Can you not connect via the console? Does your WHS not connect to the internet for updates? Is it just an issue with enabling remote access?

 

I was using the computer with WHS installed on it the whole time.

I figured it out though. Turns out WHS didn't automatically install the ethernet drivers (important to a server, wouldn't you say). It was simple after that, 'cept for jumping through hoops to first obtain the driver, and then force it to install even though WHS isn't a supported OS.

I'll check out that site if I have more problems, thanks.

 

Since WHS is basically Server 2003, it's sometimes difficult to find drivers for older hardware. Even on newer hardware it's difficult, especially if the hardware was not designed to be used in a server environment.

 

Ughh! Tell me about it.