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
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.