This is a discussion on Bad DNS record getting into DNS Client Cache within the Network forums, part of the Windows xp Support category; Hello, My question Is there a way to check or record from where the Windows XP pro workstation is getting ...
Is there a way to check or record from where the Windows XP pro workstation is getting the wrong IP address and placing it into its DNS cache?
We are connected to a multiple forest/domain network. All of our user workstations run Windows XP using DHCP and DNS Client. There are two databases our users access that are not on our domain. Through DHCP we append these DNS suffixes:
About 100 of our users must access a database multiple times a day on Company_A.com network.
Company_A is not on a trusted domain. Via group policies we map a V. to \\databaseserver1.Company_A.com\DatabaseRecord
We also have OBDC setup to access the database above.
Our users are accessing records and images of documents on the database above. Most of the time there is no problem accessing the images. About 5 times a week we get a call from one of our users where they no longer can access the images on this server. The user have already looked at 3 document images in the last 2 minutes and when they go to look at image 4 nothing happens.
We have discovered if we flush the DNS cache the user can start accessing the images on this database.
For example purposes the correct IP address for the server above would be 172.16.99.100 but when the workstation starts having the problem and we ping databaseserver1 it is sending the ping request from 126.96.36.199 . Is there a way to check or record from where the Windows XP pro workstation is getting the wrong IP address and placing it into its DNS cache?
Thanks for your assistance,