ping question..

[burnside]

when i ping my unix server from xp i get hop times of <1ms
and no packet loss
when i ping from unix to my pc i get hop times of 1000ms
and 75% loss

why does this loss not show from windows ping?

 

[pmcmicha]

What is your OS version?

Is your network card configured properly?
- Is this a new install?
- Has it ever worked correctly before?

Are your routes setup correctly on the unix side?

What happens during a traceroute?

 

[burnside]

thanks for your reply

server has been running for a few years fine
although we have just moved it to new location

i think my routes are setup ok - this side is managed by the DB company.
what routes do you mean my laptop is on the same ip range as server.

we are running SCO UnixWare 7.0.1 (RM8iTrident)

trace as follows
----------------
Tracing route to 10.170.200.100 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.170.200.100

Trace complete.

ping from windows
-----------------
Pinging 10.170.200.100 with 32 bytes of data:

Reply from 10.170.200.100: bytes=32 time<1ms TTL=64
Reply from 10.170.200.100: bytes=32 time<1ms TTL=64
Reply from 10.170.200.100: bytes=32 time<1ms TTL=64
Reply from 10.170.200.100: bytes=32 time<1ms TTL=64
Reply from 10.170.200.100: bytes=32 time<1ms TTL=64
Reply from 10.170.200.100: bytes=32 time<1ms TTL=64
Reply from 10.170.200.100: bytes=32 time<1ms TTL=64
Reply from 10.170.200.100: bytes=32 time<1ms TTL=64
Reply from 10.170.200.100: bytes=32 time<1ms TTL=64
Reply from 10.170.200.100: bytes=32 time<1ms TTL=64

Ping statistics for 10.170.200.100:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

ping from unix
---------------
PING 10.170.200.100: 56 data bytes
64 bytes from 10.170.200.100: icmp_seq=0. time=0. ms
64 bytes from 10.170.200.100: icmp_seq=1. time=1090. ms
64 bytes from 10.170.200.100: icmp_seq=6. time=1930. ms
64 bytes from 10.170.200.100: icmp_seq=8. time=1080. ms
64 bytes from 10.170.200.100: icmp_seq=14. time=1020. ms
64 bytes from 10.170.200.100: icmp_seq=20. time=1010. ms
64 bytes from 10.170.200.100: icmp_seq=27. time=900. ms
64 bytes from 10.170.200.100: icmp_seq=30. time=1090. ms
64 bytes from 10.170.200.100: icmp_seq=34. time=1130. ms
64 bytes from 10.170.200.100: icmp_seq=42. time=950. ms
64 bytes from 10.170.200.100: icmp_seq=46. time=940. ms
64 bytes from 10.170.200.100: icmp_seq=49. time=1070. ms

----10.170.200.100 PING Statistics----
53 packets transmitted, 12 packets received, 77% packet loss
round-trip (ms) min/avg/max = 0/1017/1930
#

ne ideas welcome

 

[pcunix]

Possibly bad negotiation: see

http://aplawrence.com/SCOFAQ/FAQ_scotec4autonegotiate.html

Tony Lawrence
Linux/Unix/Mac OS X Resources

http://aplawrence.com

 

[burnside]

why does windows ping not show prob-

results of ndstat -l

SCO UnixWare 7.0.1 (RM8iTrident) (pts/166)

login: root
Password:
UnixWare 7.0.1
RM8iTrident
Copyright (c) 1976-1998 The Santa Cruz Operation, Inc. and its suppliers.
All Rights Reserved.

RESTRICTED RIGHTS LEGEND:

When licensed to a U.S., State, or Local Government,
all Software produced by SCO is commercial computer software
as defined in FAR 12.212, and has been developed exclusively
at private expense. All technical data, or SCO commercial
computer software/documentation is subject to the provisions
of FAR 12.211 - "Technical Data", and FAR 12.212 - "Computer
Software" respectively, or clauses providing SCO equivalent
protections in DFARS or other agency specific regulations.
Manufacturer: The Santa Cruz Operation, Inc., 400 Encinal
Street, Santa Cruz, CA 95060.

Last login: Fri Jun 3 11:58:19 2005 on pts184


Sysbakp Reminder Running for users kcc root

Reminder - it is time to take a new Unix Operating System Backup (sysbakp)
----- No sysbakp taken for 30 days -----
# ndstat -l
Device MAC address in use Factory MAC Address
------ ------------------ -------------------
/dev/net0 00:90:27:62:a9:b9 00:90:27:62:a9:b9

Multicast address table
-----------------------
01:00:5e:00:00:01
01:00:5e:00:00:09

FRAMES
Unicast Multicast Broadcast Error Octets Queue Length
---------- --------- --------- ------ ----------- ------------
In: 14438828 8 1996659 0 1190699496 0
Out: 18794134 5 797 0 1793508689 0

DLPI Module Info: 2 SAPs open, 4096 SAPs maximum
2839295 frames received destined for an unbound SAP

MAC Driver Info: Media_type: Ethernet
Min_SDU: 14, Max_SDU: 1514, Address length: 6
Interface speed: 100 Mbits/sec

Interface Version: MDI 100

ETHERNET SPECIFIC STATISTICS

Collision Table - The number of frames successfully transmitted,
but involved in at least one collision:

Frames Frames
------- -------
1 collision 0 9 collisions 0
2 collisions 0 10 collisions 0
3 collisions 0 11 collisions 0
4 collisions 0 12 collisions 0
5 collisions 0 13 collisions 0
6 collisions 0 14 collisions 0
7 collisions 0 15 collisions 0
8 collisions 0 16 collisions 0


Bad Alignment 0 Number of frames received that were
not an integral number of octets

FCS Errors 0 Number of frames received that did
not pass the Frame Check Sequence

SQE Test Errors 0 Number of Signal Quality Error Test
signals that were detected by the adapter

Deferred Transmissions 0 Number of frames delayed on the
first transmission attempt because
the media was busy

Late Collisions 0 Number of times a collision was
detected later than 512 bits into
the transmitted frame

Excessive Collisions 0 Number of frames dropped on transmission
because of excessive collisions

Internal MAC Transmit 0 Number of frames dropped on transmission
Errors because of errors not covered above

Carrier Sense Errors 0 Number of times that the carrier sense
condition was lost when attempting to
send a frame that was deferred for an
excessive amount of time

Frame Too Long 0 Number of frames dropped on reception
because they were larger than the maximum Ethernet frame size

Internal MAC Receive 0 Number of frames dropped on reception
Errors because of errors not covered above

Spurious Interrupts 0 Number of times the adapter interrupted
the system for an unknown reason

No STREAMS Buffers 0 Number of frames dropped on reception
because no STREAMS buffers were available

Underruns/Overruns 3820 Number of times the transfer of
data to or from the frame buffer
did not complete successfully

Device Timeouts 0 Number of times the adapter failed to
respond to a request from the driver
#