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?

TIA

--
Jason Aspinall
Replies to group please, duff email used to combat spam.
SPAM: I don't like the stuff so stop sending me it!