Can't connect to another computer within network.

[JCROCCO]

I have one computer on my network that I just cant access through the network. All the other computers also are unable to connect to it. It is on the network as it can access all other computers and internet.

I have shared the drive.
I have allowed others to access and allow changes.
I ran the network setup wizard.
I turned off windows firewall.
The IP and subnet are correct.

I can't ping it.
It doesn't show up as a network connection.
It shows up in workgroup computers, but it wont allow me to access it.

ALSO, it is the only computer that did not update the timeclock for daylight savings time.

Anyone have ANY ideas?

 

[Hardlin]

If you don't have a firewall on it, have you looked at IP filtering (shouldn't be on but could be)? It would be strange for it to announce to the master browser that it's there and be able to ping others but nobody can reach it.

 

[JCROCCO]

How to check for IP filtering? I dont think it would be on either, as I dont know where to go to turn it on specifically.

 

[Muadib]

What version of Windows are you using on it? Can you ping your other computers from the pc in question?

 

[JCROCCO]

WinXP prof, and yes it can ping and access all other computers. No other computers can access it though.

 

[Muadib]

It sounds like you still have a firewall up on that pc. What anti virus are you running? Are you sure you don't have another firewall installed? Is the pc setup in a workgroup, and not a domain? Can you ping the pc from your router?

 

[JCROCCO]

As far as I know there is no other firewall. It is running nortons systemworks 2005, but it does not have any firewall.

I ran net view and it could not connect to the computer either, nor ping. I got this error: System error 53 has occurred

The help said the following:
If the net view command fails with a System error 53 has occurred message, verify that ComputerName is correct, that the computer using Windows XP is operational, and that all of the gateways (routers) between this computer and the computer using Windows XP are operational.

The name is correct, it is up and running, and it can access other computer, NAS, and WAN. I went to the other computer and ran the same command "net view" as above and it worked showing the c drive, printers, etc.

I also did this

Use the net view command and the IP address of the computer using Windows XP, as follows:
net view \\IPAddress

If the net view command succeeds, then ComputerName is being resolved to the wrong IP address.

If the net view command fails with a System error 53 has occurred message, the remote computer might not be running the File and Printer Sharing for Microsoft Networks service.
I checked and it is running file and printer sharing.

Any ideas? this has been an issue for more than a year now. Every month or so I readdress this issue, and cant figure it out.

 

[Muadib]

Can you ping the pc from your router?
Are you sure that the pc is in a workgroup & not a domain?
Did you install Service Pack 2 for XP?

 

[JCROCCO]

Well, I found out I can ping, and connect to it from other machines, just not all of them.

I was testing with the "nbtstat" command and one switich "-S" comes up with no connection when ran on the problem computer, but the other computers all show themselves as connected.

It is in the same workgroup, no domain, and now I find I can connect to it from a few other machines. My machine can connect to all machines other than this problem one. When I try to VPN in and access it, I cant do that either, yet I can do that for all other machines. I do not think it is machine problem specific. Why some machines can connect to it and others cant I dont know.

All computers are on SP2. As for the router, I cant manage it. it is managed by our VOIP service.

Does this help give any clues as to what is going on?

 

[Muadib]

If you can connect to it from other computers, then you need to check the computers that can't. It could also be the router causing the problem. Did you contact the people who control it?

 

[JCROCCO]

I did not.

My computer can access all other computers but that one, so what could be wrong with my computer to make it do that?

What to check for on the computers that can't access it?

 

[Muadib]

If they are all configured the same, then make sure that any firewalls are turned off. Something changed because you said you couldn't ping it before from any pc. The fact that you can ping it from some computers & not others tells me that the problem is not with the pc.

 

[JCROCCO]

As far as I know, all computers are configured the same. I have been having this issue between my computer and this problem computer for some time now. My computer is the only computer that needs to access everyone elses computer. Other would not know if they have a problem connecting to this one computer because they do not need to do it. I have tried in the past multiple times from different computers, and some could connect, and some cant.

Whats weird is the one computer I tested today that can connect the problem computer can also connect to mine. I also can connect to it, just not the problem computer. The problem computer can connect to mine.

I went and tested them all and 3 other computers could not ping the problem computer, but they all could ping mine. Even those that could ping the problem computer could also ping mine.

So there are 4 machines that cant ping this one problem computer. All others can.

All computers can ping all other computers other than the problem computer.

I cant ping it or access it vis VPN for home either.

Makes me think it is something with the problem computer, not each of the computers that cant ping to it.

What in the world could cause this? I am just stumped!

 

[Muadib]

It still could be the router, or you may still be behind a hardware firewall. Since you don't control the router, I'm guessing this is a business?

 

[spidey07]

Really sounds like a software firewall or possible IP/subnet mask misconfiguration.

 

[JCROCCO]

Ok, this may say something, I am just not sure what.

When I was on the problem computer, I was looking at the network connection, I right clicked on it and there was an option to repair. I did that, and then went to my own computer and I was able to now ping it, and it could ping me still. However I rebooted it and now it wont allow me to ping it. I again went to fix the connection and I can ping it again.

Why does fixing the connection allow computers that couldnt ping it to now be able to do so? What could this indicate being the problem?

ANOTHER interesting aspect of this is my remote desktop control still would not connect to the problem computer even though I used its IP address. I could pind the IP address, I could open up my network places and click on its C drive, I could double click on the Computer name in network computers all no problem, but still couldnt access it through remote desktop control using its IP address. That is why I rebooted.

This has got to be a big clue as to what could be going on.

I do appreciate any helpful advice.

 

[Muadib]

When you do a repair, you renew your ip address if you are using dhcp. The arp cache, & DNS cache is flushed, and the netbios name cache is reloaded.

As for remote desktop, are you sure it's turned on in the problem pc?

EDIT: I just saw spidey's post. Did you check the subnet mask on each pc? Are you using dhcp, or does each machine have a static ip?

 

[JCROCCO]

Yes, it is turned on, it is a service. The funny thing is I rebooted the problem computer, then from my computer I opened up RDT and tried to loggin. It worked right after it was booted, then I closed it and tried again, and it failed. After rebooting I cant ping to it either. I am not using DHCP, I am using static. Yes, all SubNetMask are identical. If they were not, would I be able to connect to all of them, even the problem computer once in a while?

Could it be a bad NIC?

Could I remove file and print sharing and then try adding it again?

UUGGGGHHHH!!!

 

[Muadib]

You might have that same ip somewhere else in your network. Unplug the ethernet cable from the bad pc, and then ping the ip address & see if you get a reply.

 

[JCROCCO]

Good idea, but no dice. I unpluged it, and pinged it from a computer that was able to ping it before, and now it didnt. So I would say no to that.

 

[Muadib]

I would have someone look at the router next.

 

[heymrdj]

Just as an off chance, assign the system a new IP and see if it malfunctions in the same way? Or take a computer off the network for a moment and give the ailing computer that IP temporarily. Just to see.

 

[TheSophist]

Uninstall Norton Systemworks. Do you have an Nvidia chipset on your motherboard??