Q:
Wireless Domain Logon
While installing the following systems I am having trouble with wireless domain logon.
I have a Server and 7 workstations (PCs) in a network.
The server is running Server 2003 Standard, and each of the PCs is running XP professional. Five of the PCs are are wired and two connect to the network wirelessly.
The Five wired PCs are able to logon to the domain with no problem. The two wireless PCs are unable to find the domain server to logon, although if I logon to the PC locally the wireless networking works fine.
It appears that the logon, from "Ctrl-Alt-Delete", is comming before the wireless network is activated.
Is there some way to activate wireless networking prior to logon?
I have a Server and 7 workstations (PCs) in a network.
The server is running Server 2003 Standard, and each of the PCs is running XP professional. Five of the PCs are are wired and two connect to the network wirelessly.
The Five wired PCs are able to logon to the domain with no problem. The two wireless PCs are unable to find the domain server to logon, although if I logon to the PC locally the wireless networking works fine.
It appears that the logon, from "Ctrl-Alt-Delete", is comming before the wireless network is activated.
Is there some way to activate wireless networking prior to logon?
ASKED:
Nov 2 2006 10:41 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
A:
RATE THIS ANSWER
0
Click to Vote:
0
Click to Vote:
- 0
0
Possibility #1:
Simply pinging machines inside does not mean DNS is configured on mobile machines. Without DNS they can't find DC for logon. This could occur if you assume DHCP will fill in DNS parameters etc but in fact the mobile machines are falling back to your alternate network configuration which has only a good IP. People some times follow the Security manual for wireless which says "don't allow DHCP via wireless" but forget to manually supply DNS and other IP parameters manually on the alternative configuration.
