setting permissions perhaps?

[Guest]

I have 2 desktops and a laptop. desktops see and share flies fine, they both
see the laptop in on the microsoft network but it is inaccesible, that is
"\\Laptop is not accesible. You might..." The laptops ip address isn't
pingable from the desktops either. The laptop can see and access both
desktops. They're all xp pro sp2, the fire wall is disabled. I guess it is a
permission problem but I don't know how to resolve it. I've never run across
this before.

 

[Chuck]

I have 2 desktops and a laptop. desktops see and share flies fine, they both
see the laptop in on the microsoft network but it is inaccesible, that is
"\\Laptop is not accesible. You might..." The laptops ip address isn't
pingable from the desktops either. The laptop can see and access both
desktops. They're all xp pro sp2, the fire wall is disabled. I guess it is a
permission problem but I don't know how to resolve it. I've never run across
this before.

Please provide ipconfig information for each computer, to start.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, make sure that Format - Word Wrap is
NOT checked!, copy and paste entire contents into your next post.

Are you running both Client for Microsoft Networks, and File and Printer Sharing
for Microsoft Networks (Local Area Connection - Properties), on each computer?
Do you have shares setup on each?

Are you running NetBIOS Over TCP/IP (Local Area Connection - Properties - TCP/IP
- Properties - Advanced - WINS) on each computer?

Make sure the browser service is running on the two desktop computers. Control
Panel - Administrative Tools - Services. Verify that the Computer Browser, and
the TCP/IP NetBIOS Helper, services both show with Status = Started. Disable
the browser on the laptop.

On each XP Pro computer, check to see if Simple File Sharing (Control Panel -
Folder Options - View - Advanced settings) is enabled or disabled. With XP Pro,
you need to have SFS consistently set on each computer.

On XP Pro with SFS disabled, check the Local Security Policies (Control Panel -
Administrative Tools). Under Local Policies - Security Options, look at
"Network access: Sharing and security model", and ensure it's set to "Classic -
local users authenticate as themselves".

On XP Pro with SFS disabled, if you set the above Local Security Policy to
"Guest only", enable the Guest account, using Start - Run - "cmd" - type "net
user guest /active:yes" in the command window. If "Classic", setup and use a
common non-Guest account on all computers. Whichever account is used, give it
an identical, non-blank password on all computers.

On XP Pro with Simple File Sharing enabled, make sure that the Guest account is
enabled, on each computer. Enable Guest with Start - Run - "cmd", then type
"net user guest /active:yes" in the command window.

On XP Pro, if you're going to use Guest authentication, check your Local
Security Policy (Control Panel - Administrative Tools) - User Rights Assignment,
on the XP Pro computer, and look at "Deny access to this computer from the
network". Make sure Guest is not in the list.

 

[Guest]

Thanks for the help

Desktop#1:
Windows IP Configuration

Host Name . . . . . . . . . . . . : amd
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : xxx.xx.xx.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI For
Complete PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-04-75-9C-00-6A
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Primary WINS Server . . . . . . . : 10.14.204.79
Secondary WINS Server . . . . . . : 10.14.204.82
Lease Obtained. . . . . . . . . . : Saturday, November 27, 2004
9:51:46 AM
Lease Expires . . . . . . . . . . : Sunday, November 28, 2004
12:01:32 AM

Laptop:
Windows IP Configuration

Host Name . . . . . . . . . . . . : Laptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controller
Physical Address. . . . . . . . . : 00-0F-1F-29-2F-A2

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR 108 Mbps Wireless PC
Card WG511T
Physical Address. . . . . . . . . : 00-09-5B-C5-EC-8E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Saturday, November 27, 2004
3:09:41 PM
Lease Expires . . . . . . . . . . : Sunday, November 28, 2004
3:09:41 PM

:

Are you running both Client for Microsoft Networks, and File and Printer Sharing
for Microsoft Networks (Local Area Connection - Properties), on each computer?
Do you have shares setup on each?
Yes

