I have recently implemented a Cisco WAP54g Wireless Access Point into our office environment. We have about 5 laptop computers and 20 odd something PC workstations. All computers (laptops and desktops) are running XP Pro. The server is Windows Small Business Server 2003.
I’ve done quite a bit of troubleshooting so far, and I’ve seemed to narrow it down to the dns on the client computers. All computers have to be assigned a static ip pointing to the dns server. Without it, the computer points to the dns servers provided by the ISP. When wired, all computers login fairly quickly, due to it pointing to the correct dns server. However, the wireless laptops, take around 5-8 minutes, even when the tcp/ip is pointing towards the correct dns server. Also, there is an error message that shows up in the event viewer that says
Description:
Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.
and another one that says
Description:
Windows cannot determine the user or computer name. (The RPC server is unavailable. ). Group Policy processing aborted.
I was able to replicate the problem, when I disabled the wireless connection and had the wired connection obtain DNS server address automatically, which pointed towards the ISP’s DNS servers. After logging off and back on, the computer was stuck on Applying Personal Settings. But, when I pointed the computers back to the correct DNS server, it logged in quickly. So to me, in my unprofessional opinion, that the wireless is not pointing to the DNS server DURING login. After it finally logs on, everything else works fine, but I have a lot of people complaining about how long it takes for their computer to log on.
If anyone knows a way to help me out, I would greatly appreciate it.