Solved FVS318VPN Firewall Reset. Windows Server 2003. HELP.

Dell Dell poweredge 1900 server (xeon 50...
January 7, 2013 at 16:25:04
Specs: Windows 2003, 8GB
We had an IT person that went AWOL, our firewall config was never viewed or backed up. Firewall was reset to factory defaults. :(

We have an ISP that goes into the Firewall (netgear FVS318).

We have a Dell Windows 2003 Server. We have exchange server for email running, don't host a website here, but did have a VPN setup (I believe) for remote server access and remote email access for some of our users.

Can access the Windows 2003 server and firewall, no problem.

I was successful in getting internet working for the all users, put in the primary IP info, gateway, etc., it works great. On all client computers ONLY.

However, Internet on the server does not work, email (exchange server) doesn't work and can't access the server remotely any longer. We also have a network printer that I can't access (even with the IP).

Next, ports and IPs, ports I was looking for definitives on which ports should be open and ranges on the firewall for Windows 2003 Server, didn't find much on this, there are defaults in the firewall, but they don't seem to help since things server are not working.

I am at a loss. What should I try next? Looking for some help. Thanks.

See More: FVS318VPN Firewall Reset. Windows Server 2003. HELP.

Report •

January 7, 2013 at 16:48:50
I should add, I can't see my windows 2003 server on the network (the same server that can't get google in a browser now (but it could last week). I know it's firewall related, I thought if I knew how to put in the port, range, allow the firewall, I'd be home free. I just don't know how to do it precisely. I've tried following the directions for netgear firewall, read all the manuals, but it hasn't worked, maybe I'm putting in the wrong information. I put in what I should have based on ipconfig /all available ports in netstat -a -o -n etc. everything worked fine last week, the firewall was reset Friday afternoon.

Report •

January 8, 2013 at 07:15:13
On both a working computer, and on the server that doesn't have internet, open a command prompt window (ie: Start >> Run >> type cmd and hit Enter) and perform the following command:

ipconfig /all

Once you've finished, copy/paste the output into a response on here so we can have a look. Label one "Server" and the other "working PC" or something to that affect so we know which is which.

For info on how to copy/paste from a command prompt window click on my name above and read my "how-to" guide titled, "Post the output of ipconfig (version 2)"

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***

Report •

January 9, 2013 at 15:02:27
✔ Best Answer
Got it figured out. The firewall was trying to run as a DHCP server, the Windows 2003 server DHCP service was stalling because of it.

Turned off DHCP on the firewall, restarted DHCP service on Windows 2003 server, it worked.

Also, the Default IP and Gateway IP were wrong from the firewall to the server, even though the internet still worked, they were and should have been Once these two things were done. The server worked. :)

Report •
Related Solutions

Ask Question