Are you running NetBIOS Over TCP/IP (Local Area Connection - Properties - TCP/IP
- Properties - Advanced - WINS) on each computer?

NetBios is set to default on all systems

Make sure the browser service is running on the two desktop computers. Control
Panel - Administrative Tools - Services. Verify that the Computer Browser, and
the TCP/IP NetBIOS Helper, services both show with Status = Started. Disable
the browser on the laptop.
Yes

On each XP Pro computer, check to see if Simple File Sharing (Control Panel -
Folder Options - View - Advanced settings) is enabled or disabled. With XP Pro,
you need to have SFS consistently set on each computer.

On XP Pro with SFS disabled, check the Local Security Policies (Control Panel -
Administrative Tools). Under Local Policies - Security Options, look at
"Network access: Sharing and security model", and ensure it's set to "Classic -
local users authenticate as themselves".

Yes for both above

 

[Chuck]

Thanks for the help

<SNIP>

YW. Now to the diagnostic procedures.

Take the following code (everything inside the "#####"). (Did I get the names
and ip addresses right)? (This would be hella more effective if you could add
the third computer to the diagnosis.

Copy the code, precisely as it is keyed, into Notepad. Ensure that Format -
Word Wrap is not checked.
Save the file as "cdiag.cmd", as type "All Files", into the root folder "C:\".
Run it by Start - Run - "c:\cdiag".
Wait patiently.
When Notepad opens up displaying c:\cdiag.txt, first check Format and ensure
that Word Wrap is NOT checked! Then, copy the entire contents (Ctrl-A Ctrl-C)
and paste (Ctrl-V) into your next post.

Do this from all computers, please.

#####

@echo off
set FullTargets=amd 192.168.0.2 Laptop 192.168.0.3
set PingTargets=127.0.0.1 192.168.0.1
Set Version=V1.05
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% (Targets %FullTargets%) >>c:\cdiag.txt
for %%a in (%FullTargets% %PingTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "net view %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view %%a >>c:\cdiag.txt
)
@echo End diagnosis for %computername% >>c:\cdiag.txt
notepad c:\cdiag.txt
:EOF

#####

 

[Guest]

here you go and I have to say thanks again. Unfortunately my 3rd box is
capturing video so it's out of the loop at the moment.

Laptop:
CDiagnosis V1.05
Start diagnosis for LAPTOP (Targets amd 192.168.0.2 Laptop 192.168.0.3)

Target amd

"ping amd"

Ping request could not find host amd. Please check the name and try again.


"net view amd"

Shared resources at amd



Share name Type Used as Comment

-------------------------------------------------------------------------------
250gig (F) Disk
C Disk G:
D Disk
Plextor Disk
The command completed successfully.


Target 192.168.0.2

"ping 192.168.0.2"



Pinging 192.168.0.2 with 32 bytes of data:



Reply from 192.168.0.2: bytes=32 time=1ms TTL=128
Reply from 192.168.0.2: bytes=32 time=2ms TTL=128
Reply from 192.168.0.2: bytes=32 time=1ms TTL=128
Reply from 192.168.0.2: bytes=32 time=1ms TTL=128



Ping statistics for 192.168.0.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 2ms, Average = 1ms


"net view 192.168.0.2"

Shared resources at 192.168.0.2



Share name Type Used as Comment

-------------------------------------------------------------------------------
250gig (F) Disk
C Disk
D Disk
Plextor Disk
The command completed successfully.


Target Laptop

"ping Laptop"



Pinging Laptop [192.168.0.3] with 32 bytes of data:



Reply from 192.168.0.3: bytes=32 time<1ms TTL=128
Reply from 192.168.0.3: bytes=32 time<1ms TTL=128
Reply from 192.168.0.3: bytes=32 time<1ms TTL=128
Reply from 192.168.0.3: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view Laptop"

Shared resources at Laptop

Laptop

Share name Type Used as Comment

-------------------------------------------------------------------------------
C-Laptop Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.0.3

"ping 192.168.0.3"



Pinging 192.168.0.3 with 32 bytes of data:



Reply from 192.168.0.3: bytes=32 time<1ms TTL=128
Reply from 192.168.0.3: bytes=32 time<1ms TTL=128
Reply from 192.168.0.3: bytes=32 time<1ms TTL=128
Reply from 192.168.0.3: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 192.168.0.3"

Shared resources at 192.168.0.3

Laptop

Share name Type Used as Comment

-------------------------------------------------------------------------------
C-Laptop Disk
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 127.0.0.1"

Shared resources at 127.0.0.1

Laptop

Share name Type Used as Comment

-------------------------------------------------------------------------------
C-Laptop Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.0.1

"ping 192.168.0.1"



Pinging 192.168.0.1 with 32 bytes of data:



Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64



Ping statistics for 192.168.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 2ms, Average = 1ms


"net view 192.168.0.1"

End diagnosis for LAPTOP

amd:
CDiagnosis V1.05
Start diagnosis for AMD (Targets amd 192.168.0.2 Laptop 192.168.0.3)

Target amd

"ping amd"



Pinging amd [192.168.0.2] with 32 bytes of data:



Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view amd"

Shared resources at amd



Share name Type Used as Comment

-------------------------------------------------------------------------------
250gig (F) Disk
C Disk
D Disk
Plextor Disk
The command completed successfully.


Target 192.168.0.2

"ping 192.168.0.2"



Pinging 192.168.0.2 with 32 bytes of data:



Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 192.168.0.2"

Shared resources at 192.168.0.2



Share name Type Used as Comment

-------------------------------------------------------------------------------
250gig (F) Disk
C Disk
D Disk
Plextor Disk
The command completed successfully.


Target Laptop

"ping Laptop"



Pinging Laptop [192.168.0.3] with 32 bytes of data:



Request timed out.
Request timed out.
Request timed out.
Request timed out.



Ping statistics for 192.168.0.3:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"net view Laptop"


Target 192.168.0.3

"ping 192.168.0.3"



Pinging 192.168.0.3 with 32 bytes of data:



Request timed out.
Request timed out.
Request timed out.
Request timed out.



Ping statistics for 192.168.0.3:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"net view 192.168.0.3"


Target 127.0.0.1

"ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 127.0.0.1"

Shared resources at 127.0.0.1



Share name Type Used as Comment

-------------------------------------------------------------------------------
250gig (F) Disk
C Disk
D Disk
Plextor Disk
The command completed successfully.


Target 192.168.0.1

"ping 192.168.0.1"



Pinging 192.168.0.1 with 32 bytes of data:



Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64



Ping statistics for 192.168.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 1ms, Average = 1ms


"net view 192.168.0.1"

End diagnosis for AMD

 

[Chuck]

here you go and I have to say thanks again. Unfortunately my 3rd box is
capturing video so it's out of the loop at the moment.

<SNIP>

OK, you have 2 notable symptoms.
1) Laptop can't resolve AMD to IP address. Ping returns "Ping request could
not find host amd.".
2) AMD can't ping Laptop. Ping returns "Pinging Laptop [192.168.0.3] with 32
bytes of data: Request timed out.".

