Xp Pro, Wireless and Domains

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
We are a college who have just brought a Netgear wireless AP and are
attempting to connect to this with a win xp pro pc, The problem we are
getting is that the pc will not log into the domain from boot instead we must
login locally and allow the wireless zero config or netgear program to start
before we can access the network, as you can imagine getting the staff to
login twice and in 2 differant ways is nigh on impossible so if anyone can
suggest a way to get the login on the first attempt will be appreciated (we
have tried static ip on the pc and have also desabled the xp firewall)

Thanks

Phil
 
Not sure the issue, but I think you may need to create the same username of the domain.

troubleshooting is not accessible error "....is not accessible. You may not have permission to use this network resource". "Access is denied" · "Network path was not found." ...
www.howtonetworking.com/Troubleshooting/notaccessibale0.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Hi,
We are a college who have just brought a Netgear wireless AP and are
attempting to connect to this with a win xp pro pc, The problem we are
getting is that the pc will not log into the domain from boot instead we must
login locally and allow the wireless zero config or netgear program to start
before we can access the network, as you can imagine getting the staff to
login twice and in 2 differant ways is nigh on impossible so if anyone can
suggest a way to get the login on the first attempt will be appreciated (we
have tried static ip on the pc and have also desabled the xp firewall)

Thanks

Phil
 
This problem is fairly common and, unfortunately, has no easy solution.
Most WNICS will not connect until after the Windows logon and loading of
required drivers and services. See the link below for some discussion of
the issue and a possible solution creating a cached credential using a wired
logon.
http://www.mcse.ms/archive44-2005-11-1939438.html
 
Back
Top