-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hah! That took awhile, but the duplicate IP question got me thinking down that path and I found the one-in-a-billion duplicate...
A duplicate _MAC_ address. Whoa, that was a zebra. But at least you all got me thinking down some alternative paths and I was able to put a new NIC in the box. Everything works now! Thanks again, - -- Ed V. IBM: It's Better 'morrow Stuart Henderson wrote: > On 2006/02/09 12:24, B.O.F.H. wrote: >> Network card: >> >> Marvell Yukon 88E8001/8003/8010, rev 0x13, Marvell Yukon Lite (0x9) >> using the sk0 driver. >> >> It has an associated PHY of: Marvell Yukon 88E1011 Gigabit PHY, rev. >> 5 using the eephy0 device. >> >> It's attached to port 2 of a Cisco 3524 10/100 switch and >> autodetects at 100baseT full-duplex. >> >> The other PC is attached to port 4 of the same switch and is in the >> same VLAN group. > > That doesn't fit with any of the things I thought of (short nat or > firewall timeouts or devices having trouble with rfc1323, which I've seen > on some ADSL routers)... > > There aren't any IP address conflicts, I take it? That may cause > something like this, but I guess you probably would have noticed. iQIVAwUBQ+zWgafRmhqF/IZAAQqxzg/+ODq4eLXdTg/KoLCDNnkWwDMnIToM+6Fv +SVJofl9AziNqeGeVS2lR6WlDiaR3hMkcIf3shmjybWOvZqTntwZ4vGwhkyg/Lbq TfjtU2j5KdAMVjITtrTuemy4aq1llov/k7J4KGAdYWhJano8hftmienelWKqJWJe sxtSWWU05plU2UHOAOVLvLtMnm1MgGuoLpwV+xhgxgkQNxw297O7B+BsVaX0IoF7 ecYspR4Abi6ftPzvjwMKL3+0LUG2oazFk+3l+8tkVMIB406puyZZsOaHgd1jWFWU yKk+CqWGykbY6AAMp5uQeeppipp+c+eMTC5fPagAulz6dJ3bNJUW+4WNZuRTDZye S2zv+y9S3oNtINd4zyTwLpu/t8TgxVa6m8yjxDZAH5YV1ATBGzUZMoxA/4/JFUAd JcTlPllhc7+ZphR4RYAGZjvP5BXDGCr8uyNETjhwzdaUM4l6N1TRbA8AXrxoOu55 /dlT3S6IO0Za03EjQmn3u73DVLEZ3KQTn36ax40GgixshsrF8Mc7jG+HZjAmpZEA Rlg34YqomIJedJobdspUwe+uCvXsUB2/yknt1E3U4LTK8cgd14r4PMiH62MVi0Zx H1zaabpcHo/C+S8ot+nfjnhW6q4695cUGxHYhpRS78lay49ZR9aazDOid3+QVIRZ 7qz+lgbDZKg= =BQ8w -----END PGP SIGNATURE-----
