Re: New pc not recognized on network
- From: Stan <stan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 4 Oct 2006 12:53:02 -0700
browstat output on prosys1
Status for domain STANLEY on transport
\Device\NetBT_Tcpip_{B40399D1-1DA2-4B7B-9
26D-6B1B492DFFD4}
Browsing is NOT active on domain.
Master browser name is held by: GIGI
Could not connect to registry, error = 53 Unable to determine build
of br
owser master: 53
\\GIGI . Version:05.01 Flags: 51203 NT POTENTIAL MASTER
C:\Documents and Settings\client>
--
Stan
"Chuck" wrote:
On Wed, 4 Oct 2006 08:30:02 -0700, Stan <stan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:.
I have three Pcs connected together via a Dlink 704p router.
Pc1 computer name gigi, winxp not sp2
Pc2 computer name vieuxpc win 98 (not se)
Pc3 computer name PROSYS1 WinXP Sp2
When I installed the new pc I ran the network wizard and connected it to the
network ans was able to see the others in network neiborhood. I still have
the names of the shared folders in network favorites.
I then proceeded to copy some files to my new hard disk, install various
software and created userids on the new pc.
I have tried disabling network firewall, to no avail.
When I ping pc3 from pc1 I see the network connectionicon blink four times.
The first time, both screens light up, the other three, only the right hand
icon blinks.
Any help on the matter will be greatly appreciated.
I then transferred my printer to pc3 and tried to share it with the others.
At that time I discoverd that I could not explore pc3 from either PC1 or Pc2
via the network neigborhood although Pc3 appears in the list of pcs in the
network
I can't ping the ip address which is generated by my router from either pc1
or pc2 or the router itself.
Pc3 can ping the other two pcs, the router and itself.
The network connection on pc3 has the correct ip address subnet id etc...
My two other Pcs have zone alarm installled but not activated. I had
installed zone alarm on pc3 but have uninstalled it
I have run pchuck's cdiag and from pc1 and pc3 and the results indicate that
from pc1 the pc3 name is resolved to the correct ip address but the ping
request times out.
I had not tried to ping pc3 from the other two until I noticed the problem
in trying to share the printer.
Stan,
If you can actually resolve PC3 by name, then it sounds like you had
connectivity at one time. What happens if you clear the name resolution cache
("nbtstat -R"), then try pinging by name?
The ping command is pretty low level. Did it not work before you tried un
installing ZA? Un installing may not be an easy task. Look for an unrecognised
personal firewall, and look for LSP / Winsock corruption too.
<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
<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
--
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.
- Follow-Ups:
- Re: New pc not recognized on network
- From: Stan
- Re: New pc not recognized on network
- References:
- Re: New pc not recognized on network
- From: Chuck
- Re: New pc not recognized on network
- Prev by Date: Cannot see computer...
- Next by Date: Re: No files showing
- Previous by thread: Re: New pc not recognized on network
- Next by thread: Re: New pc not recognized on network
- Index(es):
Relevant Pages
|
