Unix does not ping other machines in the network

[mayerling]

The Unix server can ping itself but it can not ping other computers in the network. What should I check ?
Thank you

 

[PHV]

The Unix server can ping itself but it can not ping other computers in the network
It can't ping other computer even by IP address ?
Take a look at ifconfig -a, netstat -rn, the contents of /etc/hosts.
You can also verify your NIC installation with netconfig.

Hope This Help, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[mayerling]

no, it could not ping computer even by their Ip's. I restarted the server.
This is the ifconfig -a output.

net0: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.1.1.11 netmask ffffff00 broadcast 10.1.1.255
perf. params: recv size: 24576; send size: 24576; full-size frames: 1
ether 00:06:29:05:9c:e1
lo0: flags=4049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask 7f000000
perf. params: recv size: 57344; send size: 57344; full-size frames: 1
atl0: flags=404a<BROADCAST,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 0.0.0.0 netmask 7f000000
perf. params: recv size: 4096; send size: 8192; full-size frames: 1

Also, the content of /etc/hosts differs from what I got with netstat -rn. I got the routing table where the firewall appears as well as the Unix server IP address. I wonder if do I need to have the devices listed on /etc/hosts on this routing table. I have this file to list remote printers and remote devices inside the LAN. Please let me know.Thank you

 

[PHV]

And what about traceroute IP@ofInsideLANdevice ?

Hope This Help, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[mayerling]

It works. It can find device inside LAN.

 

[PHV]

Passing thru the firewall ?
If so, maybe the firewall don't allow ICMP packets ?

Hope This Help, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[mayerling]

No, The Unix is not passing through the firewall. I restarted the server and it is OK, but I am concern if this happens again. How Do I know, if the Unix is not running out of resources (like memory). ?

 

[aseidas]

So the server is back on network again after rebooting? Any WARNING: eeE[0] - Lost Link messages in usr/adm/messages?
grep Link /usr/adm/messages

Maybe something as simple as in intermittant cable from the server to the switch??

-Aseidas

 

[PHV]

This may be of interest: thread58-454965 and thread58-728246

Hope This Help, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[mayerling]

No I did not get any warning after rebooting, but this is registered on syslog file (before restarting):
The /var/adm/syslog file says:
Feb 16 08:07:16 smbd ERROR: Could not determine network interface. You must use interfaces config line.

I think this happened after Samba 2.2.2 started running, this is the last new changed made on the Unix server.

 

[PHV]

Add something like this in the global section of your smb.conf file:
interfaces = net0

Hope This Help, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[stanhubble]

That usually only shows as a problem if you have more than one interface. does ifconfig -a still only show one?

 

[PHV]

stanhubble, net0 and atl0, as shown in the 3rd post.

 

[mayerling]

Should I add interfaces = net0 and atl0 as well ?

 

[mayerling]

PHV. Do I need to restart Samba /etc/ samba restart or it is enough with commiting changes ?

 

[stanhubble]

do not add atl0 as an interface for samba, and yes you need to restart samba after changing the smb.conf file. If you are using swat then there are restart buttons on the status page.