12-15-2008
Hello Skiturn,
I agreed with Otheus when he says that you should print the output of "netstat -nr"
You telling that the server on the same network can ping and access I think about routing problem (Maybe both networks are not talking....)
But you telling also that if you change your Solaris for a Windows starts to work.....
This is strange if we consider network Issue.
But if you also say that the machine on the same network can access and ping the server.... maybe you should take a look for this routing....
Regards,
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, dear all, I am rather new to Unix and have this problem where I cant seem to ping from 1 host to another. The scenerio is as follows: -
1 QNX host->Eth->1 SCO host
the SCO host is configured with it's IP
the QNX host is configured with another IP
both in the same domain, ie, 172.20.3.XX... (3 Replies)
Discussion started by: gavon
3 Replies
2. UNIX for Dummies Questions & Answers
I have Sco openserver 5.0. It had a 125. ip. I changed it to a 192. ip. was unable to ping the 192. I was told to change it in the
etc/tcp
etc/hosts
files which i did. still unable to ping.
i am getting a message unable to route to host.
I also have an error in my etc/tcp file on line... (1 Reply)
Discussion started by: pdoug76
1 Replies
3. UNIX for Dummies Questions & Answers
HI,
I am new to unix. I have used some basic commands and written some simple shell scripts in teh past. Currently, I am supposed to write a script to continuosly check if a couple of machines are up and if not to start a script. I am using a bash - 2.03. I have tryying to use the ping command... (3 Replies)
Discussion started by: swepaul
3 Replies
4. UNIX for Dummies Questions & Answers
DEar all
i am receiving this error on start and then unable to ping
(dlpid): unable to open network adapter driver (/dev/mdi/e3h0)
what to do ? (2 Replies)
Discussion started by: sak900354
2 Replies
5. IP Networking
We are unable to bring one of our linux boxes into the network once it was restarted. But once we stop and start the network service. We are able to ping the gateway and get into network. After a minute or two we get the following reponse for the ping command
64 bytes from 124.168.215.40:... (6 Replies)
Discussion started by: chrisanto_2000
6 Replies
6. Solaris
hi,
I setup a Solaris machine in my server room and my client cannot access it. Can anyone advise?
Test that i have done:
-My client pc cannot ping the server.
-My solaris server cannot ping client
-My solaris server can ping it's gateway
-Another NT machine 1 (10.179.30.26) in the server... (2 Replies)
Discussion started by: skiturn
2 Replies
7. Solaris
Hi ALL,
I Have installed NEW v240 server through hyper terminal, After installation i unable to ping the server from out side server... i can see no entry in resolve.conf file.. but the server has DNS.. willl that issue.. please guide me ping the server from outside within the same network
bk (1 Reply)
Discussion started by: suresh_krish
1 Replies
8. Solaris
Hello,
Am unable to ping the Windows Box, from my Solaris Box.
They both are in same LAN, have the same IP Segments.
Windows IP :: 10.141.14.120
Solaris IP :: 10.141.14.11
Unable to get why isnt working out.... When using the command 'ping 10.141.14.120', it gives the error as 'ping:... (4 Replies)
Discussion started by: jayanto
4 Replies
9. AIX
Hi all,
I have gone through many posts related to this issue,but my issue wasn't resolved hence creating new thread.
I am unable to ping localhost.
ping localhost tries to ping localhost which is defined in DNS.
My /etc/hosts has entry for localhost as
127.0.0.1 loopback localhost.
... (8 Replies)
Discussion started by: chpsam
8 Replies
10. Solaris
Hi All,
I am new to solaris environment and we are using Solaris 9
The problem is am unable to ping a particular server from from one of the solaris server
The traceroute also shows only * * * for all the 30 hops
I tried to check all the settings like
1) /etc/hosts -> contains the... (17 Replies)
Discussion started by: Sanjay255
17 Replies
ping(8) System Manager's Manual ping(8)
Name
ping - send ICMP ECHO_REQUEST packets to network hosts
Syntax
/etc/ping [ options ] host [ datasize [ npackets ]]
Description
The DARPA Internet is a large and complex network of hardware connected together by gateways. The command utilizes the ICMP protocol's
mandatory ECHO_REQUEST datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway. ECHO_REQUEST datagrams (pings) have an IP and ICMP
header, followed by a struct timeval, and then an arbitrary number of pad bytes used to fill out the packet. The length of the default
datagram 64 bytes, but this may be changed using the command-line option.
Typing ``ping host'' without any options will either report ``host is alive'' or ``no answer from host''. To get more statistics use the
-l option or one of the other options.
When using for fault isolation, it should first be run on the local host to verify that the local network interface is up and running.
Then, hosts and gateways further and further away should be pinged. The command with options sends one datagram per second and prints one
line of output for every ECHO_RESPONSE returned. No output is produced if there is no response. If an optional npackets is given, only
that number of requests is sent. Round-trip times and packet loss statistics are computed. When all responses have been received or the
program times out with npackets specified, or if the program is terminated with a SIGINT, a brief summary is displayed.
Options
-d Turns on SO_DEBUG flag on the socket.
-l Gives more statistics than if is used without options. Long output.
-r Bypasses the normal routing tables and sends directly to a host on an attached network. If the host is not on a directly-attached
network, an error is returned. This option can be used to ping a local host through an interface that has no route through it. For
example, after the interface was dropped by
-v Lists ICMP packets other than ECHO RESPONSE that are received. Verbose output.
Restrictions
This program is intended for use in network testing, measurement, and management. It should be used primarily for manual fault isolation.
Because of the load it could impose on the network, it is unwise to use during normal operations or from automated scripts.
See Also
netstat(1), ifconfig(8c)
ping(8)