Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Ping Hostname

Status
Not open for further replies.

pakamish

MIS
Aug 31, 2005
7
EU
We have three netware 6.5 servers and 1 Windows 2003 server. One of the netware servers and the windows server is on the same subnet. The other two netware servers are on different subnets each. I can ping the windows server from the two netware servers, one on the same subnet as windows and one on the other. I Cannot ping the windows server from the other netware server. The route.cfg and hostname files on the all the servers have the same entries. Please help if this makes sense.
 
Sounds like you are going in the right direction, this sounds like a routing problem. For a ping to work, the sending computer has to know the route to the receiving computer, AND the receiving computer has to know the route back to the sending computer. In this case it sounds like the Windows server does not have the route back to one of the Netware servers. If you have a router in between the 3 subnets, check the routers route table. If you are using one of your servers as the router, you need to check that servers route table.
 
I can ping the ip address. The problem is with pinging the hostname.
 
On the Netware server, when you run
PING WindowsServer
does the ping.nlm resolve the name to an IP address and is that IP address correct?

Check
sys:etc\resolv.cfg
needs to list your DNS server
your DNS server has to have an A record for the Windows
server
sys:etc\hosts

In Netware 4 the separation between IP address and host name had to be by spaces, NOT tab.

What Netware version?
 
The entries is exactly the same as on the other netware servers. We are running netware6.5. I checked all the basic stuff.
 
If you can ping by IP address but not by name, the problem is the name resolution on the netware server.
When you run 'ping windowsserver' does the ping.nlm come back with a cannot resolve, or does it come back showing that it is pinging an address?
If ping.nlm does NOT resolve then we have to check why not.
Netware checks the HOSTS file first, then uses the resolve file to identify it's DNS servers. If the windowsserver name is in the hosts file, then we have to check to ensure that Netware is reading the HOSTS file.
Netware conforms to Unix standards when querying a DNS server. If the first DNS server in the list responds at all then Netware does NOT query the second DNS server. You have to make sure the first listed DNS server can resolve the windowsserver name, either by having the domain zone file, or is configured to use the DNS server that does have the zone file as a forwarder.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top