Re: Lost peer computer on network
- From: Chuck <none@xxxxxxxxxxx>
- Date: Mon, 23 Jan 2006 19:06:02 -0800
On Mon, 23 Jan 2006 21:52:50 -0500, "Randy W. Sims"
<RandyS@xxxxxxxxxxxxxxxxxxxx> wrote:
>
>Chuck wrote:
>
>Thanks for the response Chuck. Much useful info on your website. Still
>working through some of it, but here are results from the steps you
>suggested.
>
>
>> On Mon, 23 Jan 2006 01:37:12 -0500, "Randy W. Sims"
>> <RandyS@xxxxxxxxxxxxxxxxxxxx> wrote:
>>
>>> I have a small peer network of computers running Windows 2000 Pro / XP
>>> Home. Used to be static IP, but was changed a while back to use dynamic
>>> IP/DNS except for one (Windows XP Home) notebook that didn't get
>>> changed, but it still worked fine. That notebook is now being used at
>>> two locations on two networks, so it was changed to dynamic IP/DNS. That
>>> is the only change I'm aware of that has been made. Now when connected
>>> to the original network, it doesn't see the Microsoft network. TCP/IP
>>> layer is fine. I can ping other computers and get pinged. I can access
>>> the Internet (DSL modem into router/gateway). But the MS Network cannot
>>> be browsed/accessed. Workgroup name is correct. I don't know of any
>>> other settings to check.
>>>
>>> Grateful for any advice.
>>>
>>> Randy.
>>
>> Randy,
> >
> > When you say "I can ping other computers and get pinged." are you
>referring to
> > from the problem computer?
>
>Sorry. Further testing produces mixed results. I haven't tried all
>computers on the network, but I verified that I can ping the router
>(LinkSys RT31P2) and several computers running Windows 2000. I was not
>able to ping a computer running WinXP Home. This is all from the faulty
>system. From another good system (WinXP Home), I was able to ping the
>faulty one.
>
>> This sounds like a personal firewall problem, though your history description
>> doesn't correlate that. Look at other possibilities too.
>> <http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
>> http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html
>
>1) Error message when trying to access network:
>
>---><8---
>\\MYSERVER\share is not accessible. You might not have permission to use
>this network resource. Contact the administrator of this server to find
>out if you have access permissions.
>
>The network path was not found.
>---><8---
>
>Verified many times correct Workgroup name, user name and password under
>multiple accounts.
>
>2) Temporarily disabled MS Firewall. Norton System works is installed
>with Antivirus (temp disabled). Looks like SVG antivirus also installed.
>No active firewalls.
>
>3) Anonymous access restrictions not enabled.
>
>4) `browstat status` from faulty system (GRAHAM):
>
>Status for domain WORKGROUP on transport \Device\NetBT_Tcpip_{GRAHAM_GID}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>
>
>`ipconfig /all` from faulty system:
>
>Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : GRAHAM
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Peer-Peer
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : bellsouth.net
>
>Ethernet adapter Local Area Connection 4:
>
> Connection-specific DNS Suffix . : bellsouth.net
> Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
>Connection
> Physical Address. . . . . . . . . : hh-hh-hh-hh-hh-hh
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : X.X.X.100
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : X.X.X.254
> DHCP Server . . . . . . . . . . . : X.X.X.254
> DNS Servers . . . . . . . . . . . : 205.152.37.23
> 205.152.144.23
> Lease Obtained. . . . . . . . . . : Monday, January 23, 2006
>19:23:38
> Lease Expires . . . . . . . . . . : Tuesday, January 24, 2006
>19:23:38
<SNIP>
Here's a big one, Randy. Do you have a WINS server?
>Windows IP Configuration
> Host Name . . . . . . . . . . . . : GRAHAM
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Peer-Peer
If you don't have a WINS server, "Peer-Peer" won't work.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Peer-Peer>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Peer-Peer
After you fix that, you'll need to rerun everything previously run on GRAHAM.
--
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.
.
- References:
- Lost peer computer on network
- From: Randy W. Sims
- Re: Lost peer computer on network
- From: Chuck
- Re: Lost peer computer on network
- From: Randy W. Sims
- Lost peer computer on network
- Prev by Date: Re: Lost peer computer on network
- Next by Date: XP home network issue
- Previous by thread: Re: Lost peer computer on network
- Next by thread: Re: Lost peer computer on network
- Index(es):
Relevant Pages
|
