wireless pc picks up old domain controler

[ison67]

We have a pc that connects to the domain via's wireless. When we have it at our main office, it works. Take it to the branch office where it belongs, it will connect to the wireless network, but it can't get an IP address. After some troubleshooting, we realize it is trying to reach the old Domain Contoller. We have checked all the settings, flushed everything we can thing of and it still trying to hit the old DC. Any ideas?

Thanks,
DJ

 

[Cstorms]

As for the ip issue, how do addresses get assigned? Are you using dhcp from the AP? You say it connects alright, you have already assured that there are no statically assigned ips on the client nic I assume? I would doublecheck your ipconfig after it says it is connected to the network.

You say it is checking for the old dc when it tries to login, you may legitimately have an ip from the dhcp pool?, if so you could still have SRV records in your new dc's AD Integrated zone that pertain to the old DC, especially if you have flushed dns cache on the client.

Check the ldap folders, and every where else for that matter, for stale records (assuming this machine is using the new dc's dns server for its primary dns.)

What you can also do in the future is use the Microsoft Network analyzer to capture some packets that are destined for the dc and see what response it is getting from dns.

Cory

 

[ison67]

I will follow up with the info you have given. Here is the info I received from the Technician:

When I took the PC back to Williston, it connected to the wireless network (Bluesocket AP), but would never get an address from the DHCP server at Aiken. Also, I noticed that when I typed "set l" to determine the logon server at the command prompt, it returned, one of our old domain controllers. When references to the old DC server in the registry and changing them to the NEW DC, it would revert to the Old DC setting after a reboot.

I manually set the IP address before I left Williston. It still would not get to the web.

 

[lhuegele]

Are the domains at your 2 locations the same domain, 2 different domains, or domains that are part of the same forest domain? Are the 2 domains using the same IP address range or different ones? Have you tried setting up a fixed IP on the wireless PC at the new location to see if you get network connectivity? That's what I would try first - assign a fixed IP from the new location, confirm connectivity and domain membership, then go back to a dhcp assigned IP setup.

Good luck,