Common SAPGUI Problems and

Solutions for Level Two Support

TABLE OF CONTENTS

1.0 OBJECTIVE
1.1 PURPOSE
1.2 AUDIENCE
2.0 INTRODUCTION
2.1 DESKTOP SERVICES FILE CHANGED OR DAMAGED
2.1.1 Symptoms
2.1.2 Solution
2.1.3 Explanation
2.2 INCORRECT SAP R/3 HOST NAME OR ADDRESS
2.2.1 Symptoms
2.2.2 Solution
2.3 LOGON GROUP CONFIGURATION PROBLEM
2.3.1 Symptoms
2.3.2 Solution
2.4 INCORRECT R/3 SYSTEM NUMBER
2.4.1 Symptoms
2.4.2 Solution
2.4.3 Explanation
2.5 SLOW SAPGUI PERFORMANCE ON WIDE AREA NETWORKS
2.5.1 Symptoms
2.5.2 Solution
2.5.3 Explanation
2.5.4 Installation Setup
2.6 DESKTOP RESOURCES AND SAPGUI
2.6.1 Symptoms
2.6.2 Solution
2.7 PASSWORD IS IN THE “EXCEPTION TABLE”
2.7.1 Symptom
2.7.2 Solution
2.7.3 Explanation
2.8 DETERMINING THE VERSION OF SAPGUI YOU ARE USING
2.9 USING SAPSWEEP TO UNINSTALL OLD VERSIONS OF SAPGUI
2.10 NETWORK CONNECTION PROBLEMS
2.10.1 Verifying Basic TCP/IP Network Connectivity
2.10.2 SAP Network Interface Layer
2.11 EXAMPLES OF NETWORK PROBLEMS
2.11.1 Symptoms
2.11.2 Solution
3.0 APPENDIX
3.1.1 Sample Desktop Services File (C:\Windows\services)
3.1.2 Example of a Successful “niping –t” Test
3.1.3 Services File Repair Script “sap_services.bat”
3.1.4 Services File Repair File “sap_dp_gw_.add”
3.1.5 Services File Repair File “sap_ms.add”

Objective
The objective of this document is to describe commonly encountered problems with the network and SAPGUI,
and suggest solutions.
1.1 Purpose
The purpose of this document is to describe common network problems and SAPGUI problems in sufficient
detail to allow the Basis analyst or support technician to quickly find solutions and get the user back on line.

1.2 Audience
This document is intended for experienced Basis administrators and support technicians who are familiar with
TCP/IP networking, SAPGUI, and network tools like “niping”. It is also useful to second and third level support
in handling the most common problems.
2.0 Introduction
This document describes most common problems that may be encountered when attempting to connect to an
SAP R/3 server and log on as an SAP user. Fixes, work-arounds, and referrals are provided to help you
overcome these common problems:
 Desktop services file changed or damaged
 Incorrect SAP server host name or IP address
 Incorrect SAP System Number
 Slow SAPGUI Performance
 Desktop Resources and SAPGUI
 Password is in the “Exception Table”, too easy to guess, not secure
 Determining Which Version of the SAPGUI You Are Using
 Network connection problems
2.1 Desktop Services File Changed or Damaged
2.1.1 Symptoms
There are two possible error messages for this problem. If you are logging in using a “Logon Group” like “Atlas”,
“FDC Operations”, or “GOH-Workgroup2”, you will receive this “load balancing error 88” message:

If you are logging directly into a particular SAP server, you will see this “service unknown” error:

The error window usually appears very quickly when you attempt to log into an R/3 system:

This means that SAPGUI cannot find an entry in your desktop services file. (This message is also a symptom of
not reaching the R/3 server, but that message has a slower response time.)

2.1.2 Solution
Locate the user’s desktop services file:
 For Windows 95 and Windows 98 systems, the file path is “C:\Windows\services”
 For Windows NT and Windows 2000, the file path is “C:\Windows\System32\Drivers\Etc\services”
Examine the services file, looking for the SAP port definitions. There should be entries for ports “sapdp00”
through “sapdp99”, “sapgw00” through “sapgw99”, and messge server entries like “sapmsHP1”, “sapmsPRD”,
“sapmsPE1”, etc. Compare the contents of the services file to the sample file in the Appendix below. You will
probably find that the SAP service entries beginning with “sapdp00” are missing.
Missing SAP port definitions can be reapplied to the services file using the repair script “sap_services.bat”,
available on the following servers. Click on an entry to execute the script.

System Region Command Link

FDC, Bellerica \\bl_corp1\corp_sw\pc\sap_gui\SAP_GUI_46D\sap_services.bat
HPOCS, MASS USA
Goh-Fast
FDC, North Ryde \\Znryp001\share\sap_gui_46d\sap_services.bat
HPOCS, Australia
Goh-Fast
FDC, Val Bonne \\Valbonne1\Software\SAP-Install\SAP_GUI_46D\sap_services.bat
HPOCS, France
Goh-Fast
FDC, Santa Clara \\sc_corp1\corp_sw\pc\sap_gui\SAP_GUI_46D\sap_services.bat
HPOCS, CA USA
Goh-Fast
Atlas Europe \\Znsgd034\atlasemea\sap_services.bat

Atlas North America \\ZCARC003\GROUPS\AtlasGlobalHR\GlobalHRSupport\sap_services.bat

Atlas Brazil \\Zbrgc5\atlasbrs\sap_services.bat

Atlas Mexico \\Zgard1\atlasmex\sap_services.bat

Missing SAP port definitions can also be restored manually, by copying the entries from another system, or
entering them into the services file using an editor, e.g. Notepad.
 Note: For Windows NT and Windows 2000 desktops, the services file is under the control of the
Administrative User. You will need administrator privileges to make changes to the file. Use the “Install
Privilege Tool” to grant administrative privileges.

2.1.3 Explanation
If you are installing or configuring new network devices, like PCMCIA network adapter cards or modem cards,
the installation or upgrade program may replace the IP services file. This often happens to people who use a
docking station with a network card when in their local office, but switch to a PCMCIA network card when they
are working at other Nortel Networks sites. Unfortunately, switching from one network interface to the other
runs a network configuration program that replaces the user’s services file with its own version. Any special port
definitions that were added to the default file are lost.

The repair script “sap_services.bat” appends the SAP port definitions to the services file. The list of ports
includes message server entries for all known SAP systems. Existing services file entries belonging to other
applications are not lost.
2.2 Incorrect SAP R/3 Host Name or Address
2.2.1 Symptoms

You receive this error message when attempting to log into SAP
R/3:

This means that the Domain Name Server cannot find the host server you are asking for. A similar message
results if you ask for an IP address that is not available.

2.2.2 Solution
First, make sure you have spelled the host server name correctly, or entered the IP address correctly. If the
host name or IP address is being issued from a logon icon that you have used before, then it is probably correct,
and the host itself is unreachable.

You can test whether the host is reachable using the ICMP Echo command, usually called “ping”. Open a DOS
window and enter “ping” followed by the host name or IP address. If you do no receive an echo reply from the
host, the disconnect may be caused at any point on the network between the desktop and the server. Start by
pinging other hosts you know about to see if they reply. If they do not reply to their host name, try using their IP
address, if you know it. If none reply, try pinging your own desktop’s IP address. If that fails, there is a network
stack problem, and you need to call NT4HELP to get the network software reinstalled and/or reconfigured.

If you find that host servers reply to their IP address, but not to their host names, then you have a Domain Name
Server (DNS) problem, which may be due to a configuration error on your desktop, or that the DNS server is
unreachable. In either case, you probably need to call NT4HELP to get the problem fixed. Similarly, if you
request an R/3 server by host name and you get a very slow initial response, this may be due to the DNS server
having to look up the host’s IP address. The DNS server may be very busy, or it may have to refer the question
to a lot of its fellow DNS servers before it finds one that knows the answer. If this is a chronic problem, try using
the IP address instead, so the DNS does not have to look it up. The only disadvantage of using the IP address
directly is that sometimes IP addresses are changed by the network administrators, whereas host names
usually remain the same for the working life of the server. However, IP addresses for the SAP servers are not
changed very often, and the quicker response for each login you do is definitely worth the trouble of having to
change the IP address once or twice.

System Hostname
Atlas Development maple.us.nortel.com
Atlas Training cypress.us.nortel.com
Atlas Fix mulberry.us.nortel.com
Atlas Testing aspen.us.nortel.com
Atlas Production sequoia.us.nortel.com
FDC Development sapdv3.corpwest.baynetworks.com
 System Hostname
FDC Unit Test saput3.corpwest.baynetworks.com
FDC System Test jumanji.corpwest.baynetworks.com
FDC Production sapprd.corpwest.baynetworks.com
Goh-Fast Development sapde1.corpwest.baynetworks.com
Goh-Fast Testing sapqe1.corpwest.baynetworks.com
Goh-Fast Testing 2 sapqe2.us.nortel.com
Goh-Fast Conversion sapce1.corpwest.baynetworks.com
Goh-Fast Production sappe1.corpwest.baynetworks.com
HPOCS Development sapmd1.us.nortel.com
HPOCS Training sapmd1.us.nortel.com
HPOCS Fix samf1.us.nortel.com
HPOCS Production sapmp1.us.nortel.com
2.3 Logon Group Configuration Problem
2.3.1 Symptoms
The user attempts to access any SAP System via the logon group “Atlas”, “GOH-WorkGroup1”,
”GOH-WorkGroup2”, “Customer Admin”, “EMEA”, “Financial Admin”, “Human Resources”, “Ireland”,
“Operations”, “Public” or and receives a network timeout error. There might be a problem with the configuration
with the logon groups.

To see if users are using Logon Groups: Go to Saplogon – select one of the SAP systems and click on
“Properties”. The “Application Server” field is the Logon Group name and should be greyed out. The Note:
Saplogon-pad will not have the ‘Properties’ option.

2.3.2 Solution
This may be because the IP address setting in the server “Attributes” tab in SMLG is incorrect, or more likely,
the IP address setting is missing. If there is no IP address attribute, the message server will assigning its
default address for the application server. Unfortunately, the default subnet could be private, so the user cannot
access the server by that route. Please route case to Basis Team to re-configure the Logon Groups.

Note: This problem can appear to be intermittent if only one server is misconfigured and the rest are correct.

.
2.4 Incorrect R/3 System Number
2.4.1 Symptoms

You are attempting to log into an SAP R/3 system that you
have not used before. You set up an entry in SAPlogon, specifying the host name or IP address, and an R/3
system number of 01. You then attempt to log on using the new entry. After a delay, you receive the following
error message:

2.4.2 Solution
Check your configuration information for the R/3 system. You will probably find that the system number is not
01, but 49, or some other number. Also, you must specify a two-digit system number, complete with leading
zero, for numbers under 10.

The repair file “sap_ms.add” in the Appendix lists the message server entries for all currently active SAP
systems. You can derive the system number from the entry by taking the last two digits from the port number.
For example, the message server port entry for HP1 is:

sapmsHP1 3642/tcp

That means that the system number for HP1 is 42. Similarly, the system number for PE1 is 28, MD1 is 87, etc.

2.4.3 Explanation
This error message usually means that you have reached a UNIX host, but the SAP R/3 dispatcher has not
picked up your connection. This may be because the dispatcher is only accepting calls for a different system
number, e.g. 49, or that SAP R/3 is not running on this system (it is down, or not installed).

Missing SAP system number definitions can be reapplied to the services file using the repair script
“sap_ms.add”, available on the following servers. Click on an entry to execute the script.

System Region Command Link

FDC, Bellerica \\bl_corp1\corp_sw\pc\sap_gui\SAP_GUI_46D\sap_ms.add
HPOCS, MASS USA
Goh-Fast
FDC, North Ryde \\Znryp001\share\sap_gui_46d\sap_ms.add
HPOCS, Australia
Goh-Fast
FDC, Val Bonne \\Valbonne1\Software\SAP-Install\SAP_GUI_46D\sap_ms.add
HPOCS, France
Goh-Fast
FDC, Santa Clara \\sc_corp1\corp_sw\pc\sap_gui\SAP_GUI_46D\sap_ms.add
HPOCS, CA USA
Goh-Fast
Atlas Europe \\Znsgd034\atlasemea\sap_ms.add

Atlas North America \\ZCARC003\GROUPS\AtlasGlobalHR\GlobalHRSupport\sap_ms.add

 System Region Command Link
Atlas Brazil \\Zbrgc5\atlasbrs\sap_ms.add

Atlas Mexico \\Zgard1\atlasmex\sap_ms.add

Note that if you receive this error immediately after trying to connect, it is more likely to be a problem with the
“services” file on your desktop. See the section “Desktop Services File Changed or Damaged” above.
2.5 Slow SAPGUI Performance on Wide Area Networks
2.5.1 Symptoms
It takes more than a minute for SAPGUI to start up and connect to the server. This is most likely to happen in
remote locations where network access is slow.

2.5.2 Solution
Since the network is slow, reconfigure SAPGUI to send and receive less data. There are two procedures to
follow:
1) Select the old style SAPGUI screen using the SAP Configuration tool. There should be an icon on your
desktop called “SAP Configuration” that looks like this:

• Double-click to open it. You will see a small replica of the SAPGUI screen. There is a check box to
“Use New Visual Design”. If the box is checked, click on it to remove the check. Click the “Apply”
button, and close the window. The next time you run SAPGUI, you will see a simplified screen with
less animation, which makes less demand on network resources.
2) Select the “low speed connection” setting in the SAPlogon screen. Open SAPlogon, select logon entry for
the system in question, and click on “Properties”. Click on the “Advanced” button to bring up the
“Advanced Options” window shown below. Select the “Low Speed Connection” check box, and select the
“OK” button to complete the task.

2.5.3 Explanation
Running the “old style” SAPGUI screen reduces demand on the desktop by using fewer colours and turning off
animation effects. Initial startup runs faster.

The “Low Speed Connection” option reduces demand on network resources by transferring the minimum data
required to perform a task. For example, when displaying a large quantity of data, the server sends the data
page by page when the user asks for it; it does not “read ahead” and transfer data in advance. This means that
there will be less delay in presenting the first screen of data for a transaction.

2.5.4 Installation Setup

If you are issuing a preconfigured “SAPlogon.ini” configuration file to your users, you can set the “Low Speed
Connection” option as default. Edit the file, setting the entries as follows:

[LowSpeedConnection]
Item1=1
Item2=1
2.6 Desktop Resources and SAPGUI
SAPGUI makes significant demands on desktop resources, especially RAM, virtual memory, and graphics
memory. When these resources run short, a number of symptoms will appear.

2.6.1 Symptoms
The following window pops up when you starting a new SAPGUI session, or performing a task that requires
SAPGUI to open a new window:

After a minute, this message is usually followed by:

After SAPGUI startup, resources may be taken up by other applications, and you will receive this warning:

2.6.2 Solution
You may be able to start SAPGUI successfully after you free up some desktop resources by closing other
applications. If that does not help, check that you have enough RAM to run SAPGUI. SAP recommends a
minimum of 128MB of RAM if you want to run SAPGUI along with other applications. You should also have
plenty of spare space on the C:\ drive to accommodate the Windows virtual memory page file (200MB or more
free).
Another suggestion: If the Microsoft Office Shortcut toolbar is active on your desktop, but you do not use it
much, you can turn it off to free up memory. The shortcut bar may be located at the left or right of the screen.
You can remove it by clicking on the box at the top left, and selecting the “Exit” option.

A second window will appear to ask whether you want the shortcut bar to be activated each time you restart the
system. Select the “No” button to ensure it is not restarted automatically.
2.7 Password is in the “Exception Table”
2.7.1 Symptom
The user is choosing a new password. The system responds with this rather cryptic error message:

2.7.2 Solution
The password chosen is too easy to guess. Select the check mark to accept the message. Make up a more
secure password, and try again.

2.7.3 Explanation
The system has a table of passwords that are considered too easy to guess. If a user chooses one of the
passwords in the table, the message above is issued. Passwords to avoid are any with “NORTEL” in them, or
people’s first names, or sequences like “12345678” and “QWERTY”, etc.
2.8 Determining the Version of SAPGUI You Are Using
Some SAPGUI (and even SAP short dump) problems can be traced back to an out-of-date version of the
SAPGUI on the user’s desktop. Here is how to determine the version of SAPGUI the user has on the desktop:

1) Double click on the SAPlogon icon on your desktop. Left click at the top left hand corner of the
SAPLOGON screen and you will be able to see the window menu as shown below.
2) Click on the ‘About Sapgui’ entry in the window menu. You will see a screen as shown below displaying
information about the SAPGUI version you are using. Compare the information displayed on your desktop
to that shown here. The current version is SAPGUI 4.6D Final Release, also called “Compilation 4”.

3) Click OK to close the SAPlogon screen.

 2.9 Using SAPsweep to Uninstall Old Versions of SAPGUI
You must always uninstall old versions of SAPGUI before attempting to install a new version. Normally, the
uninstall option in the Program menu will effectively remove the old version. The path is:

Start → Programs → SAP Frontend → Remove SAP Frontend

If the uninstall fails, or you have an older version of SAPGUI that has no uninstall option, the SAPsweep utility
can be used to clean up the system before installing the new version. SAPsweep can also be used when an
installation fails, leaving an incomplete installation behind. The SAPsweep program can be executed from the
following file server location:

\\zcarc003\groups\AtlasGlobalHR\GlobalHRSupport\sapsweep.exe

Note: SAPsweep consists of two executable files:

• sapsweep.exe called by the user
• sapregsv.exe called by sapsweep.exe to make a backup copy of the registry

If you wish to provide SAPsweep support on an additional file server, both binaries must be copied to the new
location.
2.10 Network Connection Problems
This section describes how SAPGUI uses the network to connect to the server, and the network services that
must be in place before the connection can be made. It is assumed that all users have basic TCP/IP networking
software installed on their systems.

2.10.1 Verifying Basic TCP/IP Network Connectivity

The user’s local desktop support team is responsible for setting up basic network services so the users can
connect to email and other applications. The Basis team is responsible for ensuring that the SAP Network
Interface (NI) layer runs on top of TCP/IP network, and that the user’s SAPGUI client can connect via NI to the
SAP servers.

The general approach in troubleshooting network problems is to start with basic TCP/IP service, and test each
additional network layer until the SAPGUI can be connected to the server. The steps are:

 check whether other network based applications are running successfully, e.g. email.
 Check the desktop TCP/IP address allocation using the “winipcfg” utility. This ensures that the user has
received an IP address from the local DHCP server. Go to the Start → Run menu, enter “winipcfg”, and
execute it. The following window will be displayed. Select the network adapter that the user is currently
using (PPP is for dial up connections). The IP Address field must contain a valid IP address for the
network the user resides on. For internal Nortel networks, the address will start with 47.

 If the user travels to another Nortel site, the laptop system may retain an address from the “home” office
location that will not work on this site. Use the “Release” and “Renew” buttons to get a new address from
the local DHCP server.
 Use the TCP/IP “ping” command to see if the user’s system can be reached using the IP address reported
by “winipcfg”. For example, log into sequoia and run “/usr/sbin/ping –s 47.130.114.179” to check out the
path from HP1 to the user’s desktop.
 Similarly, you can run the “ping” command on the user’s desktop to see if sequoia is reachable from
there. Open a DOS window, and run “ping 47.81.128.132”.
 Test TCP/IP with other applications, e.g. email.
 Once TCP/IP is working, you can concentrate on the SAP Network Interface layer.

2.10.2 SAP Network Interface Layer

 If the user is receiving errors related to “Protocol Family”, but basic TCP/IP seems to be working, examine
the NI layer for problems. The utility “niping” is used to test the NI layer.
 Test whether the desktop is properly configured to support the NI layer. Open a DOS window, change to
the directory C:\Program files\sappc\sapgui, and run the command “niping –t”. This should produce a list
of NI functional tests, ending with the message “*** SELFTEST O.K. ***”. There is an example of this test output
in the Appendix below.

 The next step is to test NI communications end-to-end. Log into sequoia and enter the command “niping –s” to start
up the niping test server. Leave it running while you start up the niping client on the user’s desktop. Enter the
 command “niping –c –H 47.81.128.132. The niping client and server programs should then be able to talk to each
other over the network. Note any error messages issued, and the response time. The user’s end of this dialog should
look like this:

Thu May 31 15:17:29 2001

connect to server o.k.

Thu May 31 15:17:30 2001

send and receive 10 messages (len 1000)

------- times -----

avg 93000 usecs
max 110000 usecs
min 50000 usecs
bw 21.00 kb/sec
excluding max and min:
av2 96250 usecs
bw2 20.29 kb/sec

 The server end of the niping test dialog looks like this:

Thu May 31 19:14:25 2001

ready for connect from client ...

Thu May 31 19:15:14 2001

connect from host dmclaren-1.ca.nortel.com, client 2 o.k.

 Capture any errors you receive to a file for reporting to SAP.

2.11 Examples of Network Problems
2.11.1 Symptoms
The user is unable to connect to the SAP servers. TCP/IP is working correctly, e.g. email access is working
correctly. The following error message is displayed when the user attempts to reach SAP:

Testing with “niping –t” produces the error messages:

Wed May 30 14:47:27 2001

function name parameters return code
---------------------------------------------------------------------
NiMyHostName (..) rc = 0
***LOG Q0I=> NiPSocket: WSASocket (10047: WSAEAFNOSUPPORT: Address family not
supported by protocol family) [ninti.c 1105]
*** ERROR => NiILocalCheck: NiPSocket (rc=-1) [nixxi.c 1758]
NiMyAddrVerify (Mauricio_Ortiz, NULL) rc = -16
*** ERROR => NiTSelfTest: NiMyAddrVerify (rc=-16) [nixxtst. 1640]

This suggests that the NI software cannot reach the local (user’s desktop) host called “Mauricio_Ortiz”. Note
that this host name is 14 characters long. Compare these messages to the successful test in the Appendix
below, where the “NiMyAddrVerify” test worked correctly.

2.11.2 Solution
The user’s desktop is identified by a host name that is too long. The maximum host name that the SAP network
will recognize is 10 characters, e.g. dmclaren_1. The solution is to ask the desktop support team to change the
host name to a shorter name, then reinstall SAPGUI.
3.0 Appendix
3.1.1 Sample Desktop Services File (C:\Windows\services)
# Copyright (c) 1993-1995 Microsoft Corp.
#
# This file contains port numbers for well-known services as defined by
# RFC 1060 (Assigned Numbers).
#
# Format:
#
# <service name> <port number>/<protocol> [aliases...] [#<comment>]
#

