RE: [ActiveDir] Strange Windows 2003 behavior after joining AD do main

2003-09-12 Thread nsegar
Actually I did the ipconfig /flushdns - no effect. nbtstat -RR would reregister my NETBIOS names, I didn't think it would help but I did it anyway. - No result. ROute print looks fine too. What kills me is that the IP stack won't even recognize the hosts file entries. GetHostByName() won't

RE: [ActiveDir] Strange Windows 2003 behavior after joining AD do main

2003-09-12 Thread Mulnick, Al
Title: Message Best bet is to create an OU that has no GPO's to clear that out of the troubleshooting process. Move the server into that OU and test again. Be sure to refresh the GPO's so you can be sure that all have been removed. Al -Original Message-From: Ninet Segar

RE: [ActiveDir] Strange Windows 2003 behavior after joining AD do main

2003-09-12 Thread nsegar
Good Idea, Hopefully whatever is doing this doesn't tattoo the registry. Thx -Original Message- Best bet is to create an OU that has no GPO's to clear that out of the troubleshooting process. Move the server into that OU and test again. Be sure to refresh the GPO's so you

RE: [ActiveDir] Strange Windows 2003 behavior after joining AD do main

2003-09-11 Thread james . blair
Title: Message Ninet, Try the following on the 2003 servers: From within a command prompt: ipconfig /flushdns nbtstat -RR route print (check and see whether or not you have inadvertantly put in a persistent route) Make sure that you don't have any "rogue" entries in the host file...