Desktop

Ask something
Discussion Locked

PING: transmit failed, error code 65

0 helpful
17 replies

by rmccon

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This Computer is running Windows XP and can access the internet. I can get my email and download stuff off of the internet. When I try to access other computers on my network it tells me that 'Domain is not available. You may not have permission to access resources.'
I have set up a shared folder on the other machine and given myself access to it. Even though, I should be able to see the machine's name in My Network Connections.

When I try to ping my gateway or the other machine, I get the PING: transmit failed, error code 65 error.

Does anyone know what this is all about?

I have already uninstalled and reinstalled the NIC.

Thanks

Rob

17 replies

by timthetoolman

OK, I'm researching as I answer here so bear with me...

Ping error code 65 is... "the error you get is [WSA][E]HOSTUNREACH (fault code 65 on Windows and Unix platforms)"

ref: http://www.tpffaq.com/cgi-bin/faqmanager.cgi?file=bugs&toc=faq#q2So not much help, there.

But.. I've never seen ping actually fail with an error code !

You can surf the net, so your nic is ok.
Can you ping in the other direction?

That would be a good place to start looking...

Let me know how you go...

Cheers,
Tim.

by rmccon

One thing I did not include, I have a router that does NAT. I cannot ping anything without getting that error.

I cannot seem to get to the link that you left. I have taken out all spaces.

Thanks

Rob

by petemcc

You may have an issue with firewall settings. Disable firewall or lower the security settings and see what effect that has. I've seen some references to zonealarm having this issue, also XP built-in firewall capabilities may conflict with LAN settings, if you're using NAT for instance.

by rmccon

Thanks for the info, but I have researched that already. I am not using XP's Firewall, nor do I have Zonealarm. I do have a router thou that does NAT. Do you know of any conflicts with this?

by timthetoolman

Wierd when I tried the link, IE6 put a %20 in the space (that TechRep so nicely inserted) between f and aq...

If you got the same, then remove it. The link is only a reference to where I got the information for the ping error from anyway...

Ahh... so a router. That makes a difference.
And the router does NAT?

I guess the router is your gateway? In that case I'd guess its a configuration on the router thats causing you grief.

Unfortunately I dont know enough about router configuration to give you definite answers but I'd be looking at its configuration with respect to passing protocols (like ping...)

Hmmm... It does NAT... Then do you have a dynamic address or a static one?

Is everything you're trying to reach on the other side of that router? Is there anything on your side of the router? And can you ping that??

Cheers,
Tim.

by rmccon

The router is my gateway, and I can get to things on the otherside, as this is the connection to the internet. There are more computers on my side of the router, but I can't ping them either. I get the same answer, so it has to be something in my machine.

I have a dynamic address, and I can ping from the other computers to site on the other side of the router, so it is not the settings on the router.

Thanks for you ideas, and please keep them coming.

Rob

by ayoshi

The router/NAT is probably configured to filter out ICMP packets (like PING).

