You're definitely not routing via his machine?
Can you remoooove his machine from the switch and make
sure you can connect fine?
Use something like tcpdump without any filters,
just to see network traffic moving, and see what happens when you unplug
his machine, if everything stops, which by the symptoms you describe, will
more than lightly be a yes.
Does the switch have an IP? Can you get a console on it, and try to ping
your machine from the switch when his is disconnected.
Basically i would yank his machine from the switch, make sure you can
connect fine first. Then work from there.
Tell us more info on the IP setup for the diagram you provided.
I can;t think of what would be wrong, but check your arp cache.
-thor
> >>>>> "Erik" == Erik Curiel <[EMAIL PROTECTED]> writes:
>
> Erik> Don't even bother trying to diagnose it. Just move your box
> Erik> to the other switch. You could waste days trying to track
> Erik> down network bug-outs like that.
>
> Not a great option for me. Switch 1 and 2 are really far from each
> other and I already ran a 100 foot ethernet cable between them and
> around firewalls (the old fashioned cinderblock kind) to join up one
> set of offices with another on the LAN. So it's a pain in the ass to
> rewire and this will crop up again anyway as we want to add more
> machines onto the LAN in the set of offices that share switch #1.
>
> JDH
>
> _______________________________________________
> Bits mailing list
> [EMAIL PROTECTED]
> http://www.sugoi.org/mailman/listinfo/bits
>
--
.........................
: highpointlowlife.com :
: 8bitrecs.com :
: tsktskrecords.com :
::::::::::::::::::::::::::
_______________________________________________
Bits mailing list
[EMAIL PROTECTED]
http://www.sugoi.org/mailman/listinfo/bits
