Issues mapping network drive via login script

I have a couple of computers that are having issues mapping their network
drives. I have login scripts assigned to the domain users via the Profile
tab of their AD account. For some reason, when a couple of the users log in,
I don't think that the script runs, or if it does, the drives just don't map.
I've looked into DNS issues and such, but can't find anything out of the
ordinary. Everything looks the same, and all other users' login scripts
appear to be working accordingly. One of the users apparently had to shut
the PC off completely and reboot and then it mapped correctly. One thing to
note - you can run the script manually after logging in and it will work just
fine (by going to \\domaincontroller\netlogon and executing it from there) -
user didn't know how to do this, thus they shut it down.

Does anyone know of any issues that could prevent the login scripts from
working properly upon logon?

Thanks in advance!

Sara

Is there more than one domain controller?


"Saral6978" <Saral6978@discussions.microsoft.com> wrote in message
news:55F43416-3341-451A-928D-CB3F371E7555@microsoft.com...
>I have a couple of computers that are having issues mapping their network
> drives. I have login scripts assigned to the domain users via the Profile
> tab of their AD account. For some reason, when a couple of the users log
> in,
> I don't think that the script runs, or if it does, the drives just don't
> map.
> I've looked into DNS issues and such, but can't find anything out of the
> ordinary. Everything looks the same, and all other users' login scripts
> appear to be working accordingly. One of the users apparently had to shut
> the PC off completely and reboot and then it mapped correctly. One thing
> to
> note - you can run the script manually after logging in and it will work
> just
> fine (by going to \\domaincontroller\netlogon and executing it from
> there) -
> user didn't know how to do this, thus they shut it down.
>
> Does anyone know of any issues that could prevent the login scripts from
> working properly upon logon?
>
> Thanks in advance!
>
> Sara

At that particular site, no. But, we have a total of 4. Replication is
working correctly between the DCs. The clients look to their local DC for
authentication, etc.


"Joe Grover" wrote:

> Is there more than one domain controller?
>
>
> "Saral6978" <Saral6978@discussions.microsoft.com> wrote in message
> news:55F43416-3341-451A-928D-CB3F371E7555@microsoft.com...
> >I have a couple of computers that are having issues mapping their network
> > drives. I have login scripts assigned to the domain users via the Profile
> > tab of their AD account. For some reason, when a couple of the users log
> > in,
> > I don't think that the script runs, or if it does, the drives just don't
> > map.
> > I've looked into DNS issues and such, but can't find anything out of the
> > ordinary. Everything looks the same, and all other users' login scripts
> > appear to be working accordingly. One of the users apparently had to shut
> > the PC off completely and reboot and then it mapped correctly. One thing
> > to
> > note - you can run the script manually after logging in and it will work
> > just
> > fine (by going to \\domaincontroller\netlogon and executing it from
> > there) -
> > user didn't know how to do this, thus they shut it down.
> >
> > Does anyone know of any issues that could prevent the login scripts from
> > working properly upon logon?
> >
> > Thanks in advance!
> >
> > Sara
>
>

"Saral6978" <Saral6978@discussions.microsoft.com> wrote in message
news:55F43416-3341-451A-928D-CB3F371E7555@microsoft.com...
> I have a couple of computers that are having issues mapping their network
> drives. I have login scripts assigned to the domain users via the Profile
> tab of their AD account. For some reason, when a couple of the users log
in,
> I don't think that the script runs, or if it does, the drives just don't
map.
> I've looked into DNS issues and such, but can't find anything out of the
> ordinary. Everything looks the same, and all other users' login scripts
> appear to be working accordingly. One of the users apparently had to shut
> the PC off completely and reboot and then it mapped correctly. One thing
to
> note - you can run the script manually after logging in and it will work
just
> fine (by going to \\domaincontroller\netlogon and executing it from
there) -
> user didn't know how to do this, thus they shut it down.
>
> Does anyone know of any issues that could prevent the login scripts from
> working properly upon logon?
>
> Thanks in advance!
>
> Sara

You write "I don't think that the script runs". You must nail this one
down as your first step by modifying your script like so:
@echo off
echo This is the login script
echo %date% %time% %UserName% >> c:\Login.txt
ping localhost -n 5
{Put your own lines of code here}

