name resoulution problem

[Guest]

I just set up two desktops both with xp pro and attempted to network through a lynksys router. Computer X is connected via eithernet wire and comp Y via wireless usb adapter. Internet connection on both machines works fine. Both have same workgroup name (homenet) and different names X and Y. I can ping both back and forth by IP address. I can ping comp X from comp Y by name but not the other way. When I attempt to ping from X to Y by name it times out. I believe this is stopping these two from sharing files and printers. There are no firewalls on either machine enabled. Can someone help??

 

[Jerry]

http://www.practicallynetworked.com/sharing/troubleshoot/ go here for XP
Network troubleshooting.

I just set up two desktops both with xp pro and attempted to network

through a lynksys router. Computer X is connected via eithernet wire and
comp Y via wireless usb adapter. Internet connection on both machines works
fine. Both have same workgroup name (homenet) and different names X and Y.
I can ping both back and forth by IP address. I can ping comp X from comp Y
by name but not the other way. When I attempt to ping from X to Y by name
it times out. I believe this is stopping these two from sharing files and
printers. There are no firewalls on either machine enabled. Can someone
help??

 

[Jetro]

Ensure Y has NetBIOS over TCP/IP enabled. Add Y record to the X lmhosts file
(C:\Windows\system32\drivers\etc\lmhosts).

 

[Steve Winograd [MVP]]

I just set up two desktops both with xp pro and attempted to network through a lynksys router. Computer X is connected via eithernet wire and comp Y via wireless usb adapter. Internet connection on both machines works fine. Both have same workgroup name (homenet) and different names X and Y. I can ping both back and forth by IP address. I can ping comp X from comp Y by name but not the other way. When I attempt to ping from X to Y by name it times out. I believe this is stopping these two from sharing files and printers. There are no firewalls on either machine enabled. Can someone help??

Make sure that NetBIOS over TCP/IP is enabled on both computers.

1. Open the Network Connections folder.
2. Right click the local area network connection and click Properties.
3. Double click Internet Protocol (TCP/IP).
4. Click Advanced.
5. Click WINS.
6. Click the Enable NetBIOS Over TCP/IP button.

Run "ipconfig /all" on both computers and look at the "Node Type" at
the beginning of the output. If it says "Peer-to-Peer" (which should
actually be "Point-to-Point") that's the problem. It means that the
computer only uses a WINS server, which isn't available on a
peer-to-peer network for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Han]

Run "ipconfig /all" on both computers and look at the "Node Type" at
the beginning of the output. If it says "Peer-to-Peer" (which should
actually be "Point-to-Point") that's the problem. It means that the
computer only uses a WINS server, which isn't available on a
peer-to-peer network for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

Thank you, thank you!!
After attending a conference at Colby College, where I had nice internet
access through their network, my laptop couldn't see my home LAN anymore.
It has taken me days to find your post and perform this simple fix -
remove the DhcpNodeType entry and reboot.

My symptoms were that everything worked on my network (several computers
linked by a wired and wireless network via a Linksys WRT54G router to
DSL), except LAN access to and from this one laptop that had just
travelled. Very occasionally after fooling with network entries there
would be a single instance of LAN access after which everything would shut
down again.

I believe this fix is worthy of including in the MS Kbase, as well as in
the Linksys KB.

 

[Steve Winograd [MVP]]

Thank you, thank you!!
After attending a conference at Colby College, where I had nice internet
access through their network, my laptop couldn't see my home LAN anymore.
It has taken me days to find your post and perform this simple fix -
remove the DhcpNodeType entry and reboot.

My symptoms were that everything worked on my network (several computers
linked by a wired and wireless network via a Linksys WRT54G router to
DSL), except LAN access to and from this one laptop that had just
travelled. Very occasionally after fooling with network entries there
would be a single instance of LAN access after which everything would shut
down again.

I believe this fix is worthy of including in the MS Kbase, as well as in
the Linksys KB.

You're welcome! I'll ping the appropriate people at Microsoft to see
if this can be added to the KB.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com