My thinking is that maybe when logged into Windows computer (not domain), my pc is able to conncect to the access point. But when logging into windows, the wireless card i have isnt connecting to the access point. And will only connect when the workstation is on. Is that wrong thinking?
The way you've stated your question is more than a bit unclear, but if this is of any help:
I have a very similar setup (Netgear RT314 router, Linksys WAP11 access point, 1 DC and 3 workstations wired to RT314, 1 laptop connecting via WAP11), and I have no issues related to the access point in terms of Domain vs. Wokstation logons on the laptop.
1. On the workstation, can you log on to the domain under other valid domain user accounts, or do you get the "domain unavailable" messages regardless of which account you try?
2. Do the event/system logs on either the workstaion or the DC contain any messages/errors that might give us more specific clues as to the "domain unavailable" error?
3. What exact versions of Windows are involved here?
4. Double/triple check the network-related settings on the workstation for errors or omissions.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
1. The "Welcome to the domain" message is a bit premature; it basically means that the workstation has been readied to join the domain, but the actual changes in your configurations won't happen until the reboot.
2. Double-check your setups for the workstation and user accounts on the DC.
3. I know this may seem redundant, but can you please walk through the procedures described in the following link and let us know the results. If you encounter any errors/problems during the procedure, please tell us exactly what they are and where in the process they occur:
http://www.wown.com/j_helmig/wxpjoind.htm
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
Or since i have several available wireless networks, its not choosing "my WAP" thus not finding the domain..
Oh well crikey, if you'd saidthat in the first place.... :)
Obviously- if you have more than one wifi network available and your computer decides to connect to a network other than the one associated with your domain's network, you are going to have problems. This is actually fairly common when people who use wireless connections are in areas where multiple wifi networks of sufficient signal-strength are available- the computer may just jump onto the first available network it finds. If the network is open/unsecured and your computer is configured for DHCP, you might never notice the difference unless you checked your WiFi card's status utility to see which specific network you were actually on.
Try this for starters, if the computer in question has an Ethernet connection:
1. Disable the Wireless connection on the computer.
2. Enable the Ethernet connection and make sure it's set for DHCP.
3. Connect the computer directly to the router using an Ethernet cable and see if you join the domain.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
Give us the exact makes/model numbers of your Wifi/network devices. Each of those devices have their own config utilities; if we know which exact devices you have we can give you specific instructions on how to configure them to connect properly.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
Sorry I couldn't respond earlier, but I'm glad you got it sorted.
Actually, what you encountered isn't too uncommon on XP systems. XP's own Wireless Zero Configuration utility can often conflict/contend with the manufacturer-supplied install/config utilities that come with WiFi NICS. The instructions for some NICs say to disable Wireless Zero before installing, while others will tell you to install the NIC using Windows' Found New Hardware and Wireless Zero utilities; go figure. For your particular model of Negear card, they mention a bit about this at the beginning of chapter 3 of the full User's Manual .
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370