Technical Document # - 8135045
____________________________________________________________
Family: LAN
Product: LAN Requester (OS/2)
Release: 4.0
Syslevel:
Last Updated: 12/17/1997
____________________________________________________________
TITLE
NT Server Connectivity from OS/2 LAN Requesters and OS/2 Peer
DESCRIPTION
When you attempt to connect to a server from an OS/2 Peer or OS/2 LAN Requester client, the following error messages appear:
NET3502: OS/2 error 53 has occurred.
Cause: The specified OS/2 error occurred.
Action: Correct the problem and type the command again.
For details on the original error, type HELP SYS####
where #### is the error number from the original message.
SYS0053: The network path was not found.
EXPLANATION: The server that you specified does not exist or has not
been started.
ACTION: Do one of the following and retry the command:
Verify that you specified the path name correctly.
Verify that the server specified is started.
Contact your network administrator if you continue to have problems.
This problem is a basic connectivity error. It occurs whenever the requester is unable to find a computer name, or server, on the network. The server could be a Microsoft NT server, or an OS/2 LAN Server.
RESOLUTION
Use the following steps to correct SYS0053 errors when using any OS/2 IBM Requester to
connect to any Peer or Server.
General Causes
1. Bad cable(s)
2. Bad or unsupported network interface cards (NICs)
3. Incorrect Computer Name
4. Network protocols incorrectly selected, configured, or matched
5. Routers bad or incorrectly configured (if present)
6. Server or Peer not running
7. Timing
8. Transport errors
Solutions
1. Replace cable(s)
2. Replace or obtain supported NIC(s)
3. Verify Computer Name (see IBM Details and NT Details, below)
4. Make sure Requester and Server or Peer are using NetBIOS protocol or
NetBIOS over TCP/IP (see IBM Details and NT Details, below).
Make sure NetBIOS over TCP/IP (if applicable) is configured properly
for WAN (Wide Area Network). (See Network Administrator Reference 1:
Planning, Installation, and Configuration, Appendix K.)
Make sure the protocols between the computers are properly matched:
If requester has NetBIOS then server must have NetBIOS.
If OS/2 requester has NetBIOS over TCP/IP then NT server must have
MS TCP/IP (which is, in effect MS version of NetBIOS over TCP/IP).
5. Check Router; make sure router can pass TCP/IP (PINGing is not a
complete verification of TCP/IP or that the router is configured properly).
6. Verify that Server or Peer services are started and operational (see IBM Details).
7. Increase timers TI, T1, and T2 in \IBMCOM\PROTOCOL.INI to 60000, 10000, and 2000,
respectively.
8. Check \IBMCOM\LANTRAN.LOG for errors; correct any errors.
IBM Specific Basics
1. IBM OS/2 LAN Server, Requester, or Peer must be configured with NetBIOS
or NetBIOS over TCP/IP (requires NetBIOS and TCP/IP to be installed and
configured (see IBM Details).
2. Userids and passwords must be defined exactly the same as on the NT Server and
any additional NT server.
3. Check Userid, Permissions, and Groups for proper authority.
4. Make sure IBM computer name is different from NT computer name (see IBM Details
and NT Details, below).
5. Make sure a resource is shared:
a. Check for a shared resource by typing NET SHARE at an OS/2 command prompt;
look for a shared resource under Netname.
b. To create a new share, type NET SHARE TESTIBM=C:\ at an OS/2 command prompt.
6. To access a shared resource:
At an NT command line, type
NET USE <unused virtual drive>: \\<IBM computer name>\<shared resource alias>
7. When using the OS/2 Peer Sharing and Connecting GUI (Graphical User Interface),
you must type in the NT computer name when trying to connect to resources.
NT servers will not show up in the drop down list.
8. Add NT domain to othdomains= in \IBMLAN\IBMLAN.INI file to see NT resources in the
Resource Browser.
9. NT domains cannot be remotely administered via GUI.
NT Specific Basics
1. The protocol must be configured as MS NetBEUI or MS TCPIP (see NT Details).
2. Userids and passwords must be defined exactly the same as on
IBM OS/2 LAN Server or OS/2 Peer.
3. Check Userid, Permissions, and Groups for proper authority.
4. Make sure NT computer name is different from IBM computer name
(see IBM Details and NT Details, below).
5. Make sure a resource is shared:
* To check shared resources, type NET SHARE at a DOS or NT command line;
look for a shared resource under Share name.
* To create a new shared resource, type NET SHARE TESTNT=C:\ at a DOS or NT command line.
6. To access a shared resource:
From an OS/2 command prompt, type
NET USE <unused virtual drive>: \\<NT computer name>\<shared resource alias>
7. NT 4.0 will not interoperate with HPFS (High Performance Filing System).
8. Manually add <IBM computer name> to Add to domain... in Server Manager to see
IBM Shared resources (NT 4.0).
IBM Details
To configure OS/2 LAN Server or Peer for NetBIOS:
Note: This is only a rough guide and assumes MPTS has been
installed and configured previously.
1. Select MPTS from the desktop.
2. Select Configure in the Multi-Protocol Transport Services window.
3. Select LAN Adapters and Protocols.
4. Select Configure.
5. Select IBM OS/2 NetBIOS in the Protocols section of the LAPS Configuration screen.
6. Select Add...
7. Select OK.
8. For complete details, refer to Multi-Protocol Transport Services - AnyNet for
OS/2: Configuration Guide (Publication Number 10H9693).
To determine OS/2 LAN Server or OS/2 Peer computer name:
1. Open an OS/2 command prompt.
2. Type EPM X:\IBMLAN\IBMLAN.INI, then press Enter.
(Where X: is the drive OS/2 LAN Server or Peer is installed)
3. Look for COMPUTERNAME= (The name here is analogous to NT Computer name.)
4. Look for DOMAIN= (The name here is analogous to NT Domain name.)
5. Close EPM editor.
To start IBM OS/2 LAN Server:
At an OS/2 command line, type NET START SRV, then press Enter.
To start IBM LAN OS/2 Peer:
At an OS/2 command prompt, type NET START REQ, then press Enter.
To start IBM LAN Requester 4.0 Peer Services:
At an OS/2 command prompt, type NET START PEER, then press Enter.
NT Details
To configure an NT Server 4.0 to use MS NETBEUI or MS TCP/IP protocol:
Note: This is only a rough guide and assumes NIC has been
installed and configured. Contact Microsoft for detailed assistance.
1. Select Start on Taskbar.
2. Select Settings.
3. Select Control Panel.
4. Select Network.
5. Select Protocol tab.
6. Select NETBEUI (or TCPIP) from the list.
7. Select OK.
To determine NT Server 4.0 computer name:
1. Select Start on Taskbar.
2. Select Settings.
3. Select Control Panel.
4. Select Network.
5. Select Identification tab.
6. View Computer name: This is analogous to COMPUTERNAME= in \IBMLAN\IBMLAN.INI.
7. View Domain: This is analogous to DOMAIN= in \IBMLAN\IBMLAN.INI.
8. Select OK.
To configure NT Server 3.51 for MS NETBEUI
Note: This is only a rough guide and assumes NIC has been
installed and configured. Contact Microsoft for detailed assistance.
1. Select Control Panel.
2. Select Network.
3. Select NetBEUI Protocol.
4. Select OK.
To determine NT Server 3.51 computer name:
1. Select Control Panel.
2. Select Network.
3. View Computer Name: This is analogous to COMPUTERNAME= in \IBMLAN\IBMLAN.INI.
4. View Domain: This is analogous to DOMAIN= in \IBMLAN\IBMLAN.INI.
5. Select CLOSE.
References
For more information, refer to the following online books:
Up and Running!, OS/2 Warp Server, Appendix C
Up and Running!, OS/2 Warp Connect, Appendix B
In addition, consult the Microsoft Windows NT Server documentation.
Document Info
Related Docs:
__________________________________________________________________________________________________________________________________
IBM disclaims all warranties, whether express or implied, including without limitation, warranties of fitness and merchantability with respect to the information in this document. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright (c) 1994, 1996 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
__________________________________________________________________________________________________________________________________