Page 1 of 1 1
Topic Options
#12924 - 2001-10-05 09:54 PM Determing Netware Connectivity
Anonymous
Unregistered


I'm trying to determine if my client workstations (9x and w2K) are logging into a Netware or NT server. We have a mixed environment and depending on which system they logon to then we want a particular anti-virus program to run. I can search for certain know reg keys or dll's for each type of client (Novell32 clients), but I'm hoping for something more definitive to tell me they are actually connected or authenticated to a Novell server or an NT server.

Thanks in advance,

Top
#12925 - 2001-10-06 11:35 AM Re: Determing Netware Connectivity
Jochen Administrator Offline
KiX Supporter
*****

Registered: 2000-03-17
Posts: 6380
Loc: Stuttgart, Germany
Hiya,

dunno if this is actually working ( dunno if you can run a kixscript on Novell login ) , but what about evaluating the @lserver macro , so maybe you can at least divide by server names !

hth b. really dunno

Jochen

_________________________



Top
#12926 - 2001-10-06 03:57 PM Re: Determing Netware Connectivity
Les Offline
KiX Master
*****

Registered: 2001-06-11
Posts: 12734
Loc: fortfrances.on.ca
I've been grappling with this question... trying to comprehend how you're implementing the logon/login. My first thought... can't you tell from the logon/login script what you're logging on/in to?

How do you setup the GINA? MSGINA or NWGINA? Do users login or attach to NetWare? What if they logon/login to both?

I suppose you should be able to do an If Exist() on a NetWare and NT share to determine connectivity. One needs to be careful, because the OS may restore a connection, so you wouldn't be able to tell if you logged in or attached.

What about drive mappings. Would they not be specific to where you logon/login?

Then there's the search mappings that NetWare does. They would only exist if logged in to NetWare. Call a utility from that search path, and if it returns "not found" you're not logged in.

_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.

Top
#12927 - 2001-10-08 04:41 PM Re: Determing Netware Connectivity
Anonymous
Unregistered


I like the idea of checking for a utility to verify if Netware is connected. How does one determine the search mappings of a particular client? Isn't this done via the logon script or the added to the autoexec?

My clients can be logging into a Netware server and NT server (they get logon scripts from both Netware and NT), or they might be logging in only to an NT server (and getting just the NT logon script). If they get the Novell logon script they get the anti-virus program, if they logon onto both, then I don't want them to run it twice, of they logon to just the NT server, then I want to be sure they are not currently connected to Netware (meaning they haven't run the Novell script) and then I will let the NT logon script run the anti-virus program.

Top
#12928 - 2001-10-08 05:49 PM Re: Determing Netware Connectivity
Les Offline
KiX Master
*****

Registered: 2001-06-11
Posts: 12734
Loc: fortfrances.on.ca
Your problem is not unlike the age old chicken and egg argument. Which came first? If you are not in control of your environment, you cannot know whether the NT script or NetWare script comes first or if the other will even follow. So then how can you determine what you're logged in/on to from within either script?

The only way to know for sure (maybe) is if you stuff another script into the RunOnce key in the registry. That script will only run after the other scripts have completed, the 'maybe' caveat being the RunLogonScriptSync setting.

You don't say how they get the anti-virus program or what it is. Is it something that gets installed or is it just run from the network? If it gets installed, then just test to see if it has been installed. With today's viruses you would be remiss to not have realtime virus protection installed. I would discourage scans during login/logon. They encourage users to stay logged in/on as long as possible.

_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.

Top
#12929 - 2001-10-08 06:25 PM Re: Determing Netware Connectivity
Anonymous
Unregistered


Anti-Virus is a Cheyenne update program that runs from the network to verify that the client has the most current .dat files.
Top
Page 1 of 1 1


Moderator:  Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart 
Hop to:
Shout Box

Who's Online
0 registered and 1821 anonymous users online.
Newest Members
ManuvdWielNL, Sir_Barrington, batdk82, StuTheCoder, M_Moore
17887 Registered Users

Generated in 0.061 seconds in which 0.03 seconds were spent on a total of 12 queries. Zlib compression enabled.

Search the board with:
superb Board Search
or try with google:
Google
Web kixtart.org