This is really getting on my nerves.
I have Road Runner, and have 3 computers on it. I have the cable modem going to a switch, and have a hub going off of the switch in another room. On the switch aside from the hub is one computer, which has no problem with the internet and the LAN. My Win2k computer on the hub off of the switch also works fine on the LAN and internet. Well, to work on my BSD box I moved it up onto the hub next to my win2k box. This computer has a problem. I can traceroute and ping it fine from a staff shell box, as well as the other two computers. But when I try to access it localy, over the one hop from one computer to another, I can't connect. I try to ping it from Windows, and I will get like 2 packets received and like 10 will timeout. I can't ssh to it, and when I traceroute, it ping pongs with this:
C:\>tracert xx.xx.xx.xx
Tracing route to xx.xx.xx.xx over a maximum of 30 hops:
1 * <10 ms * cm-xx-xx-xx-xx.nycap.rr.com [xx.xx.xx.xx]
2 <10 ms * <10 ms cm-xx-xx-xx-xx.nycap.rr.com [xx.xx.xx.xx]
Trace complete.
When I trace it from that same staff machine, as well as another machine in a seperate data center, I can trace to all 3 fine.
I would think it was a problem with the hub, but it can handle the traffic of both computers fine, until I try to connect from one to another. This is racking my brain.
The switch is a Linksys 5-port 10/100, and the hub is a 3com HomeConnect 5-port 10-baseT. The only thing that makes me think it's the hub is that I had this same setup about 1 month ago working fine. For nic's I have an SMC (realtek chipset) in the BSD box, a Netgear FA312 in the win2k box, and a Linksys something or another in the other (win me) comp.
Any ideas on what is going on woudl be appreciated
I have Road Runner, and have 3 computers on it. I have the cable modem going to a switch, and have a hub going off of the switch in another room. On the switch aside from the hub is one computer, which has no problem with the internet and the LAN. My Win2k computer on the hub off of the switch also works fine on the LAN and internet. Well, to work on my BSD box I moved it up onto the hub next to my win2k box. This computer has a problem. I can traceroute and ping it fine from a staff shell box, as well as the other two computers. But when I try to access it localy, over the one hop from one computer to another, I can't connect. I try to ping it from Windows, and I will get like 2 packets received and like 10 will timeout. I can't ssh to it, and when I traceroute, it ping pongs with this:
C:\>tracert xx.xx.xx.xx
Tracing route to xx.xx.xx.xx over a maximum of 30 hops:
1 * <10 ms * cm-xx-xx-xx-xx.nycap.rr.com [xx.xx.xx.xx]
2 <10 ms * <10 ms cm-xx-xx-xx-xx.nycap.rr.com [xx.xx.xx.xx]
Trace complete.
When I trace it from that same staff machine, as well as another machine in a seperate data center, I can trace to all 3 fine.
I would think it was a problem with the hub, but it can handle the traffic of both computers fine, until I try to connect from one to another. This is racking my brain.
The switch is a Linksys 5-port 10/100, and the hub is a 3com HomeConnect 5-port 10-baseT. The only thing that makes me think it's the hub is that I had this same setup about 1 month ago working fine. For nic's I have an SMC (realtek chipset) in the BSD box, a Netgear FA312 in the win2k box, and a Linksys something or another in the other (win me) comp.
Any ideas on what is going on woudl be appreciated