Networking with XP

  • Thread starter Thread starter Sam
  • Start date Start date
S

Sam

I have three machines running XP, one is running XP Home
and the other two are running XP Professional. They all
are connected via a router sharing cable connection and
they all can share Internet connection with DHCP present.
All computers have the same workgroup name MSHOME, and
the subnet mask is 255.255.255.0.

However, the XP Home cannot be viewed in the Workgroup on
both of the other XP machines. The only way the machines
can be accessed is if I click Start, Run and type \\<ip
address>. What could be wrong? The XP Home machine
doesn't seem to show in the workgroup, yet the other
machines show up just fine.
 
"Sam" said:
I have three machines running XP, one is running XP Home
and the other two are running XP Professional. They all
are connected via a router sharing cable connection and
they all can share Internet connection with DHCP present.
All computers have the same workgroup name MSHOME, and
the subnet mask is 255.255.255.0.

However, the XP Home cannot be viewed in the Workgroup on
both of the other XP machines. The only way the machines
can be accessed is if I click Start, Run and type \\<ip
address>. What could be wrong? The XP Home machine
doesn't seem to show in the workgroup, yet the other
machines show up just fine.

1. Make sure that NetBIOS over TCP/IP is enabled on all computers.
Details here:

Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/sharing/troubleshoot/netbt.htm

2. Run "ipconfig /all" 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
 
Steve,

Here's what I got. I'm little confused about this node
type stuff. I'll give you the results and you can
hopefully explain this to me.

Windows XP Home
Node Type: Unknown
NetBios over TCP/IP enabled

Windows XP Pro
Node Type: Hybrid
NetBios over TCP/IP enabled

Windows XP Pro
Node Type: Hybrid
NetBios over TCP/IP enabled

The XP Pro machines do not have any trouble. The XP Pro
machine don't see the XP Home machine and can only access
the Home machine by typing the ip address into the Run
box. Should all of these machines be Point-To-Point for
the node type?

I would appreciate your help. Thanks and have a good
Christmas holiday.



-----Original Message-----
 
"Sam" said:
Steve,

Here's what I got. I'm little confused about this node
type stuff. I'll give you the results and you can
hopefully explain this to me.

Windows XP Home
Node Type: Unknown
NetBios over TCP/IP enabled

Windows XP Pro
Node Type: Hybrid
NetBios over TCP/IP enabled

Windows XP Pro
Node Type: Hybrid
NetBios over TCP/IP enabled

The XP Pro machines do not have any trouble. The XP Pro
machine don't see the XP Home machine and can only access
the Home machine by typing the ip address into the Run
box. Should all of these machines be Point-To-Point for
the node type?

I would appreciate your help. Thanks and have a good
Christmas holiday.

Thanks for checking all those node types, Sam.

None of the machines should be Point-to-Point. Hybrid and Unknown
should both be OK, but not optimal. It might help to set the XP Home
computer's node type to Mixed.

But before doing that, double-check the NetBIOS setting on that
computer, making sure that it's set to "Enable", not to "Default".
While you're on the WINS tab of the TCP/IP properties, remove any WINS
addresses.
--
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
 
Steve,

I did double check that XP Home machine. It's not set to
default and is set to "Enable NetBIOS over TCP/IP", and
there is no WINS addresses. I thought restarting the
machine would help after making the changes, but it
didn't help. I didn't restart the XP Pro machines yet,
but now it looks like I need to change the Node type
to "Mixed." as you pointed out to me.

Can you tell me how to accomplish this task?



-----Original Message-----
 
Never Mind, I set the Node Type to "Mixed" and restarted
the machine and looked at the ipconfig/all results. Can
you think of anything else?

What now Steve? I'm still having problems

________________
Sam

-----Original Message-----
Steve,

I did double check that XP Home machine. It's not set to
default and is set to "Enable NetBIOS over TCP/IP", and
there is no WINS addresses. I thought restarting the
machine would help after making the changes, but it
didn't help. I didn't restart the XP Pro machines yet,
but now it looks like I need to change the Node type
to "Mixed." as you pointed out to me.

Can you tell me how to accomplish this task?
 
I'm still having problems. What should I do now?


Sam


-----Original Message-----
Never Mind, I set the Node Type to "Mixed" and restarted
the machine and looked at the ipconfig/all results. Can
you think of anything else?

What now Steve? I'm still having problems

________________
Sam
 
Steve Winograd, I finally figured this out.

The workgroup name was different. On the XP Home machine,
it was MSHOME (default for XP) but the other XP Pro
machines were changed to WORKGROUP. I changed the XP Home
machine and now all the machines show up in the
WORKGROUP.

The Workgroup names are now the same. I don't understand
this because Windows is supposed to support multiple
workgroup names reguardless of them being different and
should show up.

_______________________
Sam
 
"Sam" said:
Steve Winograd, I finally figured this out.

The workgroup name was different. On the XP Home machine,
it was MSHOME (default for XP) but the other XP Pro
machines were changed to WORKGROUP. I changed the XP Home
machine and now all the machines show up in the
WORKGROUP.

The Workgroup names are now the same. I don't understand
this because Windows is supposed to support multiple
workgroup names reguardless of them being different and
should show up.

Thanks for the report, Sam. I'm glad that you solved it.

Windows does support multiple workgroups, and a computer in any
workgroup can access a computer in any other workgroup.

When you click "View workgroup computers", only computers in your own
workgroup appear. To see all of the workgroups on the network, press
the Backspace key.

"Start | Run | \\Computer" should access a computer, regardless of
what workgroup it's in. The only exception I can think of is when
there's no browse master in that computer's workgroup.
--
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
 
Thank you so much. You are awsome.

I have never found this anywhere on the Internet and I'm
glad you've pointed this out to me. This should be
covered at Practicallynetworked.com. I'm going to have to
save this for future reference.

Sam

-----Original Message-----
 
-----Original Message-----
1. Make sure that NetBIOS over TCP/IP is enabled on all computers.
Details here:

Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/sharing/troubleshoot/ netbt.htm

2. Run "ipconfig /all" 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
.
 
Back
Top