Unsolved
This post is more than 5 years old
5 Posts
0
37877
March 17th, 2005 08:00
Ping: Transmit Failed. Error code 1
Dimension 3000
Win XP
Setting up a static IP address, to copy across data from old to new computer.
When I try to Ping the ip address assigned or 127.0.0.1 I get the error "Ping: Transmit Failed. Error code 1".
I've tried disabling the firewall, to no effect.
Any suggestions as to the possible cause?
TIA
Eric
No Events found!
volcano11
2 Intern
•
28K Posts
0
March 17th, 2005 12:00
How are you connecting these computers togother (through a hub, switch, router, or directly using a cross-over cable)? If directly, are you sure you're using a cross-over cable, as a regular network cable will not work? Which version(s) of Windows is/are running on the computers? Does each network card have a unique static IP address? Does Device Manager show the network cards to be installed properly and working?
Steve
_Paladin
795 Posts
0
March 17th, 2005 12:00
EricArm,
The error you are receiving indicates the ping is being blocked by a firewall. You may be running multiple firewalls. The Windows XP firewall either needs to be disabled (SP1) or configured to allow File and Printer Sharing (SP2). Look for other firewalls, like Norton Internet Security, McAfee Security Suite, etc. They can be configured to allow a range of IP addresses. This is called the Trusted Zone. Norton Anti-Virus 2005 also has a worm blocker, which acts like a firewall.
EricArm
5 Posts
0
March 17th, 2005 12:00
Paladin,
Cheers for that, I've removed the XP firewall but will check that both are off and let you know how it goes,
Thanks Again
Eric
EricArm
5 Posts
0
March 17th, 2005 14:00
Steve,
I'm happy with the kit external to the computer, but am new to XP. Paladin has suggested a possible reason for the error, I'll try it out when I get home and let you know how I get on,
Thanks,
Eric
EricArm
5 Posts
0
March 20th, 2005 18:00
Spent a few hours disabling firewalls but still no joy, Surely firewalls wouldn't block 'ping' for your own IP address or 127.0.0.1.
Any other suggestions please,
Eric
_Paladin
795 Posts
0
March 20th, 2005 19:00
EricArm,
Please answer the questions volcano11 asked, especially the condition of the NIC as it appears in Device Manager.
EricArm
5 Posts
0
March 21st, 2005 12:00
So I felt that any description beyond the computer was superfluous.
I take your point that I should have mentioned the condition of the NIC in the Device Manager, which is detected and flagged as having no problems.
I did give the model (Dimension 3000) and OS (XP) of the system in my original query.
For info I am running the network using a NetGear hub(RJ45) connecting to a rather old P2 120 (don't laugh) running Win95(still laughing?). This 'Pings' fine to itself, but 'times out' when pinging the XP machine. I did finally get both machines to see each other on the Microft Windows Network and copy the files I needed across, but still couldn't get the XP machine to 'Ping' itself. So the NIC works and the IP is correctly reported using 'ipconfig', but still no reply to 'Ping'
_Paladin
795 Posts
0
March 21st, 2005 12:00
EricArm,
Can you identify the model of the Netgear hub? Are the static IP addresses you used in the same subnet? They should be something like 192.168.0.1 and 192.168.0.2 and both should have a subnet mask of 255.255.255.0.
Symptoms are leaning toward a TCP/IP problem on the D3000. See this MSKB article for a procedure to reset the TCP/IP stack. If that does not help, download and run winsockfix and if necessary lspfix. If still not resolved, uninstall the NIC through Device Manager, reboot and let it reinstall the "new" hardware.
Since you transferred data between the two PCs, I assume you used a protocol other than TCP/IP. If you want to use TCP/IP, make sure File and Printer Sharing is only bound to TCP/IP and no other protocol.
Is SP2 installed on the D3000?