This will have two effects:
- The logon process will generate a screen message and
pause for a moment.
- It will create a log entry in c:\Login.txt.

Thank you, Pegasus...I will give that a try to confirm.

"Pegasus (MVP)" wrote:

>
> "Saral6978" <Saral6978@discussions.microsoft.com> wrote in message
> news:55F43416-3341-451A-928D-CB3F371E7555@microsoft.com...
> > I have a couple of computers that are having issues mapping their network
> > drives. I have login scripts assigned to the domain users via the Profile
> > tab of their AD account. For some reason, when a couple of the users log
> in,
> > I don't think that the script runs, or if it does, the drives just don't
> map.
> > I've looked into DNS issues and such, but can't find anything out of the
> > ordinary. Everything looks the same, and all other users' login scripts
> > appear to be working accordingly. One of the users apparently had to shut
> > the PC off completely and reboot and then it mapped correctly. One thing
> to
> > note - you can run the script manually after logging in and it will work
> just
> > fine (by going to \\domaincontroller\netlogon and executing it from
> there) -
> > user didn't know how to do this, thus they shut it down.
> >
> > Does anyone know of any issues that could prevent the login scripts from
> > working properly upon logon?
> >
> > Thanks in advance!
> >
> > Sara
>
> You write "I don't think that the script runs". You must nail this one
> down as your first step by modifying your script like so:
> @echo off
> echo This is the login script
> echo %date% %time% %UserName% >> c:\Login.txt
> ping localhost -n 5
> {Put your own lines of code here}
>
> This will have two effects:
> - The logon process will generate a screen message and
> pause for a moment.
> - It will create a log entry in c:\Login.txt.
>
>
>

I am having the same issue also , 1 out of the 30 PC's that run a script will
not connect to its mapped drives.
I watch the script run when the PC is booted up but when its finished the
drives do not connect, a reboot usually fixes the problem otherwis ei have
to remapp the drives every morning( it actually worked right yesterday for
the first time in a week) and i hadnt made any changes to anything.
very confused
thanks
scott


"Pegasus (MVP)" wrote:

>
> "Saral6978" <Saral6978@discussions.microsoft.com> wrote in message
> news:55F43416-3341-451A-928D-CB3F371E7555@microsoft.com...
> > I have a couple of computers that are having issues mapping their network
> > drives. I have login scripts assigned to the domain users via the Profile
> > tab of their AD account. For some reason, when a couple of the users log
> in,
> > I don't think that the script runs, or if it does, the drives just don't
> map.
> > I've looked into DNS issues and such, but can't find anything out of the
> > ordinary. Everything looks the same, and all other users' login scripts
> > appear to be working accordingly. One of the users apparently had to shut
> > the PC off completely and reboot and then it mapped correctly. One thing
> to
> > note - you can run the script manually after logging in and it will work
> just
> > fine (by going to \\domaincontroller\netlogon and executing it from
> there) -
> > user didn't know how to do this, thus they shut it down.
> >
> > Does anyone know of any issues that could prevent the login scripts from
> > working properly upon logon?
> >
> > Thanks in advance!
> >
> > Sara
>
> You write "I don't think that the script runs". You must nail this one
> down as your first step by modifying your script like so:
> @echo off
> echo This is the login script
> echo %date% %time% %UserName% >> c:\Login.txt
> ping localhost -n 5
> {Put your own lines of code here}
>
> This will have two effects:
> - The logon process will generate a screen message and
> pause for a moment.
> - It will create a log entry in c:\Login.txt.
>
>
>

Glad I'm not the only one! I'm actually going to start working on this
again tonight to see what I can figure out. I had to put this on hold for a
bit to work on some other things, but the user is still complaining of the
drives not mapping unless she shuts down and reboots again, or runs the
script manually. So, I'll finally get to do some testing and to confirm that
indeed the script is executing properly. There are a few things that I will
be looking at that could be causing some issues (network related). I'll let
you know if I find a solution!

Sara

"Scott" wrote:

