OK, this is a strange beast to be sure. And before anyone starts flaming me (no names, but I've been reading the posts in the forum from someone whose screen name begins ands ends with P), I *am* an intelligent person who does his homework, been a CNE from 3.10 days, generally knows (and loves) NW. 'k?
Alright here's the scenario:
Brand new WinXP SP2 computer, no hotfixes or programs installed, squeaky clean right out of the box. Windows Firewall is disabled. Installed Client 32, v4.9 SP2, IPX/bindery only, hard set the frame type on the NIC to 802.3. The workstation is in workgroup mode (not part of a domain). When I have this configuration, I have no problem attaching/authenticating to the NetWare 3.2 server and running the login script - life is good.
If I join the workstation to a Win2K3 SBS AD domain, when I come back from the reboot, I can still attach/authenticate to the NW server, but it refuses to run the login script. I do get the default F:=SYS: and Z:=PUBLIC. From Exploder/Explorer, I can see and manually map any drive/directory I have rights to. No rights issues.
If I leave the AD domain, I immediately start running scripts again.
If I do the same scenario to a PC with XP SP1, I do not experience this phenomenon. I have tried it with desktops and laptops. I have tried Client32 v4.83 SP2 (or 3, I forget. The stable one.) I have not been able to try this with a Win2K AD domain (just in case there's something magical about 2K3 SBS AD). I cannot seem to find any hits on Google or Novell for this. Does anyone have any clues? Anyone ever seen this before?
Any positive input is welcome,