As far as connecting, it sounds like you have configured yourself for a Domain, and not for a workgroup (I haven't worked with XP, so....).

I have heard that XP for companies requires a Domain to log in to, and if you cannot see a domain then you can't access shared resources because you can't authenticate yourself.

If you do have a domain controller, then your computer is probably trying to follow the "default gateway" out to the internet where you obviously have no domain.

Solution:
1. Reconfigure your router with an appropriate "internal" network that includes all of your local machines.
2. Reconfigure your router to NOT filter ICMP outbound (you DEFINITELY want inbound filtered).
3. If you have an internal WINS server, make sure all computers are accessing it as their primary WINS (can be called NBNS) server. If you don't have WINS, don't worry.
4. If you have an internal DNS server, configure the clients to access it, and have the DNS server do "forwarding" to the ISP's DNS server. If you don't have a DNS server, don't worry.
5. If you don't have WINS or DNS server, configure each client with an LMHOSTS or HOSTS file that includes all the other machines on your internal network (preferably LMHOSTS).

by rmccon

Sorry,

Lack of Information which is my fault.

1. There is no Domain. This is a home network with no server.
2. The router hands out the IP Addresses. DHCP Configured.
3. XP Home version.

I do not believe that it is the router, as I can access the internet and email through it. I can also ping to sites on the otherside of the router from the other machines connected to it. So I think it has to be on my computer.

Thank you for you suggestions, and if you need more info, please ask.

I would really like to solve this litte *%&$#*$!!!!

Rob

by rmccon

I would like to thank all the people who have answered this question.

Just some updated info that I forgot to put in.

I have a home network, with no server. We access the internet through a linksys router. I have 2 machines connected to the router and both can access the internet, but cannot get access to each computer on this side of the router. Machine A can see Machine B, but Machine B cannot see Machine A.
B is the computer that has been described above.
Through Machine A I can ping anywhere on the other side of the router. When I try to ping with Machine B I get the error code 65.

I would appreciate any and all help.

Thanks

Rob

by timthetoolman

Hi,

I'd be interested to know what IP addresses get assigned to each machine connected to the router.

Are they in different subnets?

Routers are great for splitting networks but I'm not sure how they handle being effectively used as a hub/switch.

There may be a configuration you need to make.

I suspect if you put a hub between the router and your two machines, then your problems would go away...

But that seems excessive. I dont see why the router shouldn't be able to do this.
The fact you get the ping error when you try to ping the router DOES worry me, though.

Are you certain of the IP address (used in the gateway) on the port you've connected to the router?

Surely by default, each port on a router must have a different IP address... otherwise they couldn't route between different subnets.

Maybe this wont help, but maybe it'll help you think of something that will !?!

Cheers,
Tim.

by rmccon

Thanks for your suggestions, but even when I connect my machine directly to the Internet, I cannot ping out. It is something within XP I think. I have switched cables, NIC, NIC Slots, and Ports in the router, nothing works.

Any Idea's would be appreciated.

by timthetoolman

OK. Thanks for the info re: not being able to ping without the router in the way...

The next few suggestions you may have already checked but have a look.

Make sure you dont have the XP firewall enabled. You may not have specifically set it but just have a look anyway. Stranger things have been known to happen...

http://www.microsoft.com/windowsxp/pro/using/howto/networking/icf.asp

(remove spaces from the above URL)

Next check that you're not filtering out any IP packets.

Its... properties of you LAN connection -> Select TCP/IP from the list and choose properties -> Advanced button -> Options tab -> select TCP/IP filtering and choose properties.

Everything there should be permit all.

Next question, and I cant believe I haven't asked this yet... can you ping 127.0.0.1 ?
Thats the loopback test and will tell you if ping is working TO your nic (but not past it)

And the other thing I dont think I got an answer on was whether your other machine can actually pingthe troubled XP one.

If you have a crossover cable, it would be worthwhile trying to network the two machines directly together for testing purposes.

That will remove most of the uncertainties.

Let me know how you get on.
Cheers,
Tim.

by rmccon

Hey Tim,
OK, the firewall is not enabled, there was no TCP/IP filtering enabled on the NIC, I enabled it and tried again, no go. I can ping 127.0.0.1, and when I ping the troubled computer from the good one, I get the request has timed out error.Unfortunatly I do not have a crossover cable, but when I connected the troubled computer directly to the internet, I still could not ping.

Again, any help would be appreciated.

by timthetoolman

Hi,

OK, next thing to have a look at...

I've looked at this on my WinXP Pro machine so I hope its an option on your WinXP Home machine...

On the control panel, under Network and Internet connections... There a box on the left hand side of the screen saying troubleshooters with a link to network diagnostics.

Click that. Then choose "scan your system" It goes off and queries a whole bunch of networky things on your system and comes back with a summary screen.

Do that and see if it all looks OK.

If you think it looks OK and still cant find the problem, then do a save to file - which creates an HTML version of that info and send it to me.

I'll be a second opinion...

Hopefully you'll get something useful from that.

Cheers,
Tim.

ps. My email address is medhurstt@hotmail.com

by rmccon

Tim,

Problem is solved. Thanks for you help. A roomate had installed zonealarm, and then uninstalled it. There seemed to be a error when it unistalled as part of it was still running, so I re-installed and then uninstalled and it works now.Thanks to everyone for there help.

This discussion is closed to new replies.