 |
» |
|
|
|
DIGITAL SNA access server migration guide |
[Top] [Prev] [Next] [Index] [Contents] DIGITAL SNA Access Server Migration Guide
Suggestions To Help You Troubleshoot
If you have installed and configured Access Server and are having problems, or if the tests reveal problems, here's a brief list of troubleshooting points to check:
- Are Access Server, SNA Server, and Windows NT Server all installed on the same Windows NT node?
- Did you install the appropriate Service Pack(s) for SNA Server?
- Have you verified that all networks are configured and working properly?
- Have you verified that all communication links are configured and working properly?
- Are connection parameters (including Node IDs) and access names that are associated with existing access routines configured properly on the OpenVMS system and on the IBM host?
- Are DECnet and TCP/IP protocols, if used, installed and properly configured?
- If you're running both an existing DECnet SNA Gateway and the new Access Server Gateway together, are there overlaps or conflicts between existing Access Names?
- Are appropriately named LUs, LU pools, local and remote LUs, and logon modes established properly in SNA Server?
- Are LUs all defined as LUAs (application LUs)?
[Top] [Prev] [Next] [Index] [Contents] DIGITAL SNA Access Server Migration Guide
|
