Windows Forum

Ask something
Discussion Locked

no name resolution...

0 helpful
7 replies

by dlanors

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have an NT 4.0 Terminal Server, with a DSL connection to the internet. From this machine I can ping anywhere, and I can connect in to the Terminal Server from the net thru a VPN. However, I can not find anything from this server by name. I have tried many valid DNS entries, and I always receive back a "bad IP address" message if I try to ping by name. NSLookup gives me a "can't find server name for address x.x.x.x (my DNS server IP), no response from server". If I use a hosts file, that works, but I want to be able to browse the net, and need DNS to work. I have tried removing/reinstalling TCP/IP, which made no difference. Any help would be appreciated.

7 replies

by spiceman

your dns entry needs to be the ISP you are using - they should give you upto 3 DNS ip addresses you can use for the internet. If you want a dns at work or home just to practice on that's a different story

Good luck

by dlanors

It doesn't matter what DNS servers I use...including the ISP that I am connecting thru...

by allan

Not sure but it would seem that this server has a static ip address.
Not sure how this would affect your hookup with your ISP.
Make sure you have the right gateway specified.
Send more info about your TCP/IP settings.

by dlanors

It turns out it was an issue with MS Service Pack 5 for Terminal Server. When I removed the Service Pack, everything started working fine again. Thanks for your efforts...

by rogued,mcse

What are you using as a gateway router? Can all other machines behind this router resolve names to outside your domain. From reading your post I gather that you can ping the far side of your router. Make sure you enter a valid DNS server entry into your TCP/IP settings. Also make sure you have more that one. I would even use one or two from a different ISP. Once you have completed all of that, if the problem still exists contact your ISP and inform them of the problem.
Good Luck,

-Doug

by dlanors

It turns out it was an issue with MS Service Pack 5 for Terminal Server. When I removed the Service Pack, everything started working fine again. Thanks for your efforts...

This discussion is closed to new replies.