Please start by looking on Laptop for a firewall problem. What firewall is
disabled?

 

[Guest]

Yeah my fire wall is disabled, that's why this is so confusing. That's where
I thought the problem was originaly but the firewall is disabled on all
systems

here you go and I have to say thanks again. Unfortunately my 3rd box is
capturing video so it's out of the loop at the moment.

<SNIP>

OK, you have 2 notable symptoms.
1) Laptop can't resolve AMD to IP address. Ping returns "Ping request could
not find host amd.".
2) AMD can't ping Laptop. Ping returns "Pinging Laptop [192.168.0.3] with 32
bytes of data: Request timed out.".

Please start by looking on Laptop for a firewall problem. What firewall is
disabled?

 

[Chuck]

Yeah my fire wall is disabled, that's why this is so confusing. That's where
I thought the problem was originaly but the firewall is disabled on all
systems

Which firewall is disabled? Many third party firewalls don't disable properly,
and cause problems even after that's done.

If you're referring to WF, how did you disable it?

 

[Guest]

Yes I'm referring to WF. I disabled it by network
places>advanced>WF>settings>off
I also have Mcafee Security center installed but not the firewall component.
What's so confusing about this is the laptop shows up in network places but
is inaccessible and unpingable?!?!

 

[Chuck]

Yes I'm referring to WF. I disabled it by network
places>advanced>WF>settings>off
I also have Mcafee Security center installed but not the firewall component.
What's so confusing about this is the laptop shows up in network places but
is inaccessible and unpingable?!?!

