Mombu the Microsoft Forum sponsored links

Go Back   Mombu the Microsoft Forum > Microsoft > Can ping out, but can't be pinged
User Name
Password
REGISTER NOW! Mark Forums Read

sponsored links


Reply
 
1 19th November 19:07
External User
 
Posts: 1
Default Can ping out, but can't be pinged


I have a computer that can ping out using IP addresses only. I can't use UNC.
Other computers cannot ping this computer either way. I have tried turning
"Use simple file sharing" off. The computer can be seen in Windows Explorer
by other computers, but cannot be accessed. I can't run Remote Desktop
Connection to it either. Any suggestions?

Thanks,

Hal
  Reply With Quote


  sponsored links


2 19th November 19:08
chuck
External User
 
Posts: 1
Default Can ping out, but can't be pinged


Hal,

A slight chance that it could be a physical issue.
<http://nitecruzr.blogspot.com/2005/05/dealing-with-physical-network-problems.html>
http://nitecruzr.blogspot.com/2005/05/dealing-with-physical-network-problems.html
An overlooked or misbehaving personal firewall or other security component is
the best possibility, based on the symptoms.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
LSP / Winsock corruption is another good possibility.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
Node Type is key to name resolution. Check with "ipconfig /all", on all computers.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html
And the NetBT setting, for name resolution.
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
  Reply With Quote
3 26th December 03:09
External User
 
Posts: 1
Default Can ping out, but can't be pinged


Chuck,

Thank you for your reply! Sorry it took me so long to get back to you. I
want to thank you for the information that you supplied to me. By using the
information, I was able to figure the problem out. I ended up needing a
Windows hotfix you had listed and also found out that the Winsock registry
files needed to be replaced. I used your link to Winsock XP Fix to do it very
easily. I also needed to clean out my DHCP on the server and then release and
renew with ipconfig.

The problem came up when I used Norton Ghost to move the contents of a hard
drive to a completely new computer. I realize now that the trouble on the
computer started when I changed the IP address given by DHCP to a static IP
address. I have one more question for you -- if I use Norton Ghost on any
more computer upgrades, will I run into this problem everytime I change the
IP address to a static one, or will setting the IP address on the computer
before joining the network keep that from happening?

By the way, I have bookmarked your blog and will pass it along to anyone
that has a Windows XP networking problem. Great stuff! You've gained a fan.
Thank you for your help!!

Hal
  Reply With Quote
4 26th December 03:09
chuck
External User
 
Posts: 1
Default Can ping out, but can't be pinged


Hi Hal,

Thanks for the feedback. Encouragement is always appreciated here.

I'm not sure what difference a static (as opposed to dynamic) IP address makes
to a computer when Ghost is involved. I wouldn't mind finding out though.

The first possibility that comes to mind is how you assign the IP addresses
manually (statically). Are they assigned from a reliable list, where the list
choices are outside the scope of the DHCP server? AN address conflict is the
greatest possibility for problems, I would suspect.

Next, when you Ghosted to recover the computer, did you use the same computer
name? Using the same name, with a different IP address, could cause a problem.
If any of the other computers have the previous address for that name cached,
you'll have problems of various types.

Let me think about this for a couple days. Don't lose this thread.

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
  Reply With Quote
5 26th December 03:10
External User
 
Posts: 1
Default Can ping out, but can't be pinged


Chuck,

I guarantee that I won't lose this thread! You've been more help to me than
anyone!

To answer your questions, first, I made out and keep the static IP list.
There's very little chance of an address conflict, since I've set up each of
the computers on the domain.

Second, when I ghosted the computer, I ran a Windows XP Pro repair after the
ghosting process so that all the drivers were up to date. I also made sure
that I was at SP2 and that all MS updates had been loaded from Microsoft
Update. The name of the computer was exactly the same as the original
computer.

What I realize now is that in doing so, it wiped out the static IP setting
from the original hard drive and I ended up with the IP address coming from
the DHCP server. When I changed the address to the static IP (and yes, I used
the same IP address that the original computer was using), that is when the
problems surfaced.

Thinking about it, I'm reasonably sure that I will run into the same problem
on any computer that I replace using this Ghosting process. I have two more
to do next week, so I'll be extra careful in setting those up.

Any thoughts you have are appreciated! Thanks

Hal
  Reply With Quote
Reply


Thread Tools
Display Modes




Copyright 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666