echo 7/tcp
echo 7/udp
discard 9/tcp sink null
discard 9/udp sink null
systat 11/tcp
systat 11/tcp users
daytime 13/tcp
daytime 13/udp
netstat 15/tcp
qotd 17/tcp quote
qotd 17/udp quote
chargen 19/tcp ttytst source
chargen 19/udp ttytst source
ftp-data 20/tcp
ftp 21/tcp
telnet 23/tcp
smtp 25/tcp mail
time 37/tcp timserver
time 37/udp timserver
rlp 39/udp resource # resource location
name 42/tcp nameserver
name 42/udp nameserver
whois 43/tcp nicname # usually to sri-nic
domain 53/tcp nameserver # name-domain server
domain 53/udp nameserver
nameserver 53/tcp domain # name-domain server
nameserver 53/udp domain
mtp 57/tcp # deprecated
bootp 67/udp # boot program server
tftp 69/udp
rje 77/tcp netrjs
finger 79/tcp
link 87/tcp ttylink
supdup 95/tcp
hostnames 101/tcp hostname # usually from sri-nic
iso-tsap 102/tcp
dictionary 103/tcp webster
x400 103/tcp # ISO Mail
x400-snd 104/tcp
csnet-ns 105/tcp
pop 109/tcp postoffice
pop2 109/tcp # Post Office
pop3 110/tcp postoffice
portmap 111/tcp
portmap 111/udp
sunrpc 111/tcp
sunrpc 111/udp
auth 113/tcp authentication
sftp 115/tcp
path 117/tcp
uucp-path 117/tcp
nntp 119/tcp usenet # Network News Transfer
ntp 123/udp ntpd ntp # network time protocol (exp)
nbname 137/udp
nbdatagram 138/udp
nbsession 139/tcp
NeWS 144/tcp news
sgmp 153/udp sgmp
tcprepo 158/tcp repository # PCMAIL
snmp 161/udp snmp
snmp-trap 162/udp snmp
print-srv 170/tcp # network PostScript
vmnet 175/tcp
load 315/udp
vmnet0 400/tcp
sytek 500/udp
biff 512/udp comsat
exec 512/tcp
login 513/tcp
who 513/udp whod
shell 514/tcp cmd # no passwords used
syslog 514/udp
printer 515/tcp spooler # line printer spooler
talk 517/udp
ntalk 518/udp
efs 520/tcp # for LucasFilm
route 520/udp router routed
timed 525/udp timeserver
tempo 526/tcp newdate
courier 530/tcp rpc
conference 531/tcp chat
rvd-control 531/udp MIT disk
netnews 532/tcp readnews
netwall 533/udp # -for emergency broadcasts
uucp 540/tcp uucpd # uucp daemon
klogin 543/tcp # Kerberos authenticated rlogin
kshell 544/tcp cmd # and remote shell
new-rwho 550/udp new-who # experimental
remotefs 556/tcp rfs_server rfs# Brunhoff remote filesystem
rmonitor 560/udp rmonitord # experimental
monitor 561/udp # experimental
garcon 600/tcp
maitrd 601/tcp
busboy 602/tcp
acctmaster 700/udp
acctslave 701/udp
acct 702/udp
acctlogin 703/udp
acctprinter 704/udp
elcsd 704/udp # errlog
acctinfo 705/udp
acctslave2 706/udp
acctdisk 707/udp
kerberos 750/tcp kdc # Kerberos authentication--tcp
kerberos 750/udp kdc # Kerberos authentication--udp
kerberos_master 751/tcp # Kerberos authentication
kerberos_master 751/udp # Kerberos authentication
passwd_server 752/udp # Kerberos passwd server
userreg_server 753/udp # Kerberos userreg server
krb_prop 754/tcp # Kerberos slave propagation
erlogin 888/tcp # Login and environment passing
kpop 1109/tcp # Pop with Kerberos
phone 1167/udp
ingreslock 1524/tcp
maze 1666/udp
nfs 2049/udp # sun nfs
knetd 2053/tcp # Kerberos de-multiplexor
eklogin 2105/tcp # Kerberos encrypted rlogin
rmt 5555/tcp rmtd
mtb 5556/tcp mtbd # mtb backup
man 9535/tcp # remote man server
w 9536/tcp
mantst 9537/tcp # remote man server, testing
bnews 10000/tcp
rscs0 10000/udp
queue 10001/tcp
rscs1 10001/udp
poker 10002/tcp
rscs2 10002/udp
gateway 10003/tcp
rscs3 10003/udp
remp 10004/tcp
rscs4 10004/udp
rscs5 10005/udp
rscs6 10006/udp
rscs7 10007/udp
rscs8 10008/udp
rscs9 10009/udp
rscsa 10010/udp
rscsb 10011/udp
qmaster 10012/tcp
qmaster 10012/udp
sapdp00 3200/tcp
sapdp01 3201/tcp
sapdp02 3202/tcp
sapdp03 3203/tcp
sapdp04 3204/tcp
sapdp05 3205/tcp
sapdp06 3206/tcp
sapdp07 3207/tcp
sapdp08 3208/tcp
sapdp09 3209/tcp
sapdp10 3210/tcp
sapdp11 3211/tcp
sapdp12 3212/tcp
sapdp13 3213/tcp
sapdp14 3214/tcp
sapdp15 3215/tcp
sapdp16 3216/tcp
sapdp17 3217/tcp
sapdp18 3218/tcp
sapdp19 3219/tcp
sapdp20 3220/tcp
sapdp21 3221/tcp
sapdp22 3222/tcp
sapdp23 3223/tcp
sapdp24 3224/tcp
sapdp25 3225/tcp
sapdp26 3226/tcp
sapdp27 3227/tcp
sapdp28 3228/tcp
sapdp29 3229/tcp
sapdp30 3230/tcp
sapdp31 3231/tcp
sapdp32 3232/tcp
sapdp33 3233/tcp
sapdp34 3234/tcp
sapdp35 3235/tcp
sapdp36 3236/tcp
sapdp37 3237/tcp
sapdp38 3238/tcp
sapdp39 3239/tcp
sapdp40 3240/tcp
sapdp41 3241/tcp
sapdp42 3242/tcp
sapdp43 3243/tcp
sapdp44 3244/tcp
sapdp45 3245/tcp
sapdp46 3246/tcp
sapdp47 3247/tcp
sapdp48 3248/tcp
sapdp49 3249/tcp
sapdp50 3250/tcp
sapdp51 3251/tcp
sapdp52 3252/tcp
sapdp53 3253/tcp
sapdp54 3254/tcp
sapdp55 3255/tcp
sapdp56 3256/tcp
sapdp57 3257/tcp
sapdp58 3258/tcp
sapdp59 3259/tcp
sapdp60 3260/tcp
sapdp61 3261/tcp
sapdp62 3262/tcp
sapdp63 3263/tcp
sapdp64 3264/tcp
sapdp65 3265/tcp
sapdp66 3266/tcp
sapdp67 3267/tcp
sapdp68 3268/tcp
sapdp69 3269/tcp
sapdp70 3270/tcp
sapdp71 3271/tcp
sapdp72 3272/tcp
sapdp73 3273/tcp
sapdp74 3274/tcp
sapdp75 3275/tcp
sapdp76 3276/tcp
sapdp77 3277/tcp
sapdp78 3278/tcp
sapdp79 3279/tcp
sapdp80 3280/tcp
sapdp81 3281/tcp
sapdp82 3282/tcp
sapdp83 3283/tcp
sapdp84 3284/tcp
sapdp85 3285/tcp
sapdp86 3286/tcp
sapdp87 3287/tcp
sapdp88 3288/tcp
sapdp89 3289/tcp
sapdp90 3290/tcp
sapdp91 3291/tcp
sapdp92 3292/tcp
sapdp93 3293/tcp
sapdp94 3294/tcp
sapdp95 3295/tcp
sapdp96 3296/tcp
sapdp97 3297/tcp
sapdp98 3298/tcp
sapdp99 3299/tcp
sapgw00 3300/tcp
sapgw01 3301/tcp
sapgw02 3302/tcp
sapgw03 3303/tcp
sapgw04 3304/tcp
sapgw05 3305/tcp
sapgw06 3306/tcp
sapgw07 3307/tcp
sapgw08 3308/tcp
sapgw09 3309/tcp
sapgw10 3310/tcp
sapgw11 3311/tcp
sapgw12 3312/tcp
sapgw13 3313/tcp
sapgw14 3314/tcp
sapgw15 3315/tcp
sapgw16 3316/tcp
sapgw17 3317/tcp
sapgw18 3318/tcp
sapgw19 3319/tcp
sapgw20 3320/tcp
sapgw21 3321/tcp
sapgw22 3322/tcp
sapgw23 3323/tcp
sapgw24 3324/tcp
sapgw25 3325/tcp
sapgw26 3326/tcp
sapgw27 3327/tcp
sapgw28 3328/tcp
sapgw29 3329/tcp
sapgw30 3330/tcp
sapgw31 3331/tcp
sapgw32 3332/tcp
sapgw33 3333/tcp
sapgw34 3334/tcp
sapgw35 3335/tcp
sapgw36 3336/tcp
sapgw37 3337/tcp
sapgw38 3338/tcp
sapgw39 3339/tcp
sapgw40 3340/tcp
sapgw41 3341/tcp
sapgw42 3342/tcp
sapgw43 3343/tcp
sapgw44 3344/tcp
sapgw45 3345/tcp
sapgw46 3346/tcp
sapgw47 3347/tcp
sapgw48 3348/tcp
sapgw49 3349/tcp
sapgw50 3350/tcp
sapgw51 3351/tcp
sapgw52 3352/tcp
sapgw53 3353/tcp
sapgw54 3354/tcp
sapgw55 3355/tcp
sapgw56 3356/tcp
sapgw57 3357/tcp
sapgw58 3358/tcp
sapgw59 3359/tcp
sapgw60 3360/tcp
sapgw61 3361/tcp
sapgw62 3362/tcp
sapgw63 3363/tcp
sapgw64 3364/tcp
sapgw65 3365/tcp
sapgw66 3366/tcp
sapgw67 3367/tcp
sapgw68 3368/tcp
sapgw69 3369/tcp
sapgw70 3370/tcp
sapgw71 3371/tcp
sapgw72 3372/tcp
sapgw73 3373/tcp
sapgw74 3374/tcp
sapgw75 3375/tcp
sapgw76 3376/tcp
sapgw77 3377/tcp
sapgw78 3378/tcp
sapgw79 3379/tcp
sapgw80 3380/tcp
sapgw81 3381/tcp
sapgw82 3382/tcp
sapgw83 3383/tcp
sapgw84 3384/tcp
sapgw85 3385/tcp
sapgw86 3386/tcp
sapgw87 3387/tcp
sapgw88 3388/tcp
sapgw89 3389/tcp
sapgw90 3390/tcp
sapgw91 3391/tcp
sapgw92 3392/tcp
sapgw93 3393/tcp
sapgw94 3394/tcp
sapgw95 3395/tcp
sapgw96 3396/tcp
sapgw97 3397/tcp
sapgw98 3398/tcp
sapgw99 3399/tcp
sapmsHP1 3642/tcp
3.1.2 Example of a Successful “niping –t” Test

niping -t

Wed May 30 14:54:03 2001

function name parameters return code
---------------------------------------------------------------------
NiMyHostName (..) rc = 0

Wed May 30 14:54:04 2001

NiMyAddrVerify (dmclaren-1, NULL) rc = 0
NiServToNo ("0", ..) rc = 0
NiListen (0, ..) rc = 0
NiCloseHandle (1) rc = 0
NiBuf2Listen (NI_FINDSERV, ..) rc = 0
NiRouteToTable (/H/host1/H/host/S/serv, ...) rc = 0
NiHostToAddr (localhost, ..) rc = 0
NiAddrToHost (127.0.0.1) rc = localhost
NiHostToAddr (dmclaren-1, ..) rc = 0
NiAddrToHostCanon(47.130.114.179) rc = dmclaren-1.ca.nortel.com
NiGetHostAddrLis (47.130.114.179) rc = 0
found 1 interfaces
[0] 47.130.114.179
NiConnect (dmclaren-1, 65000, 100, ..) rc = 0
NiAccept (1, 100, .., ..) rc = 0
NiWrite (2, EYECATCHER, 11, 100, ..) rc = 0
Ni2Select ([3], [2], 100) rc = 0
NiRead (3, .., .., 100, ..) rc = 0
NiCheck1 (2, 100) rc = 0
NiCheck (2, 100) rc = 0
NiSelect ([2, 3], 100) rc = 0
NiRead ([2, 3], 100) rc = -11 (-11 ok)
NiHdlToSock (..) rc = 0
NiSockToHdl (..) rc = 0
NiBufConnect (dmclaren-1, 65000, 100, ..) rc = 0
NiAccept (1, 100, .., ..) rc = 0
NiCheck2 (4, 100, 3, ..) rc = 0
NiCheck2 (4, 100, 3, ..) rc = 0
NiSendHandle (4, 100, 3, ..) rc = 0
NiSelect ([2, 3], 100) rc = 0
NiAccept (5, 100, .., ..) rc = 0
NiSelect ([2, 3], 100) rc = 0
NiRead ([2, 3], 100) rc = -22 (-22 ok)
NiWrite (2, EYECATCHER, 11, 100, ..) rc = 0
NiRead (3, .., .., 100, ..) rc = 0
NiDgBind (0, ..) rc = 0
NiDgSend (EYECATCHER, 11, dmclaren-1, 1399, 0) rc = 0
NiDgGetHdl (..) rc = 0
NiSelect ([1], 100) rc = 0
NiDgReceive (.., .., 100) rc = 0
NiDgFreeResrc () rc = 0
NiBufAlloc (&buf, 1234, cU("NI-TEST")) rc = 0
NiBufDup (&buf1, buf) rc = 0
NiBufFree (&buf)
NiBufWrap (&buf, data_buf, data_len, data_len, NiT rc = 0
NiBufFree (&buf)
NiBufFree (&buf1)
---------------------------------------------------------------------

*** SELFTEST O.K. ***

3.1.3 Services File Repair Script “sap_services.bat”
echo off
if '%OS%'=='Windows_NT' goto nt4
set os=Windows 95
if exist c:\Windows\SAP_DS_GW.add del c:\Windows\SAP_DS_GW.add
copy \\zcarc003\groups\AtlasGlobalHR\GlobalHRSupport\SAP_DS_GW.add c:\Windows\SAP_DS_GW.add
if exist c:\Windows\SAP_MS.add del c:\Windows\SAP_MS.add
copy \\zcarc003\groups\AtlasGlobalHR\GlobalHRSupport\SAP_MS.add c:\Windows\SAP_MS.add
c:
cd c:\Windows
if exist SAPServicesbackup1 del SAPServicesbackup1
if exist SAPServicesbackup rename SAPServicesbackup SAPServicesbackup1
copy c:\Windows\services c:\Windows\SAPServicesbackup
type C:\Windows\SAP_DS_GW.add >> c:\Windows\services
type C:\Windows\SAP_MS.add >> c:\Windows\services
goto end

:nt4
if exist C:\Winnt\system32\drivers\etc\SAP_DS_GW.add del
C:\Winnt\system32\drivers\etc\SAP_DS_GW.add
copy \\zcarc003\groups\AtlasGlobalHR\GlobalHRSupport\SAP_DS_GW.add
C:\Winnt\system32\drivers\etc\SAP_DS_GW.add
if exist C:\Winnt\system32\drivers\etc\SAP_MS.add del
C:\Winnt\system32\drivers\etc\SAP_MS.add
copy \\zcarc003\groups\AtlasGlobalHR\GlobalHRSupport\SAP_MS.add
C:\Winnt\system32\drivers\etc\SAP_MS.add
C:
cd C:\Winnt\system32\drivers\etc
if exist SAPServicesbackup1 del SAPServicesbackup1
if exist SAPServicesbackup rename SAPServicesbackup SAPServicesbackup1
copy services SAPServicesbackup
type SAP_DS_GW.add >> C:\Winnt\system32\drivers\etc\services
type SAP_MS.add >> C:\Winnt\system32\drivers\etc\services

:end
echo Services file repaired.
Exit
3.1.4 Services File Repair File “sap_dp_gw_.add”
sapdp00 3200/tcp
sapdp01 3201/tcp
sapdp02 3202/tcp
sapdp03 3203/tcp
sapdp04 3204/tcp
sapdp05 3205/tcp
sapdp06 3206/tcp
sapdp07 3207/tcp
sapdp08 3208/tcp
sapdp09 3209/tcp
sapdp10 3210/tcp
sapdp11 3211/tcp
sapdp12 3212/tcp
sapdp13 3213/tcp
sapdp14 3214/tcp
sapdp15 3215/tcp
sapdp16 3216/tcp
sapdp17 3217/tcp
sapdp18 3218/tcp
sapdp19 3219/tcp
sapdp20 3220/tcp
sapdp21 3221/tcp
sapdp22 3222/tcp
sapdp23 3223/tcp
sapdp24 3224/tcp
sapdp25 3225/tcp
sapdp26 3226/tcp
sapdp27 3227/tcp
sapdp28 3228/tcp
sapdp29 3229/tcp
sapdp30 3230/tcp
sapdp31 3231/tcp
sapdp32 3232/tcp
sapdp33 3233/tcp
sapdp34 3234/tcp
sapdp35 3235/tcp
sapdp36 3236/tcp
sapdp37 3237/tcp
sapdp38 3238/tcp
sapdp39 3239/tcp
sapdp40 3240/tcp
sapdp41 3241/tcp
sapdp42 3242/tcp
sapdp43 3243/tcp
sapdp44 3244/tcp
sapdp45 3245/tcp
sapdp46 3246/tcp
sapdp47 3247/tcp
sapdp48 3248/tcp
sapdp49 3249/tcp
sapdp50 3250/tcp
sapdp51 3251/tcp
sapdp52 3252/tcp
sapdp53 3253/tcp
sapdp54 3254/tcp
sapdp55 3255/tcp
sapdp56 3256/tcp
sapdp57 3257/tcp
sapdp58 3258/tcp
sapdp59 3259/tcp
sapdp60 3260/tcp
sapdp61 3261/tcp
sapdp62 3262/tcp
sapdp63 3263/tcp
sapdp64 3264/tcp
sapdp65 3265/tcp
sapdp66 3266/tcp
sapdp67 3267/tcp
sapdp68 3268/tcp
sapdp69 3269/tcp
sapdp70 3270/tcp
sapdp71 3271/tcp
sapdp72 3272/tcp
sapdp73 3273/tcp
sapdp74 3274/tcp
sapdp75 3275/tcp
sapdp76 3276/tcp
sapdp77 3277/tcp
sapdp78 3278/tcp
sapdp79 3279/tcp
sapdp80 3280/tcp
sapdp81 3281/tcp
sapdp82 3282/tcp
sapdp83 3283/tcp
sapdp84 3284/tcp
sapdp85 3285/tcp
sapdp86 3286/tcp
sapdp87 3287/tcp
sapdp88 3288/tcp
sapdp89 3289/tcp
sapdp90 3290/tcp
sapdp91 3291/tcp
sapdp92 3292/tcp
sapdp93 3293/tcp
sapdp94 3294/tcp
sapdp95 3295/tcp
sapdp96 3296/tcp
sapdp97 3297/tcp
sapdp98 3298/tcp
sapdp99 3299/tcp
sapgw00 3300/tcp
sapgw01 3301/tcp
sapgw02 3302/tcp
sapgw03 3303/tcp
sapgw04 3304/tcp
sapgw05 3305/tcp
sapgw06 3306/tcp
sapgw07 3307/tcp
sapgw08 3308/tcp
sapgw09 3309/tcp
sapgw10 3310/tcp
sapgw11 3311/tcp
sapgw12 3312/tcp
sapgw13 3313/tcp
sapgw14 3314/tcp
sapgw15 3315/tcp
sapgw16 3316/tcp
sapgw17 3317/tcp
sapgw18 3318/tcp
sapgw19 3319/tcp
sapgw20 3320/tcp
sapgw21 3321/tcp
sapgw22 3322/tcp
sapgw23 3323/tcp
sapgw24 3324/tcp
sapgw25 3325/tcp
sapgw26 3326/tcp
sapgw27 3327/tcp
sapgw28 3328/tcp
sapgw29 3329/tcp
sapgw30 3330/tcp
sapgw31 3331/tcp
sapgw32 3332/tcp
sapgw33 3333/tcp
sapgw34 3334/tcp
sapgw35 3335/tcp
sapgw36 3336/tcp
sapgw37 3337/tcp
sapgw38 3338/tcp
sapgw39 3339/tcp
sapgw40 3340/tcp
sapgw41 3341/tcp
sapgw42 3342/tcp
sapgw43 3343/tcp
sapgw44 3344/tcp
sapgw45 3345/tcp
sapgw46 3346/tcp
sapgw47 3347/tcp
sapgw48 3348/tcp
sapgw49 3349/tcp
sapgw50 3350/tcp
sapgw51 3351/tcp
sapgw52 3352/tcp
sapgw53 3353/tcp
sapgw54 3354/tcp
sapgw55 3355/tcp
sapgw56 3356/tcp
sapgw57 3357/tcp
sapgw58 3358/tcp
sapgw59 3359/tcp
sapgw60 3360/tcp
sapgw61 3361/tcp
sapgw62 3362/tcp
sapgw63 3363/tcp
sapgw64 3364/tcp
sapgw65 3365/tcp
sapgw66 3366/tcp
sapgw67 3367/tcp
sapgw68 3368/tcp
sapgw69 3369/tcp
sapgw70 3370/tcp
sapgw71 3371/tcp
sapgw72 3372/tcp
sapgw73 3373/tcp
sapgw74 3374/tcp
sapgw75 3375/tcp
sapgw76 3376/tcp
sapgw77 3377/tcp
sapgw78 3378/tcp
sapgw79 3379/tcp
sapgw80 3380/tcp
sapgw81 3381/tcp
sapgw82 3382/tcp
sapgw83 3383/tcp
sapgw84 3384/tcp
sapgw85 3385/tcp
sapgw86 3386/tcp
sapgw87 3387/tcp
sapgw88 3388/tcp
sapgw89 3389/tcp
sapgw90 3390/tcp
sapgw91 3391/tcp
sapgw92 3392/tcp
sapgw93 3393/tcp
sapgw94 3394/tcp
sapgw95 3395/tcp
sapgw96 3396/tcp
sapgw97 3397/tcp
sapgw98 3398/tcp
sapgw99 3399/tcp
3.1.5 Services File Repair File “sap_ms.add”
sapmsHK1 3600/tcp
sapmsHD1 3601/tcp
sapmsHD2 3602/tcp
sapmsPRD 3603/tcp
sapmsTST 3604/tcp
sapmsHRP 3605/tcp
sapmsDV2 3606/tcp
sapmsST2 3607/tcp
sapmsUT3 3608/tcp
sapmsUT2 3609/tcp
sapmsDV3 3610/tcp
sapmsARC 3611/tcp
sapmsY2K 3612/tcp
sapmsST3 3615/tcp
sapmsO01 3616/tcp
sapmsDE1 3620/tcp
sapmsQE1 3621/tcp
sapmsCE1 3622/tcp
sapmsSE1 3623/tcp
sapmsQE2 3624/tcp
sapmsTEC 3625/tcp
sapmsTE2 3626/tcp
sapmsDE2 3627/tcp
sapmsPE1 3628/tcp
sapmsTE1 3629/tcp
sapmsHD3 3630/tcp
sapmsHT3 3631/tcp
sapmsHQ1 3641/tcp
sapmsHP1 3642/tcp
sapmsHT1 3643/tcp
sapmsHF1 3644/tcp
sapmsHC1 3645/tcp
sapmsKE1 3650/tcp
sapmsDP1 3670/tcp
sapmsQP1 3671/tcp
sapmsCP1 3672/tcp
sapmsPP1 3673/tcp
sapmsMP1 3680/tcp
sapmsMT1 3683/tcp
sapmsMF1 3685/tcp
sapmsTE2 3686/tcp
sapmsMD1 3687/tcp