If you want to solve your problem, IMHO you need to consider two possibilities:

1) A rogue firewall. Third party products like McAfee Security Center contain
components that can interfere with file sharing, even when the firewall is
"disabled" or "not installed".

2) A browser (no I'm not talking about Internet Explorer) problem. You have
three computers, and you have to work on all three. Enable the browser on both
desktop computers, and disable it on the laptop. Then power all three off.
Power on the one desktop computer that stays online the most, so it becomes the
master browser. Then power on the second desktop computer, and finally the
laptop.

The Microsoft Browstat program will show us what browsers you have in your
domain / workgroup, at any time.
http://support.microsoft.com/?id=188305

You can download Browstat from either:
<http://www.dynawell.com/reskit/microsoft/win2000/browstat.zip>
<http://rescomp.stanford.edu/staff/manual/rcc/tools/browstat.zip>

Browstat is very small (40K), and needs no install. Just unzip the downloaded
file, copy browstat.exe to any folder in the Path, and run it from a command
window, by "browstat status". Make sure all computers give the same result.

For more information about the browser subsystem (very intricate), see:
http://support.microsoft.com/?id=188001
http://support.microsoft.com/?id=188305
<http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx>

Please provide browstat information for all 3 computers.
Start - Run - "cmd". Type "browstat status >c:\browstat.txt" into the command
window - Open c:\browstat.txt in Notepad, make sure that Format - Word Wrap is
NOT checked!, copy and paste into your next post.

 

[Guest]

I uninstalled mcafee internet security to remove that variable. This is what
browstat gave me, and it's not identical!?!

desktop1:
Status for domain 3DS on transport
\Device\NetBT_Tcpip_{2A4323F6-3D4F-45BC-837D-ED5BC323608C}
Browsing is active on domain.
Master browser name is: AMD
Master browser is running build 2600
1 backup servers retrieved from master AMD
\\AMD
There are 3 servers in domain 3DS on transport
\Device\NetBT_Tcpip_{2A4323F6-3D4F-45BC-837D-ED5BC323608C}
There are 1 domains in domain 3DS on transport
\Device\NetBT_Tcpip_{2A4323F6-3D4F-45BC-837D-ED5BC323608C}

desktop:2
Status for domain 3DS on transport
\Device\NetBT_Tcpip_{A980A968-C696-443D-8931-3C061C15EA41}
Browsing is active on domain.
Master browser name is: AMD
Master browser is running build 2600
1 backup servers retrieved from master AMD
\\AMD
There are 3 servers in domain 3DS on transport
\Device\NetBT_Tcpip_{A980A968-C696-443D-8931-3C061C15EA41}
There are 1 domains in domain 3DS on transport
\Device\NetBT_Tcpip_{A980A968-C696-443D-8931-3C061C15EA41}

Laptop:
Status for domain 3DS on transport
\Device\NetBT_Tcpip_{85A13487-0361-49CE-8158-2B4120C46D97}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

 

[Guest]

Wow, I guess I've stumped the forum. Or I'm just missing something very
basic...

 

[Chuck]

Wow, I guess I've stumped the forum. Or I'm just missing something very
basic...

You have two observed problems.
1) Laptop can't resolve AMD to IP address. Ping returns "Ping request could
not find host amd.".
2) AMD can't ping Laptop. Ping returns "Pinging Laptop [192.168.0.3] with 32
bytes of data: Request timed out.".

