Dejawin Lost Connection

[Bill Vermillion]

Mike Schwartz-PC Support & Services, the prominent pundit, on Thu, Jul 22 10:18  while half 
mumbling half-witicized: 

> > We are running filePro on a SCO Unix system using DejaWin.
> > There is a problem, I believe occurring daily, where the
> > users get kicked out of the system. I have had it happen to
> > me. I'll be working along in

>  This is pretty off-topic for this group, although several of
> us use dejawin. I doubt that the issue is with dejawin, because
> it is very stable at the few client sites where I am using it.
> However, if you think you have a good, stable network and that
> the issue is with dejawin, you should try contacting the tech
> support people at Facet Corp. They are excellent people to work
> with.

>  Most likely this has nothing to do with dejawin. If this is
> an internal network that you are talking about, then I think
> you have hardware network issues that you need to look into.
> Try starting a ping from one computer on the network to the
> server or to another computer on the network and see if the
> ping terminates or has timeouts. It could be anything from
> a bad network card someplace on your system to a faulty or
> misprogrammed router or switch or even just an intermittent
> cable.

Just an FYI.   You couple perform   'ping nnn.nnn.nnn.nnn'
and never see a problem and therefore think everything is OK.

That is not true, and I had to trouble shoot a problem system
for a person and plain old pings worked just fine.

The default packet size of a ping is 56 bytes and add the 8 byte
ICMP header and it is now 64 bytes long.

Try   ping -s 500 nnn.nnn.nnn
And if that works try  ping -s 1400 nnn.nnn.nnn.nnn

The first is a size small enough for dialups with smaller packets
before fragmenting, and the latter is low enough to keep from
fragmenting even if the maximum number of headers is used - 
8 headers at 8 bytes each.

The -s sets packetsizes on all "ping"s that I have used. You can
always try man ping if you are not sure. Do not accidentally type
S as that want's a source address. [ An aside. S is handy in machines
with more than one NIC. I've also used that in a network with
several routers by sending from the far to the local and finding
it failed because of routing table mismatches. The default route
on the far machine was not set to be the near machine. ]

You man find that a ping works, but pings at larger sizes wont.

For the problem site pings works, as the packet size went up
I got more lost packets.   Once I crossed the 1500 byte packet
size it got worse.  While a another machine in the same switch
could flawless handle packet sizes of 8000 bytes, the problem
machine had 100% failure at that point.

I really didn't need to go past 1500 but I wanted to see just where
it failed.

So when using ping start with the default and work up just under
the default maximum for ethernet, and then you will know if 
things really work the way you think they should.

-- 
Bill Vermillion - bv @ wjv . com