home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 14 Text
/
14-Text.zip
/
PSERRO.ZIP
/
PSERRO.DOC
Wrap
Text File
|
1993-02-21
|
7KB
|
216 lines
Peer Server error messages you might see.
And how to share stuff on a Peer Server.
At the Peer Server:
Trying to share resources on the Peer Server:
Doing it wrong:
Before I logged on locally to the Peer server with a valid Admin ID:
[D:\]net share ibm4019l /print
NET2761: This command requires that you have administrator privilege or
that you are a user who has been granted one of the following operator
rights: PRINT,SERVER.
To logon locally to the peer server:
Go to that peer server sit down, put your soda
aside and issue this command:
[D:\]logon userid /p:password /v=local
The user ID was not added as a message name. **
The command completed successfully.
**( The user ID was not added as a messenger name
because someone else is also logged on the LAN
with this ID USERID )
If this is the first time you have logged on locally
then the userid and password will be at default, which is
USERID PASSWORD. Remember the Net.acc file on the peer server
knows nothing about the Net.acc on your Domain Controller.
After Logging on locally with a valid Admin ID:
[D:\]net share ibm4019L /print
ibm4019L was shared successfully.
The IBM4019L was taken from the View page of the Settings
folder for the printer I want to share. On the View page look
at the Physical Name. That's what you include in the share
command.
Doing a Net share commmand for a file alias wrong:
[D:\]net share util = d:\util
The syntax of this command is:
NET SHARE [netname]
netname=device [password]
[/COMM]
[/USERS:number | /UNLIMITED]
[/REMARK:text]
[/PERMISSIONS:XRWCDA]
netname [password]
[/PRINT]
....................( bunch of more stuff )
After taking out the spaces around the equal ( = ) sign :
[D:\]net share util=d:\util
util was shared successfully.
Adding access control to your Peer resources:
( this only needs to be done if you are using User level
Security on your Peer Server )
Doing it wrong:
[D:\]net access D:\UTIL /grant users:r
NET2222: The resource name cannot be found.
Doing it right:
(1) First add the alias name:
[D:\]net access D:\UTIL /ADD
The command completed successfully.
(1) Next grant the access control desired:
[D:\]net access D:\UTIL /GRANT
users:r The command completed successfully.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
From another Requester trying to use the resources shared on the Peer
Server:
Before adding the other user's ID (Joe Bob is wanting to do a
Net Use )to the Peer Server's copy of the Net.acc file:
[C:\]net use lpt8 \\rjameson\ibm4019l
NET3502: OS/2 error 5 has occurred.
SYS0005: Access is denied.
After adding the user's ID to the Peer Server with the following
command:
[D:\]net user joebob joebob /add **
The command completed successfully.
** ( Joe Bob has a hard time with passwords )
Now Joe Bob does the Net Use over again:
[C:\]net use lpt8 \\rjameson\ibm4019L
The command completed successfully.
Doing a Net Use for a file alias from another requester
before adding the access control needed to the
alias on the Peer Server:
[C:\]net use f: \\rjameson\util
The command completed successfully.
[C:\]dir f:
The volume label in drive F is D DRIVE.
The Volume Serial Number is A4A6:0814
Directory of F:\
SYS0065: Network access is denied.
(See "Adding access control to your Peer resources" above for
instructions on how to add access control to an alias)
Doing a Net Use with wrong alias name:
[C:\]net use lpt7 \\rjameson\ibm4020
NET3502: OS/2 error 67 has occurred.
SYS0067: The network name cannot be found.
Doing a Net Use from a second requester after first
requester has done a Net Use to the Peer Server:
(the first requester has the 1 session tied up with the
Peer Server)
[C:\]NET USE LPT1 \\RJAMESON\IBM4019L
NET3502: OS/2 error 71 has occurred.
SYS0071: The network request was not accepted.
Doing a Net Use to a Share on a Peer Server using Share level Security:
Using the incorrect alias password:
[C:\]Net Use w: \\RJAMESON\UTIL junk
NET3502: OS/2 error 86 has occured
SYS0086: The specified network password is not correct.
The password of junk was incorrect, after doing it with the
correct password it worked okay.
Notes:
A Peer Server sharing a printer resource or file resource can only be
used by one person and the owner** of that Peer Server ( as stated in the
IBMLAN.INI file). So if it shares a printer and one (1) user on another
requester does a Net Use to it then it is tied up. There are two (2) work
arounds to this:
(1) Instead of doing a Net Use to the alias just do a copy to the
netname. For instance say I share my printer on my Peer Server with
the following command:
net share ibm4019l /print
Then a user on another machine could do the following:
Copy config.sys \\rjameson\ibm4020
The session would be established, the job printed and then the
session disconnected, ready for the next user.
(2) On the Domain Controller (DC) or on one of the Additional Servers
(AS) do a Net Use to that printer alias. Then turn around and share
it. Note: This trick only works on a printer share.
Remember the Peer Server does not have anything to do with the Domain.
In other words a Peer Server does not have a Domain. PCLP ( DOS LAN
Product available from IBM ) uses a concept similar to Peer Server. The
Net.acc (The User database ) on the Peer server does not have access tothe
user IDs and Passwords that are on the Domain Controller***. With the
Share level of security one dooesn't need to worry about the user IDs,
only the password for the item shared. So one can select how you setup
the Peer Server. In the IBMLAN.INI file there is a section called : [peer]
You can change the security from User to Share or visa versa. See below:
[peer]
; I commented out the next line.
; security = User
; Then added the next line
; and stopped and restarted the requester.
security = Share
username = RJAMESON
**The owner is the name listed as username, if you as an Admin are doing
backups of the Peer Server from a Server you might have this as your
Admin userid.
*** Domain Controller is a machine with LAN Server 1.3/2.0/3.0 installed
and setup thru Advanced Installation as the Domain Controller.
There is a section in the new Redbook coming out about the Peer server.
It's quite good.
Hope this helps with any of your Peer questions.