Link to home
Start Free TrialLog in
Avatar of jamesreddy
jamesreddy

asked on

Server no longer can connect to Internet.

Ok...this is wierd.  Last week everything is great.  I have three 2003 servers, 3 2000 servers.  One of my 2K3 servers is a domain controller and DNS server, one is my Symantec Ghost Server, and one is a member server/file server.  Of my 2000 servers, one of them is also a domain controller.

Ok...so...like I said, last week, everything is cool.  This week, I can no longer connect to anything not on the local network.  But here is the wierd part....the problem is only affecting my 2003 servers.  They cannot connect to the Internet anymore, my Symantec Server cannot connect to the LiveUpdate server anymore, and any attempt to connect to any address outside the network fails.

Internet Explorer yields the message "search page cannot be found.".  Symantec tells me it is unable to connect to the update server.

Now...another wired detail.  One of the 2K3 server is also an IIS server hosting our Intranet and Helpdesk sites.  Both of those worj from inside and outside the company.  So, traffic is allowed in, just nothing allowed out.


No other server or workstation on the network has any symptoms except the 2003 server, and they were fine last week.  What's going on?  Was there some freak virus or update that would stop this?

I've already tried setting Internet security to nothing, and it had no effect.  This is wierd.  It just started this week.

James
Avatar of jamesreddy
jamesreddy

ASKER

I meant to say one is my Symantec Virus Server...not my Ghost server.
Wow, that is weird.
Are your clients getting out?
What happens to a ping test? Try both IP and host pings, externally.
Do a DNS test.
Good Luck!
SOLUTION
Avatar of Glenn Abelson
Glenn Abelson
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
EVERYONE is getting out, EXCEPT the 2K3 servers.  They will not resolve DNS, they will not ping an external IP.  They ping internal IP addresses just fine.

Routers aren't an issue...this is definately an OS issue.  2K3 firewall is disabled, so that is not an issue...it's just these servers.  I have changed no configurations on them.  They were fine Friday when I left for the weekend...now they won't go out this week.

It's by far the wierdest thing I've ever seen.  I have five 2K3 servers total on three different campuses that are not interconnected and they all are acting the same way.  No one has seen this?  I was sure it was some new thing or update by Microsoft.  I can't imagine that we're the only ones with this problem.
Minor correction...they will not resolve DNS externally.  All internal traffic is normal.
What happens when you ping?
Is there anything in the Event Viewer?
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial