- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Address resolution problem
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-15-2004 09:17 AM
тАО01-15-2004 09:17 AM
Address resolution problem
The names have been changed to protect the innocent...
Local server
IP = 146.11.11.11
Hostname = myserver.mydomain.com
Remote server
IP = 146.22.22.22
Hostname = remserver.remdomain.com
I have added all of the followint to the remote .rhosts file
146.11.11.11
myserver
myserver.mydomain.com
When I try to remote login to - it asks for a password (which I give).
When I enter the "who -a" command, I fond that the remote server resolves my server as
cc011011.corpdomain.com
where 011011 are the last 2 fields of my IP address and corpdomain.com is our corporate domain.
Any ideas?
Thank you
Joe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-15-2004 09:23 AM
тАО01-15-2004 09:23 AM
Re: Address resolution problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-15-2004 09:24 AM
тАО01-15-2004 09:24 AM
Re: Address resolution problem
Cam you give us the nslookup output from source server ( myserver )on the traget server ( remserver).
1.Can there be aliases configured in DNS.
2. Is /etc/hosts wrong
3. /etc/nsswitch.conf hosts line ( DNS files ?)
4. /etc/resolv.conf search or domain string?
Gideon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-15-2004 10:45 AM
тАО01-15-2004 10:45 AM
Re: Address resolution problem
If you simply say "nslookup 146.11.11.11" on that server, it should print out the information from where it is picking up the hostname like
Using /etc/hosts on: blablabla
looking up FILES <---
Trying DNS <---
Name: cc011011.corpdomain.com
Address: 146.11.11.11
The above output is dependent on what you have in /etc/nsswitch.conf. You can find out if the DNS server is returing the above address.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-15-2004 01:29 PM
тАО01-15-2004 01:29 PM
Re: Address resolution problem
Server B .rhosts file example:
111.222.333.444 rworkman
Since I'm on server A logged in as rworkman I can now rlogin to Server B.
On both servers follow the advise above to ensure you can nslookup properly both servers from both servers.
Then make sure there is nothing stopping you like inetd.sec refusing rlogin ... or some firewall issue saying that subnet ~333.x can not access subnet ~xxx.x (serverA).
Just a thought,
Rita
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-16-2004 08:56 AM
тАО01-16-2004 08:56 AM
Re: Address resolution problem
assigned at the local site. Our corporate DNS policy is to resolve and 146.47
address to ccXXXYYY.corpdomain.com if it doesn't resolve to something else
first.
We are using DNS. Our DNS servers are Windows boxes (I don't know what
type). Our HPUX config consists of only the resolv.conf and nsswitch.conf
files. Our files look like the following...
resolv.conf
search mydomain.com remdomain.com corpdomain.com
nameserver 146.47.XXX.YYY
nameserver 146.47.XXX.ZZZ
nsswitch.conf
hosts: files [...] DNS [...]
We include only local workstations/servers in our /etc/hosts file, so DNS
should resolve any remote addresses.
When I do a nslookup on my local server, everything works as expected.
When I do a nslookup on the remote server, I get the following ...
nslookup myserver
*** Can't find server name for address 146.47.XXX.YYY: Non-existent domain
*** Can't find server name for address 146.47.XXX.ZZZ: Non-existent domain
*** Default servers are not available
Using /etc/hosts on: remserver
looking up FILES
Trying DNS
*** can't find myserver: No response from server
These ARE the correct DNS server IP's
From my server, if I do a nslookup 146.47.XXX.YYY, I receive
ccXXXYYY.corpdomain.com. If I do a nslookup remdns.remdomain.com, I
receive the correct 146.47.XXX.YYY address. Is it that the DNS server
(remdns) cannot reverse lookup its own IP?
Strange the "who -a" will resolve the IP to cc######.corpdomain.com and
nslookup fails completely.
I am the admin for the local HPUX workstations (no access to DNS server admin).
I am in Pennsylvania.
The remote systems are in Brazil, where I have no admin authority, so it's
difficult for me to try a bunch of ideas.
My inetd.conf file in all locations has the "-s" option in the shell (remshd)
and login (rlogind) statements. Will removing the -s from the Brazil HPUX
servers help this?
Ultimately I would like the Brazil servers to respond with either
myserver.mydomain.com or 146.47.11.11. I do not want cc011011.corpdomain.com.
Thank you,
Joe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-16-2004 09:10 AM
тАО01-16-2004 09:10 AM