Highlighted
Absent Member.
Absent Member.
2777 views

Login Script doesn't always map

Hi.

I'm seeing some strange happenings on my network. Users sign in and the login script maps correctly most of the time. However, there are sporadic occasions where the script will not map network drives, instead mapping search drives to the local hard drive. I've sat at a workstation and logged in over and over again. Most of the time it's fine, but the other times, the users aren't getting their required network drives.

These are Windows 7 Pro 64 bit workstations using NC2 SP2 on Netware 6.5 SP8. I know Client SP3 is out, but before I spend days updating clients all over my network, I want to know if anyone else has experienced something similar.

Thanks!
Labels (1)
0 Likes
20 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: Login Script doesn't always map

Sarcoxie,
> I'm seeing some strange happenings on my network. Users sign in and the
> login script maps correctly most of the time. However, there are
> sporadic occasions where the script will not map network drives, instead
> mapping search drives to the local hard drive. I've sat at a workstation
> and logged in over and over again. Most of the time it's fine, but the
> other times, the users aren't getting their required network drives.


Can you port a snippet of the script where the mappings happen?

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Login Script doesn't always map

Is that for all users or specific (group) users and/or workstations?

-- eDirectory Rules! Peter www.DreamLAN.com
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Login Script doesn't always map

This happens randomly. Computer A might work for a time, then not work, then start working again later. User A might work for a time, then not work, then start working again later. There is no rhyme or reason as to why this is happening. It's happening on wired and wireless connections at various times during the day.

Could this have anything to do with timesync? I had some timesync issues a couple of weeks ago, but thought they were all solved.

sarcoxie;2289139 wrote:
Hi.

I'm seeing some strange happenings on my network. Users sign in and the login script maps correctly most of the time. However, there are sporadic occasions where the script will not map network drives, instead mapping search drives to the local hard drive. I've sat at a workstation and logged in over and over again. Most of the time it's fine, but the other times, the users aren't getting their required network drives.

These are Windows 7 Pro 64 bit workstations using NC2 SP2 on Netware 6.5 SP8. I know Client SP3 is out, but before I spend days updating clients all over my network, I want to know if anyone else has experienced something similar.

Thanks!
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Login Script doesn't always map

Anders,

Here is a copy of the actual login script:
------------------------------
WRITE "Good %GREETING_TIME, %FULL_NAME."
WRITE "The time is %HOUR:%MINUTE %AM_PM"

NO_DEFAULT

IF MEMBER OF "EVERYONE" THEN
map f:=HS_SYS:\
map root g:=HS_APPS:\
END

IF MEMBER OF "HS_OFFICE" THEN
map root o:=HS_DATA:\HS_OFFICE
END

IF MEMBER OF "STAFF" THEN
map root i:=HS_STAFF:\%LOGIN_NAME
END

IF MEMBER OF "TECH" THEN
map root h:=HS_TECH:\
map root j:=HS_DATA:\
map root k:=HS_STUDENTS:\
map root l:=HS_STAFF:\
END

IF MEMBER OF "STUDENTS" THEN
map root i:=HS_STUDENTS:\%LOGIN_NAME
END

IF OS="WINNT" THEN
@G:\LNScrpt\Track.bat %YEAR%MONTH%DAY, %HOUR24:%MINUTE, %CN, %<USERNAME>, %<COMPUTERNAME>, %P_STATION, %OS_VERSION
END

SET NETSWEEPER_USER="%1"

#F:\public\logout.bat
#F:\public\login.bat
------------------------------

