that *is* heavy packet loss - try increasing your buffers & insure that you
are not getting
heartbeat losses.
[log in to unmask]

Donna Garverick wrote:

> toback2 wrote:
> > Usually, this is caused by misconfiguration of the network software.
> > What's happened is that the network can't figure out how to route to
> > the requestor's address. The first few things to check are the
> > gateways, including the default gateway, and the netmask. (Make sure
> > your netmask matches the IP address class, e.g., 255.255.0.0 for class
> > B.)
> bruce (and chris bartram) is absolutely right - this machine's reach-
> able networks/gateways were not configured properly.  i added in
> the correct ip and things are happier.  but let me ask this...i've
> got another pc being used for this odbc work that occasionally
> gets this same 116 error and everything is configured properly!
> could heavy network traffic cause the 3000 to think that it
> can't reach this pc?  when i get into nettool, i'm seeing alot of
> packet loss - to the tune of 20-25%.  i think (swag!) it's due to
> traffic.  what do you think?  i'm considering adjusting some
> timers in nmmgr but it's just a thought....      - d
> --
> Donna Garverick     Sr. System Programmer
> 510/210-6631        [log in to unmask]
>
> >>>MY opinions, not Longs Drug Stores'<<<<