At 12/26/05 15:29, Eric Hines wrote:
Folks,
I'm having a problem with my LAN, and I'm sure it's something I'm doing that's utterly brain dead that I haven't found, yet. One PC can't get connectivity even into its subnet on the LAN, much less via that LAN onto the Net.
I'm running SUSE Pro 9.3 on an Intel server that has two NICs on the motherboard, and a third NIC installed later as a daughter board. When I first set this up, all three NICs had direct access to the Net through a separate Linksys router serving also as a firewall, so I believe the NICs and the cabling, at the hardware level, are functional. I have since rearranged my LAN into two subnets (using the same cabling as earlier). I have one NIC facing the Net through the Linksys, with NIC's address set to 192.168.1.2. The other two NICs each run a subnet (one on .3.1 and the other on .2.2). I have a laptop dual bootable with SUSE Pro 9.3 and WinXP on the 3.1 subnet, and I have a Win2k PC on the 2.2 subnet. <snip> My Win2k PC, when plugged into the 2.2 NIC on the server, has no connectivity to the Net. Indeed, there is no connectivity at all--the lights on the NICs (both on the PC and on the server) all remain dark. When I plug the PC directly into the Linksys (which was the PC's original configuration), I get (back) onto the Net. <snip>
Like I said, I was doing something utterly brain dead. Connecting my Win2k PC's NIC to my server's NIC wants a cross-over cable, vice a straight cable. Doh. Sorry for the spam. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell