TCP/IP and NFS FAQ
This article is from a FAQ concerning SCO operating
systems. While some of the information may be applicable to any OS,
or any Unix or Linux OS, it may be specific to SCO Xenix, Open
Desktop or Openserver.
This is an old article about SCO Unix and is only left here for historical purposes.
There is lots of Linux, Mac OS X and general Unix info elsewhere on
this site: Search this site is the best
way to find anything.
"portmapper is not responding" usually means that there is an
incorrect extra ip address in /etc/hosts for this machine. Remove
the incorrect address( this usually happens when you change the
tcp/ip address). Here's an example of what such a /etc/hosts file
would look like:
# @(#)hosts,v 6.1 1993/08/21 02:17:48 stevea Exp - STREAMware
# SCCS IDENTIFICATION
10.1.36.8 scobox scobox.fredness.com
10.1.36.7 scobox scobox.fredness.com
The machine's IP address has been changed, but the old entry is
still present. Remove it. This could also be caused by not having
any entry in /etc/hosts, or by having an entry that is different
than what ifconfig shows. An unconfigured network can cause this
too, so a dhcp failure could do it (though of course then no
networking would be working at all).
The portmapper is used by NFS, so you could also disable NFS
startup by commenting it out of the startup files in /etc/rc2.d. If
you need nfs, and everything else looks right, try "nfs stop;nfs
See also: http://aplawrence.com/cgi-bin/ta.pl?arg=102428
Michael DiCostanzo provided this:
I have an OpenServer 5.0.5 Enterprise server. The
original name and IP address, call them NAME1 and IP1, were
registered with our DNS servers. I had a need to change the name
and IP address and did so, call these NAME2 and IP2. This name was
also registered with our DNS. I had omitted to remove the original
entry from the DNS.
I was getting the portmapper warning message
after rebooting. I checked here and SCO and found the article which
said to remove NAME1 and IP1 from the /etc/hosts. I did that yet
still got the portmapper warning message.
I had some time recently and did some admin tests
for other reasons. I found the article "How to change a system name or IP address
on SCO Unix" and used it to find that NAME1 still was being
used in some other files. Once I changed NAME1 to NAME2 in those
files, the portmapper warning message went away.
This may be a second time when the portmapper
warning is made. It's related to the first because the name change
was not completely made. If anyone gets this warning and the
/etc/hosts file is correct, it means that the name/IP address
change was not complete.
If this page was useful to you, please help others find it:
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Jump to Comments
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.