> I am having the same issue also , 1 out of the 30 PC's that run a script will
> not connect to its mapped drives.
> I watch the script run when the PC is booted up but when its finished the
> drives do not connect, a reboot usually fixes the problem otherwis ei have
> to remapp the drives every morning( it actually worked right yesterday for
> the first time in a week) and i hadnt made any changes to anything.
> very confused
> thanks
> scott
>
>
> "Pegasus (MVP)" wrote:
>
> >
> > "Saral6978" <Saral6978@discussions.microsoft.com> wrote in message
> > news:55F43416-3341-451A-928D-CB3F371E7555@microsoft.com...
> > > I have a couple of computers that are having issues mapping their network
> > > drives. I have login scripts assigned to the domain users via the Profile
> > > tab of their AD account. For some reason, when a couple of the users log
> > in,
> > > I don't think that the script runs, or if it does, the drives just don't
> > map.
> > > I've looked into DNS issues and such, but can't find anything out of the
> > > ordinary. Everything looks the same, and all other users' login scripts
> > > appear to be working accordingly. One of the users apparently had to shut
> > > the PC off completely and reboot and then it mapped correctly. One thing
> > to
> > > note - you can run the script manually after logging in and it will work
> > just
> > > fine (by going to \\domaincontroller\netlogon and executing it from
> > there) -
> > > user didn't know how to do this, thus they shut it down.
> > >
> > > Does anyone know of any issues that could prevent the login scripts from
> > > working properly upon logon?
> > >
> > > Thanks in advance!
> > >
> > > Sara
> >
> > You write "I don't think that the script runs". You must nail this one
> > down as your first step by modifying your script like so:
> > @echo off
> > echo This is the login script
> > echo %date% %time% %UserName% >> c:\Login.txt
> > ping localhost -n 5
> > {Put your own lines of code here}
> >
> > This will have two effects:
> > - The logon process will generate a screen message and
> > pause for a moment.
> > - It will create a log entry in c:\Login.txt.
> >
> >
> >

thanks that would be great
today it mapped 2 out of the 5 drives, so who knows what tommorow will bring.

thanks
scott

"Saral6978" wrote:

> Glad I'm not the only one! I'm actually going to start working on this
> again tonight to see what I can figure out. I had to put this on hold for a
> bit to work on some other things, but the user is still complaining of the
> drives not mapping unless she shuts down and reboots again, or runs the
> script manually. So, I'll finally get to do some testing and to confirm that
> indeed the script is executing properly. There are a few things that I will
> be looking at that could be causing some issues (network related). I'll let
> you know if I find a solution!
>
> Sara
>
> "Scott" wrote:
>
> > I am having the same issue also , 1 out of the 30 PC's that run a script will
> > not connect to its mapped drives.
> > I watch the script run when the PC is booted up but when its finished the
> > drives do not connect, a reboot usually fixes the problem otherwis ei have
> > to remapp the drives every morning( it actually worked right yesterday for
> > the first time in a week) and i hadnt made any changes to anything.
> > very confused
> > thanks
> > scott
> >
> >
> > "Pegasus (MVP)" wrote:
> >
> > >
> > > "Saral6978" <Saral6978@discussions.microsoft.com> wrote in message
> > > news:55F43416-3341-451A-928D-CB3F371E7555@microsoft.com...
> > > > I have a couple of computers that are having issues mapping their network
> > > > drives. I have login scripts assigned to the domain users via the Profile
> > > > tab of their AD account. For some reason, when a couple of the users log
> > > in,
> > > > I don't think that the script runs, or if it does, the drives just don't
> > > map.
> > > > I've looked into DNS issues and such, but can't find anything out of the
> > > > ordinary. Everything looks the same, and all other users' login scripts
> > > > appear to be working accordingly. One of the users apparently had to shut
> > > > the PC off completely and reboot and then it mapped correctly. One thing
> > > to
> > > > note - you can run the script manually after logging in and it will work
> > > just
> > > > fine (by going to \\domaincontroller\netlogon and executing it from
> > > there) -
> > > > user didn't know how to do this, thus they shut it down.
> > > >
> > > > Does anyone know of any issues that could prevent the login scripts from
> > > > working properly upon logon?
> > > >
> > > > Thanks in advance!
> > > >
> > > > Sara
> > >
> > > You write "I don't think that the script runs". You must nail this one
> > > down as your first step by modifying your script like so:
> > > @echo off
> > > echo This is the login script
> > > echo %date% %time% %UserName% >> c:\Login.txt
> > > ping localhost -n 5
> > > {Put your own lines of code here}
> > >
> > > This will have two effects:
> > > - The logon process will generate a screen message and
> > > pause for a moment.
> > > - It will create a log entry in c:\Login.txt.
> > >
> > >
> > >

