Server 2003 Internet Issue

Forums › IT Pro and developers › Server 2003 Internet Issue

Walrus

6 posts

Wannabe Geek

#27732 4-Nov-2008 22:37

Help!

I have a seerver running MS Server 2003 (with SP2), Terminal server and MDaemon. It has 3 thin clients and 3 PCs connecting to it via DHCP. Here's where the problem starts (it started about a week ago)

The PC's can connect and use the internet through the router fine.
The server and the thin clients cannot.

The server is serving both DNS and DHCP. I have checked the Event Viewer and there are no errors.

Next thing I discovered is I can ping the router from the server, but cannot browse to it. I cannot access the internal web site either.

I have checked the services and all are OK and running as I would expect. It is nothing silly like ICS or Firewall.

Any help would be greatly appreciated.

Cheers

bradi

137 posts

Master Geek
Inactive user

#175930 4-Nov-2008 23:06

Ok, rule out the thin clients as they are on the server.

On the server, can you ping stuff... no... firewall?... routing? RRAS config? router config/firewall?

You haven't hard coded MACs or anything on the router have you? Not doing double NAT via the server/router? Proxy?

Go back to basics... ping / tracert to the Internet from the server... does it work? No, why? If it does, can you telnet to something on the Internet?...

Try different switch, check network config... dns settings especially...

Good luck.

Walrus

6 posts

Wannabe Geek

#175935 4-Nov-2008 23:15

Thanks, but.....

No hard coded MACs, no RRAS, no double NAT.

Tracert to Xtra jumps to router, then to xtra jetstream etc.

From what I can tell, there seems to be a problem with getting out on port 80, whether it's blocked or vanishing.

Secondly, when MDaemon trys to collect POP3 it gets the bums rush from Xtra but I can access the server remotely via RDC or VNC.

Help, I'm running out of hair.

bradi

137 posts

Master Geek
Inactive user

#176432 6-Nov-2008 22:06

ok, telnet to your internal www server (it's not on the same server is it?) telnet www 80... do you get a reponse?... no it's blocked then... figure out what you installed that b0rked it. Take it back to basics.

If you can telnet to it, try a different browser, ie firefox. Although if your having trouble with other outgoing TCP protocols I don't think a browser change will make any difference.

A network sniffer would help in this situation.

Walrus

6 posts

Wannabe Geek

#176495 7-Nov-2008 08:15

I found the fault.

AVG version 10.190 has an issue where it may block all web activity. Of course this also blocks the AVG updates which also fixes the problem.

I should have thought of it earlier, but there we go. Remove AVG, (the server instantly worked) download the new version, install and all is happy.

The faulty release affects only some W2003 server installations, so others may have the issue.

Thanks for the help.

Cheers