Windows Server 2003 R2 Fresh Install, No internet

[lumstar]

Hi there,

Fresh install of win2k3r2 with sp2. Internet isn't working. I can make incoming connections to ssh and file shares, and the rest of the computers on my network have internet, but none for the server.

It is behind a nat firewall and I have the dns and gateway correctly set to that router. I can reach the router's web admin page and I can ping the router from the server, but I have no internet.

That includes windows update, ie, etc.

Does anyone have any ideas?

Thanks a lot!

Stephen

 

[itsp1965]

Do you happen to have the windows firewall enabled? or have you installed IE Enhanced Security Config? Are you going through a proxy server to get to the internet?

 

[lumstar]

Firewall is disabled (although I thought that it was for inbound connections only). No proxy. I didn't explicietly install IE Enhanced Security config, is it contained in the SP2 install?

Could IE ESC be the problem though, my connectivity problems exist outside of IE as well (update, ntp, etc.)?

Thanks,
Stephen

 

[lumstar]

Sorry, IE ESC is installed, it is always installed and enabled by default on a 2003 install, however, this should have no effect on the internet connection, only on web browsing in IE.

 

[Davetoo]

Normally a DNS issue. Try a tracert to a known Internet address and see where it "dies".

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

There are no more PDC's! There are DC's with FSMO roles!

 

[lumstar]

Hmmm.. definitely a DNS issue, weird. Here's what happens. tracert works fine for and IP but cannot resolve an ip based on domain name. Also, if I type the IP into ie, it can load the page fine.

So something seems to be wrong with my dns. Any idea what?

Thanks again!

 

[egodette]

Check the DNS entry on the nic card. Try pointing it to 4.2.2.1

 

[lumstar]

Nope, that does nothing. I am wondering if I have blocked port 53 outbound. I have enabled tcp/ip filtering on the connection but 53 is on the allow list.

Is there any other way I could have blocked 53 outbound?

 

[lumstar]

Hmmm, if I disable tcp/ip filtering then everything works as it should.

I did have port 53 in the allow list for tcp and udp. Do i need anything else? (I also have 80, 22 and 445 in allow list for web, ssh and smb trafic)

 

[lumstar]

Okay, so after some more googling, it looks like tcp/ip filtering does not allow dns to work, unless i open udp ports above 1024...

 

[Davetoo]

Anytime you can't "get" somewhere, but everything else seems ok, always look at DNS first and exhaust that as a problem before moving on to something else.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

There are no more PDC's! There are DC's with FSMO roles!