Okay, this might be a dumb suggestion, but I've overlooked this in the past:
The computer that is not mapping the drives - does it have any of those
removable media slots or anything that is already using the drive letter that
is attempting to be mapped? If the drive letter is being used already, then
the script will not be able to map the network drive assigned to that same
letter. I've had to go in and change the removable media slots, or
CD/DVDROMs in Disk Management so that my script could actually map the drive
successfully...I don't know, just a suggestion in case you might have
overlooked it...

I only suggest this since you mentioned 2 of the 5 mapped okay...my user
gets zero mapped drives.

Sara

"Scott" wrote:

> thanks that would be great
> today it mapped 2 out of the 5 drives, so who knows what tommorow will bring.
>
> thanks
> scott
>
> "Saral6978" wrote:
>
> > Glad I'm not the only one! I'm actually going to start working on this
> > again tonight to see what I can figure out. I had to put this on hold for a
> > bit to work on some other things, but the user is still complaining of the
> > drives not mapping unless she shuts down and reboots again, or runs the
> > script manually. So, I'll finally get to do some testing and to confirm that
> > indeed the script is executing properly. There are a few things that I will
> > be looking at that could be causing some issues (network related). I'll let
> > you know if I find a solution!
> >
> > Sara
> >
> > "Scott" wrote:
> >
> > > I am having the same issue also , 1 out of the 30 PC's that run a script will
> > > not connect to its mapped drives.
> > > I watch the script run when the PC is booted up but when its finished the
> > > drives do not connect, a reboot usually fixes the problem otherwis ei have
> > > to remapp the drives every morning( it actually worked right yesterday for
> > > the first time in a week) and i hadnt made any changes to anything.
> > > very confused
> > > thanks
> > > scott
> > >
> > >
> > > "Pegasus (MVP)" wrote:
> > >
> > > >
> > > > "Saral6978" <Saral6978@discussions.microsoft.com> wrote in message
> > > > news:55F43416-3341-451A-928D-CB3F371E7555@microsoft.com...
> > > > > I have a couple of computers that are having issues mapping their network
> > > > > drives. I have login scripts assigned to the domain users via the Profile
> > > > > tab of their AD account. For some reason, when a couple of the users log
> > > > in,
> > > > > I don't think that the script runs, or if it does, the drives just don't
> > > > map.
> > > > > I've looked into DNS issues and such, but can't find anything out of the
> > > > > ordinary. Everything looks the same, and all other users' login scripts
> > > > > appear to be working accordingly. One of the users apparently had to shut
> > > > > the PC off completely and reboot and then it mapped correctly. One thing
> > > > to
> > > > > note - you can run the script manually after logging in and it will work
> > > > just
> > > > > fine (by going to \\domaincontroller\netlogon and executing it from
> > > > there) -
> > > > > user didn't know how to do this, thus they shut it down.
> > > > >
> > > > > Does anyone know of any issues that could prevent the login scripts from
> > > > > working properly upon logon?
> > > > >
> > > > > Thanks in advance!
> > > > >
> > > > > Sara
> > > >
> > > > You write "I don't think that the script runs". You must nail this one
> > > > down as your first step by modifying your script like so:
> > > > @echo off
> > > > echo This is the login script
> > > > echo %date% %time% %UserName% >> c:\Login.txt
> > > > ping localhost -n 5
> > > > {Put your own lines of code here}
> > > >
> > > > This will have two effects:
> > > > - The logon process will generate a screen message and
> > > > pause for a moment.
> > > > - It will create a log entry in c:\Login.txt.
> > > >
> > > >
> > > >

