PeachParts Mercedes-Benz Forum - View Single Post

pawoSD · #8 07-25-2008, 10:58 PM

I tried setting up one of my servers with 2003 to be a router, but I absolutely could not get it to open up ports to the outside that would allow my web server traffic from another system on the network out/be accessible. I spent hours at it but never got it to work. The idea was that the windows server would be our router, dhcp server, vpn server, and traffic monitor.....I had all of it working great, just couldn't get the outside (ISP) IP address to reach our webserver on the internal network....I had the ports open on the firewall and the IP address of the webserver all entered in and forwarded, but it wouldn't work. Oddly, I had our mail server stuff entered in the same way, and it DID work. Explain that one?

None of it will be an issue now anyways since we're going with the Unimog of self contained units (The Netgear)....but still....I'd like to know what the deal was with port forwarding in Windows Server! The ShieldsUp! site would say every single port was in stealth, even when I had opened them up in the windows firewall.

The Netgear unit will be more reliable, more secure, use less power, and be easier to configure than windows server for the things I need it to do...so thats a big advantage.