beecher@cunixf.cc.columbia.edu (Ben Beecher) (06/14/91)
We have a Netware 2.15 server and a 3.11 server on the same network.
If both servers are up when I turn on my workstation I can log in to
the 3.11 server with no problems. If the 3.11 server goes down and
comes back up my workstation will be attached to the 2.15 server.
Then I log in to the 3.11 server explicitly by specifying the server
name in the login command and I get the following error message during
login:
(ELSE)
Unknown LOGIN script command.
What's going on here? If I had to guess I would say that IF-THEN-ELSE
is not supported under Netware 2.15 and when the workstation has to
reattach from the 2.15 server to the 3.11 server it doesn't know ELSE
is supported. I know it's a lousy explanation. Can someone give us
the real answer?
Ben Beecher beecher@cunixf.cc.columbia.edu
Network Planning 212-854-7439
Columbia University mjl@unix.cis.pitt.edu (Michael J Lewinter) (06/15/91)
In article <1991Jun14.155201.8284@cunixf.cc.columbia.edu> beecher@cunixf.cc.columbia.edu (Ben Beecher) writes: >We have a Netware 2.15 server and a 3.11 server on the same network. >If both servers are up when I turn on my workstation I can log in to >the 3.11 server with no problems. If the 3.11 server goes down and >comes back up my workstation will be attached to the 2.15 server. >Then I log in to the 3.11 server explicitly by specifying the server >name in the login command and I get the following error message during >login: > >(ELSE) > Unknown LOGIN script command. > >What's going on here? If I had to guess I would say that IF-THEN-ELSE [Remainder deleted] You appear to be running the LOGIN.COM program from the 2.15 Server which in your case appears not to be of the version that suports ELSE statements. For my workgroup I maintain a 'known' version of the login program on the local disk to avoid such problems. The version of login that came with the netware Windows Workstation update seems to work for both 2.15 and 3.0, your milage may vary with 3.11. Michael J. LeWinter
RBYAML@ROHVM1.BITNET (Aengus Lawlor) (06/18/91)
In article <1991Jun14.155201.8284@cunixf.cc.columbia.edu>, beecher@cunixf.cc.columbia.edu (Ben Beecher) says: > >We have a Netware 2.15 server and a 3.11 server on the same network. >If both servers are up when I turn on my workstation I can log in to >the 3.11 server with no problems. If the 3.11 server goes down and >comes back up my workstation will be attached to the 2.15 server. >Then I log in to the 3.11 server explicitly by specifying the server >name in the login command and I get the following error message during >login: > >(ELSE) > Unknown LOGIN script command. > >What's going on here? If I had to guess I would say that IF-THEN-ELSE >is not supported under Netware 2.15 and when the workstation has to >reattach from the 2.15 server to the 3.11 server it doesn't know ELSE >is supported. I know it's a lousy explanation. Can someone give us >the real answer? Are you running LOGIN.COM from your local drive, or from the first Network drive? (usually F:). You should be able replace your 2.1x version of LOGIN, on the 2.15 server, with the newer LOGIN, (but don't take my word for it!) As far as I can remember, you should replace all the PUBLIC utilities with the 3.x versions at the same time. (I got the 3.x utilities to run Windows 3.0 on our Netware for VMS network, which, as far as I'm aware, won't be upgradeable to 3.x any time soon) > >Ben Beecher beecher@cunixf.cc.columbia.edu >Network Planning 212-854-7439 >Columbia University -- RBYAML@ROHMHAAS.COM Aengus Lawlor RBYAML@ROHVM1.BITNET (who used to be ALAWLOR@DIT.IE) "How about some of that famous Dublin wit, Barman?" "Certainly, sir. Would that be Dry or Sparkling?"
orand@kuhub.cc.ukans.edu (06/18/91)
In article <91168.171213RBYAML@ROHVM1.BITNET>, Aengus Lawlor <RBYAML@ROHVM1.BITNET> writes: > In article <1991Jun14.155201.8284@cunixf.cc.columbia.edu>, > beecher@cunixf.cc.columbia.edu (Ben Beecher) says: >> ... >>What's going on here? If I had to guess I would say that IF-THEN-ELSE >>is not supported under Netware 2.15 and when the workstation has to >>reattach from the 2.15 server to the 3.11 server it doesn't know ELSE >>is supported. I know it's a lousy explanation. Can someone give us One thing I have noticed here at the University is that when a workstation powers up and NETx runs without the PS option (or if the preferred server is down) the machine will most often attach itself to a 386 server. When I want to login to a 2.15 server, I have to either attach before logging in or login twice. Otherwise wierd things happen such as f:\LOGIN being mapped as the F:\ root directory. Also, login.sys will not run correctly. Try attaching first and then see what happens. Brady... ORAND@kuhub.cc.ukans.edu