• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

OS/2 tries to map Printer and File Share resource on Domain Controller - why?

Started by halgorithm, 2008.11.04, 01:25:03

Previous topic - Next topic

halgorithm

Everything works, but this is annoying me and my users...

When the machine starts up, it launches requester service (since it's needed to talk to Windows file share) and I'm finding before I need to put in credentials for a file share I'm mapping to manually (via NET USE), OS/2 wants to map this 'LS' for network and printer file resources.  It wants to do this with a username and password prompt that is different than others I have seen, which has never worked any username or password I know.  We have just been cancelling it and then using the other domain logon prompt, which has always worked and maps a network drive successfully.

My question - How do I prevent this LS prompt from coming up?  I've tried digging through the ibmlan.ini file and thought I configured it properly.  I must have missed something. Is it even in this area to configure the change to stop this LS prompt?  LS isn't even the workgroup name or domain name, so I'm at a loss.

I'm guessing that when OS/2 is talking to the DC and then it 'sees' a guest share for, let's say like a default share for all users, that it wants to map to this guest share and comes up with a prompt - which i don't want to log into and doesn't work with any known userid/password.  I would rather not see this and only have the logon to domain prompt when I manually launch the NET USE command to the DC.

Any ideas?  Attaching the IBMLAN file.  What I can't figure out is that it says there are 40 config options, but there are 42 characters in the wrkheuristics line.

RobertM

Hi,

You have a couple options.
(1) Log on first

(2) Write a simple script that logs on the machine at startup. Add it to the startup.cmd script (at the end).

You can also then connect to your shares in the same script.

Doing a commandline login is easy. Simply use the logon command. The parameters are somewhat explained by typing:

logon /?

at a command prompt. Of primary interest are the switches for logging into a domain.

Thus your completed script will look something like this:

logon (parameters)
Net use (parameters)
Net use (parameters)
(etc)

Viola! That is all there is to it.




Thus, to log onto a domain, you would use the logon command like this:

logon username /P:password /d:DOMAIN

(if /D:DOMAIN does not work, try /V:DOMAIN)





As for the weird prompt, OS/2 allows logging in either via a domain (or domains), or via a workgroup (as coded in the INI files). It usually is managed by the same login window - but depending on what parameter is sent, it creates the dialog box differently. If you are only getting a prompt for username and password, it is defaulting to workgroup login. If you are getting a weird, very long dialog box (very long in comparison to the standard domain and workgroup ones), it's a holdover login box or parameter variant. In either way, it's no big deal, as logging in before (via the script ot the login icon) assigning the shares will ensure that you do not see it.

If that doesnt help, or you are not sure where or how to put the script call, let me know...

Robert



|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


halgorithm

In the startup.cmd file right after the reqeuster service, I call the login.bat script that does the

LOGON /V:D /D:ABC
NET USE K: \\server\share
NET USE LPT1 \\server\printer

and then I get the proper login prompt as I want (aka just like the NET USE prompt, because if I do this it works)

Yeah, the very long / tall prompt I'd just like to squelch and not have to see it.  I found out yesterday when I went into the ibmlan.ini and changed the DOMAIN = ABC variable to something else, it compes up in the long and tall dialog prompt box with that domain...

So yes, it looks like it is something inside of the ibmlan.ini or somwhere else and the local os/2 machine is trying to authenticate as itself to the domain.  So you're right Rob with the fact that it's probably set to default with workgroup logon and I can change this and it will stop this annoying prompt?  I'm going to go and give it a try really quick-like and get back.

RobertM

Hi halgorithm,

First, you can name OS/2 batch files using the .cmd extension instead of the .bat extension (.cmd is the default for OS/2 batch files)



You can simplify things a little (to avoid the login prompt entirely) - if you desire to. Simply insert the username and password (see example below) into the logon line in the batch file.

LOGON USERNAME /P:PASSWORD /D:ABC

Just keep in mind, it does leave the username and password viewable to anyone with access to that file. With HPFS386 installed, and Local ACLs enabled, such is avoidable. Preface the command with the @ symbol, save the file, and make it only readable for logins under a certain account (requires setting the access rights on the file either manually, or to whatever directory the script file is in. If you set it by directoy, ensure that other files in that directory do not need to be readable by others and can also be secured using the same schema).




As for the odd login box, I am at a loss to find it (or replicate it) with a proper domain name set in the INI files. Otherwise, simply use the method above or below.




More information can be found in OS/2's help files... at a command prompt, type:
  HELP LOGON

Or, open the Help Viewer (or Assistance Center) and find the Command Reference.

Let us know how things go.

Thanks,
Robert


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


Pete

Hi

Just wondering if you have a (Domain) logon in the Startup folder? - or, possibly, slighlty munged ini files that "think" you have a logon in the Startup folder. Might be worth a run with checkini from the WPTools package.

Regards

Pete

halgorithm

Slightly munged ini files?  ???  Sorry, I'm not understanding you completely.

I've removed all startup items from the Startup folder in the WPS and my startup.cmd calls my other logon, which the first thing after the Requester services launches is it authenticates wtih the domain.  This window is expected; however, my original posting referrs to a window that opens when the Requester service launches, it's almost as if the requester service itself is trying to authenticate with the domain, but it incorrectly does so.  THAT was the dialog box I wanted to separate from the Domain authentication logon.  Here, next time I've got a momento (between this and Vista support) I'll take some screenshots of what I'm talking about in my virtual pc, that is if it comes up on that thing. 

I think it really has something to do with the protocol.ini file or some sort of config, but I can't determine this.  It may even have something to do with the way OS2 talk to a Windows 2k3 server or a default file share and it wants to authenticate.  I have no idea really.