allan grossman [ms-mvp]
April 21st 03, 04:12 PM
Hi, Shane -
Let's assume all the workstations are configured
correctly.
Is there a domain controller on the same subnet as the
workstations that are having problems? I believe WinXP
requires an authentication response from a DC within 5
seconds or it reverts to a cached login - which would
mean your login scripts wouldn't run.
It's worth a look - maybe someone else will have a
different idea.
Good luck!
>-----Original Message-----
>I am having an issue with about 50% of our Windows XP
Pro
>clients. We have an NT 4 domian and use Windows 98
>(phased out moving to XP Pro when leases are up) and
>Windows XP Pro. During the login process we use login
>scripts for different location and departments to map
>drives to network shares. Everything works fine for
>Windows 98 Clients and for about half of our XP Pro
>clients. When we run in to a problem is mapped drives of
>network shares on half of the XP Pro Clients, they just
>refuse to map the drives according to the script.
>
>Through testing this out we have found no relationship
or
>common cause between machines or software installs. It
is
>compeletly random and only affects XP Pro.
>
>Since some people make their own mapped drives we make
>sure the U drive is deleted each time and re
established.
>This Drive is basically the users home directory used to
>back up their files to a network share. We have tried it
>without the deletion step and have the same problems
>(some times more common).
>
>
>here is a sample of the script (bat) we are running:
>
>net time \\timeserver /set /yes
>net use e: \\server1\shareE
>net use /delete u:
>net use s: \\server2\shareS
>net use u: \\homeserver1\shareU
>
>I appreciate any help or if anyone else has seen this
>issue before.
>
>Thanks
>Shane Nicholson
>
>.
>
Let's assume all the workstations are configured
correctly.
Is there a domain controller on the same subnet as the
workstations that are having problems? I believe WinXP
requires an authentication response from a DC within 5
seconds or it reverts to a cached login - which would
mean your login scripts wouldn't run.
It's worth a look - maybe someone else will have a
different idea.
Good luck!
>-----Original Message-----
>I am having an issue with about 50% of our Windows XP
Pro
>clients. We have an NT 4 domian and use Windows 98
>(phased out moving to XP Pro when leases are up) and
>Windows XP Pro. During the login process we use login
>scripts for different location and departments to map
>drives to network shares. Everything works fine for
>Windows 98 Clients and for about half of our XP Pro
>clients. When we run in to a problem is mapped drives of
>network shares on half of the XP Pro Clients, they just
>refuse to map the drives according to the script.
>
>Through testing this out we have found no relationship
or
>common cause between machines or software installs. It
is
>compeletly random and only affects XP Pro.
>
>Since some people make their own mapped drives we make
>sure the U drive is deleted each time and re
established.
>This Drive is basically the users home directory used to
>back up their files to a network share. We have tried it
>without the deletion step and have the same problems
>(some times more common).
>
>
>here is a sample of the script (bat) we are running:
>
>net time \\timeserver /set /yes
>net use e: \\server1\shareE
>net use /delete u:
>net use s: \\server2\shareS
>net use u: \\homeserver1\shareU
>
>I appreciate any help or if anyone else has seen this
>issue before.
>
>Thanks
>Shane Nicholson
>
>.
>