[Cialug] Network response!

[David Champion]

I was kind of wondering that... what does this give you back (you may 
have to be root or sudo to use it) :

mii-tool eth0

Should show something like this:
eth0: no autonegotiation, 100baseTx-FD flow-control, link ok

Sometimes you have equipment that won't auto-negotiate the connection 
correctly (starts with a "3" and ends with a "Com").

Also do this:

ifconfing eth0

... and look to see if there are a lot of errors.

I would agree that if the "search" line in your /etc/resolv.conf doesn't 
resolve, that should be fixed by your network admin.

... and Ken's right, each OS has it's own network stack that handles the 
protocol differently, even though they're getting the same data. Even 
different versions, or network card drivers, or a bad network card can 
cause them to act differently.

-dc

Dan Schlichting wrote:
> What kind of equipment are you using. If it is an action tek. I know 
> the older ones I had trouble with. there was a bug in the way it 
> handed out dns. I had to either set static dns in the router or I just 
> setup my own dhcp server in house.
>
> To me this is what is happening. Your router is probably at fault.
>
> my .02
>
> Dan
>
> On Tue, Feb 17, 2009 at 10:22 PM, kristau <kristau at gmail.com 
> <mailto:kristau at gmail.com>> wrote:
>
>     On Tue, Feb 17, 2009 at 9:56 PM, Dave J. Hala Jr. <dave at 58ghz.net
>     <mailto:dave at 58ghz.net>> wrote:
>     > No. The protocols are the same. Don't think in terms of the
>     operating
>     > system, think in protocol context. DHCP, TCP, UDP, etc...
>
>     I'm thinking in terms of how the OS responds or reacts to the
>     protocol.  In other words, the implementation of the protocol on each
>     OS may be different.
>
>     --
>     Tired programmer
>     Coding late into the night
>     The core dump follows
>