XP connecting to Windows 98

J

Jim Matthews

On our small office (5 PC's) one of the users upgraded his W98 laptop to XP
Home.

Now he can no longer connect via a network share to another desktop which is
running W98.

Netbios over TCP/IP is enabled on both.

They can ping each other and they show up in the "Network Neighborhood" and
"My Network Places"

File and Print Sharing is enabled on both.

The new XP Home laptop can access the Internet - it just can't see the
shares on the other machine.

Any ideas ?

TIA

JM
 
S

Steve Winograd [MVP]

"Jim Matthews" said:
On our small office (5 PC's) one of the users upgraded his W98 laptop to XP
Home.

Now he can no longer connect via a network share to another desktop which is
running W98.

Netbios over TCP/IP is enabled on both.

They can ping each other and they show up in the "Network Neighborhood" and
"My Network Places"

File and Print Sharing is enabled on both.

The new XP Home laptop can access the Internet - it just can't see the
shares on the other machine.

Any ideas ?

TIA

JM

Use only one protocol for File and Printer Sharing. If the network
needs more than one protocol, unbind File and Printer Sharing from all
but one of them. Details here:

Windows XP Network Protocols
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

Double-check the NetBIOS over TCP/IP setting on XP:

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. The "Default" setting
doesn't always work.

Run "ipconfig /all" on XP 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
 
S

Steve Winograd [MVP]

you could try specifing an ip address for each computer, then set the subnet mask to 255.255.0.1 note subnetmask must be the same for each pc the last digit of the ip needs to change on each pc

I think you mean 255.255.0.0. 255.255.0.1 isn't a valid subnet mask.

Most home networks use 255.255.255.0, which is the conventional subnet
mask for the 192.168.x.x private IP range (computers with IP addresses
192.168.0.1, 192.168.0.2, etc).
--
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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top