Degraded network (protocol problems?)

Degraded network (protocol problems?)

Post by Gerard Farrà » Tue, 22 Jun 2010 01:24:39



Hi!

We have in our network a Ubuntu server working correctly as a web
server & Linux Terminal Server but, unexpectedly, this machine
disconnects from the network. In this moments, this machine doesn't
response ping but it response with arping (I use Hardping tool [1]
from a Windows machine).

I think it's not a machine problem: It's a network problem. If we
disconnect some seconds some wires in our switch, this machine
responses again.

I heard something about protocol problems when there are to many
network traffic what... I don't know what we can do :-(

Any comment or suggestions ?

Thank you very much,

[1] http://www.hardping.com/

--
Gerard Farrs i Ballabriga
Coordinador TIC - Escola Arrels
http://www.escolaarrels.com

 
 
 

Degraded network (protocol problems?)

Post by Maxwell Lo » Tue, 22 Jun 2010 07:50:11



> Hi!

> We have in our network a Ubuntu server working correctly as a web
> server & Linux Terminal Server but, unexpectedly, this machine
> disconnects from the network. In this moments, this machine doesn't
> response ping but it response with arping (I use Hardping tool [1]
> from a Windows machine).

> I think it's not a machine problem: It's a network problem. If we
> disconnect some seconds some wires in our switch, this machine

Is the address static? Or is it DHCP assigned?
Perhaps another device is trying to use the same IP address?
What do the logs on the server say?

 
 
 

1. How does "Time Synch Protocol" relate to "Network Time Protocol"?

I am administering a SCO ODT system running
Unix System V release 3.2v4.2 on our local
network, and I am looking for some additional
information about the "Time Synchronization Protocol"
as mentioned in the SCO ODT Administrator's Guide.

I am also looking for information on the "Time Synchronization
Protocol" as well - which explains the cross-posting. I
apologize in advance if necessary.

From the manual:

   "...The time daemons communicate with each other
    using the Time Synchronization Protocol (TSP),
    which is built on the DARPA UDP protocol..."

Questions:

   1) Is the TSP proprietary to SCO?
   2) What is the difference (if any) between
       TSP and the "Network Time Protocol"?
   3) Has anyone out there successfully
        time-synched a SCO box with non-SCO
        boxes as either a master or a slave?
   4) If you are running a SCO box as a
       master or a slave, what types of machines
       and operating systems are in your network?
   5) Someone told me that NTP may actually
       be public-domain. If so, does anyone
       know where I might find a copy?
   6) If TSP *is* different than NTP, then
       does anyone know where I may find
       a list of machines that NTP will run on?

I am under the gun on this one, so I'd appreciate
any help you could provide.  "Time pressure, don'cha know"

Thanks

Angelo A. Keene
Lead Engineer Software
Harris Information Systems Division

--- flames cheerfully and promptly ignored ---

2. Differences between NFS2 and NFS3

3. Other computers HIGHLY degrading network performance (DoS?)

4. Getting Doom to work

5. More ipchains rules degrades network performance?

6. Apache+mysql on linux cluster!

7. degrading network performance -- wild ping times

8. printer stopped working

9. Network time protocol Sync Problem

10. Protocol-Reject for unsupported protocol 0xc001

11. demuxprotrej: Unrecognized Protocol-Reject for protocol 0x94f1

12. TCP, UDP protocols vs. Unix domain protocols

13. Protocol-Reject for unsupported protocol