DNS haywire!

Permabanned
Joined
19 Apr 2006
Posts
2,333
Location
West Yorkshire
My Windows 2000 machine at work keeps losing it's DNS registration for some reason.

It is a brand new Dell and all was fine until about a week ago.

Now I will be working away, the go to connect to a server on Terminal Services or to browse to share and blam, suddnely it doesnt know what the server is or where it is.

I have 2 network cards one that I keep disabled and use only when connecting to a seperate network.

I also have a cisco VPN client installed, but it is not in use.

I am on windows 2000 AD domain as well.

I can fix the problem by opening a command prompt and doing ipconfig /flushdns, but it is proving to be a little annoying!
 
To be honest havent tried, however an example of the problem is this:

ts.png


Notice the "expand by default" is ticked, yet the domain doesnt expand.

Double click the domain displays the error at the bottom of the screenie.

I can then type the IP of the server I wish to connect to and it connects fine.
 
Hmm, that's a shame. We need to establish if this is a name resolution problem with the whole domain (unlikely), your entire system, or that application. An nslookup test would have helped.

You're using the old TSC I see, would you be up for downloading the Remote Desktop Client and trying that (it replaced the terminal services client a few years back)?
 
Thanks I was being a bit of a numpty.

Unfortunately it is just the same with the rdp client. I can connect by typing in the machine name (dns is ok atm) or IP, but I cannot expand the list of servers. All I can see is the top level domain.
 
Back
Top Bottom