Can't get New L2000 on network by name

[Jim Rogers_5]

I am configuring a new L2000 server. It has dual gig NICs. I have assigned each an IP address. I can talk to each by pinging the IP address. What I can't do is see it on the network by its name.

Please help me. I know I must have missed something. Tell me what you want to see out put from and I can post.

[Mel Burslan]

from your workstation, where you are issuing ping commands, if you run

nslookup

can you get the right ip addresses ?

[Jim Rogers_5]

When I issue that command on the server it does resolve to the correct IP address. I can not see it on our windows network by name, only by IP address.

[Mel Burslan]

Well, you have more than one problem it sound like.

first if you want to connect to this server by name from your windows system, it needs to be placed in DNS system. Depending upon if you are the DNS admin or not, you need to do it or find the DNS admin to do it.

Wrong address resolution on the server itself is not good at all. This will cause you grief all the way, so let's work on that one.

Please provide the output of these commands:

cat /etc/hosts
cat /etc/nsswitch.conf
cat /etc/resolv.conf

also please let me know what the correct address should be, for comparison purposes

[Jim Rogers_5]

OK, the name DID resolve to the correct IP. I think there was a mis-communication there. Still not on the Windows network though. Here is the output you requested.

/ # cat /etc/hosts
/ # onfigured using SAM by root on Wed Sep 21 15:24:03 2005
# @(#)hosts $Revision: 1.9.214.1 $ $Date: 96/10/08 13:20:01 $
#
# The form for each entry is:
#
#
# For example:
# 192.1.2.34 hpfcrm loghost
#
# See the hosts(4) manual page for more information.
# Note: The entries cannot be preceded by a space.
# The format described in this file is the correct format.
# The original Berkeley manual page contains an error in
# the format description.
#

192.168.100.9 BMCHP2
127.0.0.1 localhost loopback
/ # cat /etc/nsswitch.conf
#
# /etc/nsswitch.conf
#
# This is the default configuration file for the name service switch.
# It will cause behavior similar to that performed on prior HP-UX
# releases when a configurable name service algorithm was not provided.
#
# If the /etc/nsswitch.conf file is not present, it will default to the
# behavior represented by the ordering and conditions below.
#
# See the Adminstering Internet Services Manual and the switch(4) man
# page for more information on the name service switch.
#

hosts: files[NOTFOUND=continue UNAVAIL=return] nis [NOTFOUND=return UNAVAIL=cont
inue TRYAGAIN=return]

services: files
protocols: files
networks: files
rpc: files
netgroup: files
automount: files
/ # cat /etc/resolv.conf
domain buntingmagnetics.com
nameserver 192.168.100.7
/ #

192.168.100.9 is the correct IP for the one NIC I have turned on right now. .7 is our server that runs DNS.

[Mel Burslan]

Are you using NIS server in your architecture somewhere ? if not, your only resolution ,ethod in and out of this server is /etc/hosts file. DNS server doe snot get referenced at all.

if you are using NIS, your configuration may be fine, as I don't know your internal architecture and do not know much about NIS other than few horror stories I have been thru in the past.

if NIS is totally out of picture, modify the following line in /etc/nsswitch.conf file as follows:

hosts: files [NOTFOUND=continue TRYAGAIN=continue UNAVAIL=continue] dns [NOTFOUND=continue TRYAGAIN=continue UNAVAIL=return]
(yours is quite different)

and not but not the least, make sure this server's name and IP address gets in to the DNS database so that you can reference it by name instead of the IP address from the windows side. Otherwise, you will not be able to.

[Robert-Jan Goossens_1]

Hi,

an other thing to check is the lanspeed, this should be the same on your switch port and on your nic.

use 1000 mb autoneg on.

Hope this helps,
Robert-Jan

[Jim Rogers_5]

I just figured it out. My network admin told me, emphatically even, that there was not static routing for the existing server. So I was trying to get the new server to be visible on the network with similar setting. I poked around in his WINS setup and found that there is a static link for the old server Ip and name.

Thank you for all of your suggestions.

[Devesh Pant_1]

Change the nis in your /etc/nsswitch.conf to a dns and if the dns entries are present on the dns server and if you are able to ping the dns server by the IP address, you should be all set

thanks
DP

[Jim Rogers_5]

problem solved