Scott,

Please ignore my above post - I forgot that you mentioned sometimes all the
drives work and sometimes not...I would delete it if I could, but oh well!

If it sometimes works, then there obviously is no drive letter conflicts.

Sorry!

Sara





"Saral6978" wrote:

> Okay, this might be a dumb suggestion, but I've overlooked this in the past:
> The computer that is not mapping the drives - does it have any of those
> removable media slots or anything that is already using the drive letter that
> is attempting to be mapped? If the drive letter is being used already, then
> the script will not be able to map the network drive assigned to that same
> letter. I've had to go in and change the removable media slots, or
> CD/DVDROMs in Disk Management so that my script could actually map the drive
> successfully...I don't know, just a suggestion in case you might have
> overlooked it...
>
> I only suggest this since you mentioned 2 of the 5 mapped okay...my user
> gets zero mapped drives.
>
> Sara
>
> "Scott" wrote:
>
> > thanks that would be great
> > today it mapped 2 out of the 5 drives, so who knows what tommorow will bring.
> >
> > thanks
> > scott
> >
> > "Saral6978" wrote:
> >
> > > Glad I'm not the only one! I'm actually going to start working on this
> > > again tonight to see what I can figure out. I had to put this on hold for a
> > > bit to work on some other things, but the user is still complaining of the
> > > drives not mapping unless she shuts down and reboots again, or runs the
> > > script manually. So, I'll finally get to do some testing and to confirm that
> > > indeed the script is executing properly. There are a few things that I will
> > > be looking at that could be causing some issues (network related). I'll let
> > > you know if I find a solution!
> > >
> > > Sara
> > >
> > > "Scott" wrote:
> > >
> > > > I am having the same issue also , 1 out of the 30 PC's that run a script will
> > > > not connect to its mapped drives.
> > > > I watch the script run when the PC is booted up but when its finished the
> > > > drives do not connect, a reboot usually fixes the problem otherwis ei have
> > > > to remapp the drives every morning( it actually worked right yesterday for
> > > > the first time in a week) and i hadnt made any changes to anything.
> > > > very confused
> > > > thanks
> > > > scott
> > > >
> > > >
> > > > "Pegasus (MVP)" wrote:
> > > >
> > > > >
> > > > > "Saral6978" <Saral6978@discussions.microsoft.com> wrote in message
> > > > > news:55F43416-3341-451A-928D-CB3F371E7555@microsoft.com...
> > > > > > I have a couple of computers that are having issues mapping their network
> > > > > > drives. I have login scripts assigned to the domain users via the Profile
> > > > > > tab of their AD account. For some reason, when a couple of the users log
> > > > > in,
> > > > > > I don't think that the script runs, or if it does, the drives just don't
> > > > > map.
> > > > > > I've looked into DNS issues and such, but can't find anything out of the
> > > > > > ordinary. Everything looks the same, and all other users' login scripts
> > > > > > appear to be working accordingly. One of the users apparently had to shut
> > > > > > the PC off completely and reboot and then it mapped correctly. One thing
> > > > > to
> > > > > > note - you can run the script manually after logging in and it will work
> > > > > just
> > > > > > fine (by going to \\domaincontroller\netlogon and executing it from
> > > > > there) -
> > > > > > user didn't know how to do this, thus they shut it down.
> > > > > >
> > > > > > Does anyone know of any issues that could prevent the login scripts from
> > > > > > working properly upon logon?
> > > > > >
> > > > > > Thanks in advance!
> > > > > >
> > > > > > Sara
> > > > >
> > > > > You write "I don't think that the script runs". You must nail this one
> > > > > down as your first step by modifying your script like so:
> > > > > @echo off
> > > > > echo This is the login script
> > > > > echo %date% %time% %UserName% >> c:\Login.txt
> > > > > ping localhost -n 5
> > > > > {Put your own lines of code here}
> > > > >
> > > > > This will have two effects:
> > > > > - The logon process will generate a screen message and
> > > > > pause for a moment.
> > > > > - It will create a log entry in c:\Login.txt.
> > > > >
> > > > >
> > > > >