Re: XP, WIFI and Server 2000
From: Ross Mccullough (blakmoon91_at_hotmail.com)
Date: 07/12/04
- Next message: Jonathan Maltz [MS-MVP]: "Re: Win 2K3 server going down"
- Previous message: Lakshman: "Re: Win 2K3 server going down"
- In reply to: Jason Aspinall: "Re: XP, WIFI and Server 2000"
- Next in thread: Jason Aspinall: "Re: XP, WIFI and Server 2000"
- Reply: Jason Aspinall: "Re: XP, WIFI and Server 2000"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 12 Jul 2004 00:56:28 -0400
Jason Aspinall wrote:
> "Jason Aspinall" <fakemail@nowhere.con> wrote in message
> news:OpMUZvRXEHA.128@TK2MSFTNGP10.phx.gbl...
>
>>Ok.. I have a user on the lan running an XP Pro box, connected via a
>
> Buffalo
>
>>WiFi link (stop laughing at the back!) all works fine peer to peer...
>>However, upon trying to join his workstation to the "new" Win2k server, I
>>can see the domain as he's logged in, upon rebooting the machine to then
>
> log
>
>>into the Win2k server, it's then claimed his profile and home paths cannot
>>be located... He eventually, after a lot of computer umming and ahhing,
>
> ends
>
>>up with a default desktop.
>>
>>However, his profile works sweet as a nut should he decide to log in using
>>his account details on a wired workstation to the LAN...
>>
>>Something tells me his authentication is failing along the way as the
>>machine wakes up and interogates the LAN for servers... While his
>>particular workstation if push come to shove could be wired back the the
>>LAN, I have another nine wifi workstations that will need authentication
>
> to
>
>>the Win2k server in the next few weeks...
>>
>>Where should I start looking to resolve this issue?
>
>
> *BUMP*
>
> Anyone have an inkling of an idea on this?
>
>
Jason,
Hopefully can give you some guidance on some of these issues drawing
from what I found put together roaming profiles on a windows 2003 server
and windows xp pro clients. Typically on a Wireless comp your wi-fi
(unless you are using Centrino or something along those lines) uses
drivers that do not load in time to pull down the user rights and
desktops from the server. Typically this is resolved by making services
such as the netlogon dependent on another network service which will
force it to "wait" until a network connection has been established
before hitting the time limit. Another great place to look would be in
the client event viewer, using those event id go to someplace such as
eventid.net to look them up, should give you the direction to at least
help isolate the problem. Please post back if you don't have any luck.
Ross
- Next message: Jonathan Maltz [MS-MVP]: "Re: Win 2K3 server going down"
- Previous message: Lakshman: "Re: Win 2K3 server going down"
- In reply to: Jason Aspinall: "Re: XP, WIFI and Server 2000"
- Next in thread: Jason Aspinall: "Re: XP, WIFI and Server 2000"
- Reply: Jason Aspinall: "Re: XP, WIFI and Server 2000"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|