On those last few items, track.bat tracks who has logged in where. The last 3 lines (NETSWEEPER_USER, logout.bat, and login.bat) are all for my content filter. Most of the time it runs correctly and the users get all the drive mappings they need. Randomly, however, I'll get these results instead of correct mappings:
------------------------------
Your current context is HS
Your current tree is: R-2
You are attached to server HS.
Drives C,D map to a local disk.
----- Search Drives -----
S1: = C:\Program Files (x86)\Intel\iCLS Client\
S2: = C:\Program Files\Intel\iCLS Client\
S3: = C:\Windows\system32
S4: = C:\Windows
S5: = C:\Windows\System32\Wbem
S6: = C:\Windows\System32\WindowsPowerShell\v1.0\
S7: = C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
S8: = C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
S9: = C:\Program Files\Intel\Intel(R) Management Engine Components\DAL
S10: = C:\Program Files\Intel\Intel(R) Management Engine Components\IPT
S11: = C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL
S12: = C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT
------------------------------



AndersG;2289160 wrote:
Sarcoxie,
> I'm seeing some strange happenings on my network. Users sign in and the
> login script maps correctly most of the time. However, there are
> sporadic occasions where the script will not map network drives, instead
> mapping search drives to the local hard drive. I've sat at a workstation
> and logged in over and over again. Most of the time it's fine, but the
> other times, the users aren't getting their required network drives.


Can you port a snippet of the script where the mappings happen?

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Login Script doesn't always map

Sarcoxie,
> f:=HS_SYS:\


OK. And users and volumes are in the same container?

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Login Script doesn't always map

Yes. Everything is in a container called HS, which is directly under the root of a tree called R-2.

AndersG;2289474 wrote:
Sarcoxie,
> f:=HS_SYS:\


OK. And users and volumes are in the same container?

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Login Script doesn't always map

Sarcoxie,
> Yes. Everything is in a container called HS, which is directly under the
> root of a tree called R-2.


Odd. A packet trace of a failed login would be nice to see.

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Login Script doesn't always map

The problem is that I can't replicate the problem on demand. I've got a laptop sitting on my desk that I've logged in to about 50 times today. It has worked about 45 of those times. The other 5 times, it has mapped the search drives to the local disk.

AndersG;2289518 wrote:
Sarcoxie,
> Yes. Everything is in a container called HS, which is directly under the
> root of a tree called R-2.


Odd. A packet trace of a failed login would be nice to see.

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Login Script doesn't always map

Sarcoxie,
> The other 5 times, it has mapped
> the search drives to the local disk.


OK. In those cases, does the script run at all?

Also:

IF OS="WINNT" THEN
@G:\LNScrpt\Track.bat %YEAR%MONTH%DAY, %HOUR24:%MINUTE, %CN,
%<USERNAME>, %<COMPUTERNAME>, %P_STATION, %OS_VERSION
END

SET NETSWEEPER_USER="%1"

#F:\public\logout.bat
#F:\public\login.bat

What is the purpose of the last two?

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Login Script doesn't always map

On the occasion that it doesn't work, I still see the results window, but it just shows me the local search drives that it maps instead of my network drives.

Track.bat tracks who logs in where.
Logout.bat is a script that runs to clear the last user from this workstation.
Login.bat is a script that runs to attach the new user to this workstation. This is how my content filter works. It is integrated with eDirectory, so whoever logs in can be filtered differently based on the user level. Since Novell doesn't run a logout script, I had to make logout.bat run when the next user logs in, then login.bat runs directly behind it. This was all done with instructions from my content filter company.

AndersG;2289640 wrote:
Sarcoxie,
> The other 5 times, it has mapped
> the search drives to the local disk.


OK. In those cases, does the script run at all?

Also:

IF OS="WINNT" THEN
@G:\LNScrpt\Track.bat %YEAR%MONTH%DAY, %HOUR24:%MINUTE, %CN,
%<USERNAME>, %<COMPUTERNAME>, %P_STATION, %OS_VERSION
END

SET NETSWEEPER_USER="%1"

#F:\public\logout.bat
#F:\public\login.bat

What is the purpose of the last two?

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Login Script doesn't always map

OK. I know that it is a royal pain, but what I suggest is to simply
hook up wireshark. Get a trace pf a good login, save it. Then keep
logging in util it fails and grab that trace, compare.

What could be worth while is to put the new client on a few
workstations and see if the problem stops on those.

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.