Can't connect to a pc

[Guest]

Hi,

I am running on a w2k3 domain. I have a 2 PCs (PC1 and PC2), I am logged
onto PC1 with admin account but I am unable to ping or connect to PC2.
However when I log onto PC2 I am able to ping and connect to PC1. I have
tried this with both PCs windows firewalls switched off and both swtiched on
and a combination of these.

I am able to ping the domain controller (which is the dns server) from both
machines and the names are resolved. I have tried ping the ip and that still
times out.

Has anyone experienced this before and\or know a resolution for this?

Any help will be much appreciated.
Thanks,
Jo

 

[Guest]

you know that the firewall is user specific so if you log into the admin
profile and turn it off. It will be turned back on when user x logs onto
it...could this be what is happening.
Are they both xp2p2?
are you talking about the MS firewall or something else?
can you ping the other machine from the dc?

 

[Guest]

I tried it when I was using the same account so the windows firewall (and
Microsoft firewall client) were both switched off.

It's very strange as I can't even ping it from the DC but it has no problem
pinging the DC and connects to all network resources (shared drives printers
etc) without any problems. I don't seam to be able to ping from any machine
on the network.

Is there anyway a workstation and block ping requests?

I'm going to try reinstalling tcp/ip service and see if that has any
resolution but can anyone think of anything else to try?

Many Thanks,
Jo

 

[George]

Hi,

I am running on a w2k3 domain. I have a 2 PCs (PC1 and PC2), I am logged
onto PC1 with admin account but I am unable to ping or connect to PC2.
However when I log onto PC2 I am able to ping and connect to PC1. I have
tried this with both PCs windows firewalls switched off and both swtiched on
and a combination of these.

I am able to ping the domain controller (which is the dns server) from both
machines and the names are resolved. I have tried ping the ip and that still
times out.

Has anyone experienced this before and\or know a resolution for this?

I have similar situation, running 2 xp boxes. In looking deeper into
the bad one, I find other things wrong, with what appeared to be a
'working' PC. Eg ...

- opening the adapter's icon in 'network connections' takes a couple of
minutes.

- When I open the 'advanced' tab in the adapter's 'properties' dialog, I
get a "WMI corrupted" message.

- When I run WMIdiag, it says "WINMGMT failed to start".

- When I select 'manage' for 'my computer' (right-click), I get an
"access denied" message, even though I'm the administrator.

.... etc.

Not to say that your case is the same; but, you might find you have
more systemic problems. I'm reluctantly coming to the conclusion that
the only thing for me is re-install something.

If you do fix it, pls post your results. Esp if reinstalling tcp/ip
fixes it.

Thanks,
George

 

[NtM]

I have similar situation, running 2 xp boxes. In looking deeper into
the bad one, I find other things wrong, with what appeared to be a
'working' PC. Eg ...

- opening the adapter's icon in 'network connections' takes a couple of
minutes.

- When I open the 'advanced' tab in the adapter's 'properties' dialog, I
get a "WMI corrupted" message.

- When I run WMIdiag, it says "WINMGMT failed to start".

- When I select 'manage' for 'my computer' (right-click), I get an
"access denied" message, even though I'm the administrator.

... etc.

Not to say that your case is the same; but, you might find you have
more systemic problems. I'm reluctantly coming to the conclusion that
the only thing for me is re-install something.

If you do fix it, pls post your results. Esp if reinstalling tcp/ip
fixes it.

Thanks,
George

Try going to "set up your home network" and re do that, including the
step where you name the workgroup, I struggled with that the other day
and that fixed it.
Neil

 

[George]

Try going to "set up your home network" and re do that, including the
step where you name the workgroup, I struggled with that the other day
and that fixed it.
Neil

Did it, similar issues - long delays, and finally "an error occured
during configuration of the network on the computer." Re-install (of
something) is looking like the only path forward.

Thanks, though.
G