Printable View
On my win2k server at work, about 50 pc's are added to the active dir. when I turn some off and ping their netbios name.
For example:
ping my-computer
it trys to ping using 192.168.16.13
but that's the ip when I joined the domain.
I'm currently using 192.168.16.55
What's the deal ? Why is it remembering this address and why isn't it checking the intranet for the new ip.
I tried: ipconfig /flushdns ...nothing
quick guess it sounds like a server/client syncronization error.
well i kinda got that already,
any known fixes, commands to flush this info
yea, u have a setting wrong with sync, find it and fix it.
why does there have to be someone like this in every board...
If all your going to say is "find it and fix it" I bet most would rather you say nothing at all
No solutions yet....
Even after reboot, cache flush, dns flush
i did say something more then find and fix, i told him its a syncranization error. When u log off a machine, if setup properly in his type of situation, it should syncronize with the server. Sometimes these will fail. When it fails, as it is obviously doing, it will tell you WHY it is failing, then go to the source of that error and fix it.
I assumed he would know what i meant seeing as how hes obviously not a network newbie.
not all users log off properly, either they can't be bothered or the PC crashed.
I'm in the midst of making a program that reads the netbios names from the server and records the ip's, since for some reason the server is remembering the ip of the client when joined the program is recording bogus info.
sync errors aren't showing up, no errors in the logs.
hmm thats interesting....i assume your obtaining ip's automatically then since its not chnaging on the server side? How bout assigning a set ip to each machine then resyncing the server and clients, maybe if it always has the same ip it won't pose a problem? if thats an option of course...
yes, IP's are obtained automatically from the server.
If the IP are fixed (from the server to the client) I'll get the same problem when a computer gets moved to another user.
I get the concept of resyncing but could explain your version so we're on the same track. (how you'd do it)
I didn't do it, i just know of it. You know what, let me get in touch with a friend of mine tonight around 10pm EST if i can, and i'll post his thoughts in the morning, hes a CISCO engineer and his main o/s is win2k.
My guess would be that its somewhere in the security setting under the admin options, maybe a policy.
Sounds great, Thanks