IPConfig for AMD:

Windows IP Configuration

Host Name . . . . . . . . . . . . : amd
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : xxx.xx.xx.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI For
Complete PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-04-75-9C-00-6A
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Primary WINS Server . . . . . . . : 10.14.204.79
Secondary WINS Server . . . . . . : 10.14.204.82

What are 10.14.204.79 and 10.14.204.82? Either remove those servers from AMD
WINS configuration, or change Node Type for both computers to Broadcast (or
Unknown).

Here are Microsoft article discussing node types:
<http://support.microsoft.com/?id=314053>
<http://support.microsoft.com/?id=160177>

To correct this, you'll need to run the Registry Editor on both computers.

You need to find this key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]
and delete these two values (which ever is there):
NodeType
DhcpNodeType

After you delete the two values, reboot the computer. After the reboot, rerun
IPConfig and post the results.

The Registry Editor is a scary tool, but it's pretty simple once you get used to
it. Here are a couple articles that might help:
<http://www.microsoft.com/windowsxp/...home/using/productdoc/en/tools_regeditors.asp>
<http://www.annoyances.org/exec/show/registry>

Just remember to backup the key (create a registry patch) for:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]
before deleting the values.

From the Annoyances article:
You can create a Registry patch by opening the Registry Editor, selecting a
branch, and choosing Export from the File menu. Then, specify a filename, and
press OK. You can then view the Registry patch file by opening it in Notepad
(right-click on it and select Edit). Again, just double-click on a Registry
patch file (or use Import in the Registry Editor's File menu) to apply it to the
registry.

 

[Guest]

Well I'm back and I tried option A. That is to remove the servers form the
WINS configuration and there's still no connection. Shuold I still go ahead
and change the registry?

Wow, I guess I've stumped the forum. Or I'm just missing something very
basic...

You have two observed problems.
1) Laptop can't resolve AMD to IP address. Ping returns "Ping request could
not find host amd.".
2) AMD can't ping Laptop. Ping returns "Pinging Laptop [192.168.0.3] with 32
bytes of data: Request timed out.".

IPConfig for AMD:

Windows IP Configuration

Host Name . . . . . . . . . . . . : amd
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : xxx.xx.xx.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI For
Complete PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-04-75-9C-00-6A
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Primary WINS Server . . . . . . . : 10.14.204.79
Secondary WINS Server . . . . . . : 10.14.204.82

What are 10.14.204.79 and 10.14.204.82? Either remove those servers from AMD
WINS configuration, or change Node Type for both computers to Broadcast (or
Unknown).

Here are Microsoft article discussing node types:
<http://support.microsoft.com/?id=314053>
<http://support.microsoft.com/?id=160177>

To correct this, you'll need to run the Registry Editor on both computers.

You need to find this key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]
and delete these two values (which ever is there):
NodeType
DhcpNodeType

After you delete the two values, reboot the computer. After the reboot, rerun
IPConfig and post the results.

The Registry Editor is a scary tool, but it's pretty simple once you get used to
it. Here are a couple articles that might help:
<http://www.microsoft.com/windowsxp/...home/using/productdoc/en/tools_regeditors.asp>
<http://www.annoyances.org/exec/show/registry>

Just remember to backup the key (create a registry patch) for:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]
before deleting the values.

From the Annoyances article:
You can create a Registry patch by opening the Registry Editor, selecting a
branch, and choosing Export from the File menu. Then, specify a filename, and
press OK. You can then view the Registry patch file by opening it in Notepad
(right-click on it and select Edit). Again, just double-click on a Registry
patch file (or use Import in the Registry Editor's File menu) to apply it to the
registry.