Windows 2008 R2 No Internet Acces


I have a Windows 2008 R2 box that is showing the yellow exclamation sign in the Network and Sharing Center Icon (anx a big red X to the Internet once you open the Network Center).

However, the server HAS access to the Internet just fine.

I am running behind a http Proxy and I have blocked access to several web sites but I do not understand why this machine shows the yellow sign as my other Windows 2008 R2 server and even Vista PCs are not showing this problem.

Anyone has a clue why?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hey Benj, I had the same problem. My solution was to manually assign the IPs and DNS info. Either one could spell disaster. If you have 2 NICs and your ISP has a private IP for DNS entries you'll need to run a special command.

run > cmd
route add mask -p

Replace with your back end IP gateway.

Hope that helps.
benjilafouineAuthor Commented:
No, I have only one NIC and the IP address is already static assigned (the router being the gateway and a DC being the DNS server). I double checked the address and everything is OK.

Why only one machine would exhibit this problem, I don't have a clue yet (aside that this is a Terminal Server rather than a simple server or PC.

First check to make sure they are resolving names correctly. Do an nslookup on both the 2008r2 that is being blocked and your 2008 that works fine. See if they can both resolve If this works then dns is working. Next do a tracert for If it works then we know the routing is working and it must be blocked. For a test download and install firefox. If this works then the problem is your proxy configuration. You may want to delete it and re-configure.
benjilafouineAuthor Commented:
I fixed it an a bizarre way: I changed the default gateway to another gateway address and then I reentered the original one and the warning went away.

The only way I can explain this is that this server was in another location before I moved it to this new one. Maybe the gateway value hadn't been properly entered in the IP properties page. I see from time to time changes "hanging" for a long time with Windows 2008 R2. Maybe I had this problem last time I changed the address.

Another bizarre thing with Windows...



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
This question has been classified as abandoned and is being closed as part of the Cleanup Program.  See my comment at the end of the question for more details.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.