| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 68171 | 2006-04-20 01:47:00 | XP loads network fails | MrBeef (342) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 447810 | 2006-04-20 01:47:00 | Hi there, I just brought my comp home from having a LAN with a mate, it was working perfectly fine. And I hooked it all up at home and booted it up and the Host computer says network connected active, and then as the client loads xp it says the network cable has come unplugged. Whats going on? |
MrBeef (342) | ||
| 447811 | 2006-04-20 02:01:00 | Do you have another cable to test with? other than ensuring cable plugged in ok, check system device to ensuring no issue with ethernet port | SolMiester (139) | ||
| 447812 | 2006-04-20 02:21:00 | I dont exactly have another cable i can test with. When i ping from the Home computer to mine, it says requst timed out. When i ping from my computer to the home, it says destination host unreachable ping 127.0.0.1 both shows up fine |
MrBeef (342) | ||
| 447813 | 2006-04-20 02:38:00 | Ping 127.0.0.1 is the local loopback, so it's pretty much a meaningless test. It just test the stack. I realise it's a major investment, on par with a home or car purchase, but you might want to take SolMiester's advice and buy another cable. |
kingdragonfly (309) | ||
| 447814 | 2006-04-20 02:46:00 | It's not the cable. A faulty cable would not give either of those messages. You took one machine away and installed it on another LAN. It was given an IP address which worked on that other LAN. Now it's back on your LAN, that IP address does not work. That's why you get those messages. |
Graham L (2) | ||
| 447815 | 2006-04-20 02:47:00 | How is it connected?? Is it using a crossover cable, or is it connected thru a hub? |
Speedy Gonzales (78) | ||
| 447816 | 2006-04-20 02:56:00 | It's not the cable. A faulty cable would not give either of those messages. You took one machine away and installed it on another LAN. It was given an IP address which worked on that other LAN. Now it's back on your LAN, that IP address does not work. That's why you get those messages. Yes, could be static addresses, however I would of though he would be aware of that having had to setup for mates LAN. Not entirely correct with regards to faulty cable thou Gray. At boot ethernet port tested for operational, not transport protocol. Cable could be failing on TCP/IP. I have had IPX/SPX working while TCP/IP doesnt on a cable before. If it was incompatible IP address ranges it would say limited or no connectivity The posters description is vague on whats going on thou!.... |
SolMiester (139) | ||
| 447817 | 2006-04-20 03:03:00 | "Request timed out" means that the source computer's TCP/IP stack is working, and it has a physical link (so the cable is OK). The other end is not responding. "Destination host unreachable" means that it is on a different network, and there is no known route to it. The other end is not responding, because it's never receiving any packets, because it's on a different network. (So the cable condition is irrelevant. ;D | Graham L (2) | ||
| 447818 | 2006-04-20 03:13:00 | Yes, could be right, however, I didnt have that information when I replied to 1st post... :illogical | SolMiester (139) | ||
| 447819 | 2006-04-20 08:29:00 | well in an effort to rectify the problem i removed my network card. booted xp and then turned it off. chucked in a different network card.. and yup she works now.. maybe xp was just freaking out at a new network and was used to being on a hub. Im using a crossover cable | MrBeef (342) | ||
| 1 | |||||