The tale of three computers

[Bogdan Giusca]

There are three computers in a network:

#1: Windows XP Professional SP2
#2: Windows XP Home, no updates
#3: Windows XP Professional, no updates

I can access #1 from #2 and from #3 only by using the IP address, not
by the computer name, even the proxy server I have on #1 works.

All other combinations (such as #2 from #3 and #2 from #1) don't work.

I'd install SP2 on the other two computers, but I heard from someone
that in the first place the problem could be the 'security upgrades' in
SP1+ and it might stop working altogether.

Any ideas what should I do ?

 

[Steve Winograd [MVP]]

There are three computers in a network:

#1: Windows XP Professional SP2
#2: Windows XP Home, no updates
#3: Windows XP Professional, no updates

I can access #1 from #2 and from #3 only by using the IP address, not
by the computer name, even the proxy server I have on #1 works.

All other combinations (such as #2 from #3 and #2 from #1) don't work.

I'd install SP2 on the other two computers, but I heard from someone
that in the first place the problem could be the 'security upgrades' in
SP1+ and it might stop working altogether.

Any ideas what should I do ?

With so many known security problems in the original release of
Windows XP, it's risky to connect to the Internet on an un-updated
system. I'd update computer #2 and #3 to SP2 right away. The
'security upgrades' in SP2 are important, and they don't interfere
with networking. If the Windows Firewall is enabled, configure it to
allow file and printer sharing on the LAN.

If another firewall program (Norton, PC-cillin, ZoneAlarm, Sygate,
eTrust, McAfee, etc) is installed, configure it to allow file and
printer sharing on the LAN.

Since accessing #1 by IP address works and accessing it by computer
name doesn't, the problem probably involves NetBIOS. On all three
computers:

1. Make sure that NetBIOS over TCP/IP is enabled:

a. Open the Network Connections folder.
b. Right click the LAN connection and click Properties.
c. Double click Internet Protocol (TCP/IP).
d. Click Advanced.
e. Click WINS.
f. Click the Enable NetBIOS Over TCP/IP button.

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

 

[Carey Holzman]

www.caryeholzman.com/net1.htm

Carey

 

[Bogdan Giusca]

If another firewall program (Norton, PC-cillin, ZoneAlarm, Sygate,
eTrust, McAfee, etc) is installed, configure it to allow file and
printer sharing on the LAN.

I have ZoneAlarm installed and configured the local network as "safe
zone.

Since accessing #1 by IP address works and accessing it by computer
name doesn't, the problem probably involves NetBIOS. On all three
computers:

1. Make sure that NetBIOS over TCP/IP is enabled:

a. Open the Network Connections folder.
b. Right click the LAN connection and click Properties.
c. Double click Internet Protocol (TCP/IP).
d. Click Advanced.
e. Click WINS.
f. Click the Enable NetBIOS Over TCP/IP button.

NetBIOS was disabled, I enabled on #1 and #2, restarted them, with no
change.

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.

#1 "unknown"
#2 "hybrid"

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

They're not present.

 

[Hans-Georg Michna]

There are three computers in a network:

#1: Windows XP Professional SP2
#2: Windows XP Home, no updates
#3: Windows XP Professional, no updates

I can access #1 from #2 and from #3 only by using the IP address, not
by the computer name, even the proxy server I have on #1 works.

All other combinations (such as #2 from #3 and #2 from #1) don't work.

I'd install SP2 on the other two computers, but I heard from someone
that in the first place the problem could be the 'security upgrades' in
SP1+ and it might stop working altogether.

Any ideas what should I do ?

Bogdan,

please use http://www.michna.com/kb/wxnet.htm to solve this
problem.

Hans-Georg

 

[Steve Winograd [MVP]]

I have ZoneAlarm installed and configured the local network as "safe
zone.


NetBIOS was disabled, I enabled on #1 and #2, restarted them, with no
change.


#1 "unknown"
#2 "hybrid"


They're not present.

What about computer #3? If you haven't done it already, enable
NetBIOS and check the node type on it, too.

The only node type that causes a problem is "Peer-to-Peer". "Unknown"
and "Hybrid" are OK.

It can take some time after enabling NetBIOS or rebooting a computer
before browsing through My Network Places works. To access another
computer directly, type its name in the Start | Run box in this form:

\\computer
--
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

 

[Bogdan Giusca]

beginning of >> the output. If it says "Peer-to-Peer" (which should
actually be >> "Point-to-Point") that's the problem.

What about computer #3? If you haven't done it already, enable
NetBIOS and check the node type on it, too.

#3 was off. However I'll check it.

The only node type that causes a problem is "Peer-to-Peer". "Unknown"
and "Hybrid" are OK.

It can take some time after enabling NetBIOS or rebooting a computer
before browsing through My Network Places works. To access another
computer directly, type its name in the Start | Run box in this form:

\\computer

It doesn't work. Actually, before, it worked from #1 to access the
shared stuff from itself.

Now it doesn't. In fact, everything I want to "Unable to browse the
network -- The network is not present or not started" and at "network
connections" it shows none.

The even more strange thing is that although there is no connection
shown, I can access the internet...

 

[Bogdan Giusca]

Bogdan,

please use http://www.michna.com/kb/wxnet.htm to solve this
problem.

I got this: (among other):
<<
DNS Client service running in a workgroup

In a workgroup (not domain), if networking works perfectly as long as
you use IP addresses, but fails when you use host names, the cause may
be that the DNS Client service is running. Stop and disable it
permanently. It is only needed in Windows Server domains, not in
workgroups, and it tends to get in the way.
I did that and the network wouldn't work at all (not even what it did
until now).

 

[Hans-Georg Michna]

Hans-Georg Michna wrote:

I got this: (among other):
<<
DNS Client service running in a workgroup

In a workgroup (not domain), if networking works perfectly as long as
you use IP addresses, but fails when you use host names, the cause may
be that the DNS Client service is running. Stop and disable it
permanently. It is only needed in Windows Server domains, not in
workgroups, and it tends to get in the way.

I did that and the network wouldn't work at all (not even what it did
until now).

Bogdan,

sorry for that. I hope it works again after you reenabled the
DNS Client service. The advice is no longer valid. I have
retested this and find that the DNS Client does not cause any
problems, at least not on computers with Service Pack 2. I will
remove this wrong advice from the web page within 24 hours.

Thank you very much for this report! It has helped to improve
the web page.

But don't give up too early. After using all information given
in http://www.michna.com/kb/wxnet.htm after filling in the form,
your network will probably function fine.

Hans-Georg