Kbase P123508: Partial loss of network connectivity and DNS functionality leads to Unable to find <server> (8281)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/30/2009 |
|
Status: Verified
SYMPTOM(s):
Partial loss of network connectivity and DNS functionality leads to Unable to find NameServer (8281) error from nsman, asbman, wtbman and proadsv.
Unable to find NameServer (8281)
Cannot manage unified brokers from command line
Login denied, check username and password when running wtbman, asbman or nsman
AdminServer is up and running
The extranet connection has failed.
Intranet connection is active.
The DNS server resolution is for fully qualified domain names, not simple names.
Using nslookup of server simple hostname fails.
Using nslookup of server fully qualified domain name succeeds.
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
The DNS references for the machines within the intranet are incompletely defined. While the extranet connections are active the hosts are addressable but are not addressable by simple hostname.
FIX:
Complete the DNS servers references for all hosts related to the application (database server, AppServers, WebSpeed Brokers, etc) by adding simple hostname aliases to complement the Fully Qualified Domain Name (FQDN) references.
One partial workaround may be to modify the hosts file of all the application related systems:
Example of the poorly defined hosts file:
192.168.0.5 myhost.mydomain.com
Example of the hosts file with the simple hostname alias added:
192 168.0.5 myhost.mydomain.com myhost
stop the NameServer and restart it using the FQDN reference to the AdminServer.
Example:
nsman -i NS1 -port 20931 -H myhost.mydomain.com -stop
nsman -i NS1 -port 20931 -H myhost.mydomain.com -start