XP Pro and Netware - Cannot Find Tree?

[DaveTulk]

I cannot for the life of me seem to be able to get my XP box to find my server. All of the Win98b systems find it just fine. When I boot. Iget the "cannot find tree" error.

I have the 4.83 client with the patch installed

Where do I start?

Thanks,
Dave

 

[TheLad]

What protocols are you running? NetWare 4.11 will only allow you to attach via IPX so you must ensure that IPX is enabled on your XP workstation. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[DaveTulk]

These are the protocols that are installed:

NWLink IPX/SPX/NetBIOS Compatable Transport Potocol
NWLink NetBIOS
TCP/IP

They are the ones that the 4.83 client software set up.

--Dave

 

[TheLad]

Try going into the Network Properties and check the properties of the IPX/SPX/NetBIOS etc....

Ensure the frame type is correct for your network. IF it is set to Auto, change it.

Failing that, uninstall and reinstall the client. I haven't experienced any issues with XP and Client 4.83 (yet!) -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[DaveTulk]

What is the frame type? and where would I confirm what my network is configured for?

I found it in the dialoge box but do not know if i should set it to 802.2,802.3 .....

Regards,
Dave Tulk

 

[TheLad]

On your NetWare server console, type:

CONFIG

It will tell you the protocols currently in use - including the frame type for IPX. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[DaveTulk]

I saw two things on that screen that said Frametype

VIRTUAL_LAN
802.3

I set my client to the 802.3 but still no go.

 

[TheLad]

I'd suggest uninstalling and reinstalling the client, making sure you configure it for IPX only -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[Catadmin]

Also, you might want to check with Microsoft to make sure your XP box doesn't need Gateway and Client Services for Netware installed in addition to the NWLink protocols. If it does need it, then that might be the reason you can't connect, even though you have the NWLink protocols on.


Catadmin - New to Server Admin, but willing to learn... All help is appreciated.

 

[TheLad]

All the XP boxes I have configured have never required any of that - just the protocols that Dave has already got configured. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[DaveTulk]

Isn't there a way to call the server by IP or something? With Windows, If I cannot see a system I can still run the IP down and get to the resource if it is physically available.

The only other consideration that I can think of is that this box is on a different switch than the server. I am not sure if that matters, I have 12 other Win98 systems all connecting fine fron the second switch.

- Dave

 

[TheLad]

NetWare 4.11 will only allow you to attach via IPX. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[Catadmin]

I only suggested Gateway & Client Services for Netware because I know Win 2000 needs it in relationship to Netware. Didn't know if XP needed it or not. Wanted to throw out the thought just in case. @=)

The only other thought my limited experience has is maybe it isn't frame type or protocols. (I don't know if the tree message is generic or specific to certain situations). Are you sure the port it's plugged into or network card and / or cable haven't gone bad? It's not unknown for a new piece of equipment to be junk. Try swapping patch cables or ports (or both) out. Check under Device Manager to see if there's a diagnostic tool or a troubleshooting tool for the network card. If all else fails, double check the website of the card's manufacturer to make sure the driver isn't bad.

Catadmin - New to Server Admin, but willing to learn... All help is appreciated.

 

[Catadmin]

Oh, wait! Another thought! @=)

Have you tried unintstalling and reinstalling the NWLink protocols themselves?

Catadmin - New to Server Admin, but willing to learn... All help is appreciated.

 

[DaveTulk]

What about the physical network itself? My NW server is located about 300 feet accross the building and connected to a Cisco switch. That switch is connected to another switch on my side of the building, that is where I am hook in. The Win2k server also get's that same error message.

Is it possible that the switches have some sort of configuration issue? Are switches ambiguous to the protocols of the servers and clients?

-Regards
Dave

 

[Catadmin]

If it would be a physical network issue, I would think that everything on the w2k side of the switch would be having problems, not just that one machine. Unless, of course, it is the port or the cable that the machine itself is plugged into. Have you tried changing out the cable with one you know works and switching the port the machine is on?

Catadmin - New to Server Admin, but willing to learn... All help is appreciated.

 

[doublej2]

Try going into Novell Client Properties, Protocol Preference and make sure IPX is the preferred protocol.
Also make sure your network card is not set to autosense
and is set to the same setting as the port on the switch.

cheers

JJ