Unable to access DNS names

  • Thread starter Thread starter Matt Maynard
  • Start date Start date
M

Matt Maynard

I'm setting up a new PC for our work network. It's running Win2k SP4 and
cannot see the network. I can't see anything in Computers Near Me, and
unless I know an ip address I can't ping anyone (inside or outside the
network). DHCP is turned on and I can release/renew the address using
ipconfig. The DNS addresses are assigned from the DHCP server and I can ping
both servers. nslookup returns the following:

C:\>nslookup yahoo.com
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 207.108.112.1: Timed out
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 204.147.80.5: Timed out
*** Default servers are not available
Server: UnKnown
Address: 207.108.112.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

Any ideas on how I can get this computer to see the outside world?
 
Are you able to ping the two DNS servers that you are using (207.108.112.1
and 204.147.80.5)? I tested and was able to ping both these servers (by IP
address) and was able to resolve various names using these two servers.

If you are able to ping these addresses, then check that the router or
firewall or whatever is the intermediate device to your connection to the
internet is not blocking common ports such as UDP 53 and TCP 53 for DNS,
TCP 80 for HTTP, etc.

----
Thanks,
Rakesh Chanana [MSFT]

When replying, please post to GROUP so that everyone can benefit from the
knowledge.

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


--------------------
 
Thanks, that did the trick. I had blocked access to the UDP ports, and
removing that block allowed things to work. Under what circumstances should
UDP ports be blocked?

Matt
 
I don't think there's a reason to block UDP ports for common services such
as DNS. You may not want to open up all UDP ports because of internet
security issues. For example, tftp uses UDP and tftp is sometimes used in
internet hacking attempts.
----
Thanks,
Rakesh Chanana [MSFT]

When replying, please post to GROUP so that everyone can benefit from the
knowledge.

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


--------------------
Reply-To: "Matt Maynard" <[email protected]>
From: "Matt Maynard" <[email protected]>
Newsgroups: microsoft.public.win2000.networking
References: <[email protected]>
Click to expand...
Subject: Re: Unable to access DNS names
Lines: 31
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <[email protected]>
Date: Fri, 29 Aug 2003 11:43:29 -0700
NNTP-Posting-Host: 67.41.30.172
X-Trace: news.uswest.net 1062182654 67.41.30.172 (Fri, 29 Aug 2003 13:44:14 CDT)
NNTP-Posting-Date: Fri, 29 Aug 2003 13:44:14 CDT
Path:
Click to expand...
cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!newsfee
d01.sul.t-online.de!t-online.de!newspeer1-gui.server.ntli.net!ntli.net!peer0
1.cox.net!cox.net!news-out.visi.com!petbe.visi.com!feed.news.qwest.net!news.
uswest.net.POSTED!not-for-mail
Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.networking:34508
X-Tomcat-NG: microsoft.public.win2000.networking

Thanks, that did the trick. I had blocked access to the UDP ports, and
removing that block allowed things to work. Under what circumstances should
UDP ports be blocked?

Matt


Rakesh Chanana said:
Are you able to ping the two DNS servers that you are using (207.108.112.1
and 204.147.80.5)? I tested and was able to ping both these servers (by IP
address) and was able to resolve various names using these two servers.

If you are able to ping these addresses, then check that the router or
firewall or whatever is the intermediate device to your connection to the
internet is not blocking common ports such as UDP 53 and TCP 53 for DNS,
TCP 80 for HTTP, etc.

----
Thanks,
Rakesh Chanana [MSFT]

When replying, please post to GROUP so that everyone can benefit from the
knowledge.

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Click to expand...
Click to expand...
Click to expand...
 
Back
Top