XP SP2 + Netware

• Oct 15, 2004

• #2

Mike2287

IS-IT--Management

Mar 15, 2004

214

US

I think whats causing that is the netware services are not starting fast enough. Here's a link from Novells web site that may fix it.

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10086186.htm

Mike

 

Upvote 0 Downvote

• Oct 15, 2004

• Thread starter
• #3

nevets2001uk

IS-IT--Management

Jun 26, 2002

609

GB

Thanks.

The problem it describes is exactly what we're experiencing. However looks like 4.90 SP1 and above should fix it. The registry keys it suggests changing are already at the new values.

We are using Client SP2 but have also tried SP1 on one of the systems.

Any further ideas.

Steve G (MCP)

 

Upvote 0 Downvote

• Oct 15, 2004

• #4

JockMullin

MIS

Jul 11, 2002

878

CA

Hi, Steve

I have found that setting the connection type, speed, frame type etc rather than leaving things on Auto negotiate improves the speed of connecting to Novell servers.

i.e. if your frame type is ethernet_802.2 and you are connecting at 100 mbs half duplex, then put those settings into the client and network properties and it may help avoid timeouts and subsequent failure to connect.

Also, I have found removing the Novell client, installing the MS client and getting it working and then reinstalling the Novell client sometimes helps, though not really sure why.

Jock

 

Upvote 0 Downvote

• Oct 15, 2004

• Thread starter
• #5

nevets2001uk

IS-IT--Management

Jun 26, 2002

609

GB

Thanks Jock.

I'm just in the process of building the forth system. Going to leave of Windows SP2 and stick with SP1a for the time being and see what happens.

Will also try your ideas and see if any of them do the trick.

Will keep you informed of the outcome.

Cheers

Steve G (MCP)

 

Upvote 0 Downvote

• Oct 15, 2004

• Thread starter
• #6

nevets2001uk

IS-IT--Management

Jun 26, 2002

609

GB

Well our test system worked fine (Windows SP1a and Client 4.90 SP1a). Found the tree almost instantly. However as soon as we took it to the users desk it started displaying the same problem.

Only difference is that it goes through a cisco switch before reaching the main switch for the servers. Our test system uses a simpler switch in our office. When we brought back one of the Windows SP2 systems which had the problem to our IT office, again it found the tree in under 2 seconds.

Guessing its all down to some setting on the cisco switches which all the office users goe through, although my knowledge of switches is very limited.

Steve G (MCP)

 

Upvote 0 Downvote

• Oct 15, 2004

• #7

bcastner

IS-IT--Management

Aug 13, 2002

29,271

US

thread558-912351

 

Upvote 0 Downvote

• Oct 15, 2004

• #8

TimRegester

Technical User

Dec 18, 2002

195

GB

I am not so sure this is spanning treem but good to remind people. I may be out of date but as I understand it the Novell IP client/server mechanism uses SLP (Service Location Protocol) to replace SAPS as was used in IPX. SLP is a multicast protocol, multicast will work seamlessly on a simple unmanaged switch but switch to a managed switch and much tweaking of such protocols as IGMP and PIM is necessary to get the client seeing the SLPs properly.

I could go into real technical detail on this but suffice to say that XP must understand and not in anyway block SLP and the switch must forward SLP multicast packets to either all ports or at the minimum all the clients that request it.

Look at the Cisco multicast config and check that SLP can be seen at the client and that the multicast client request does not time out in too short a time. If the Timeout is too short the cisco switches will lose the address of the client and have to reconfigure themselves. Cisco switches are not the quickest switches in the world (the older ones are horribly underpowered) so this could easily explain the issue in this thread. A good ethernet analyser is the only real way of ascertaining whether there is any problem with SLP.

I learnt all this 4 years ago and have not had to troubleshoot Novell since and it may have changed, if it has and SLP is no longer used please ignore this post.

 

Upvote 0 Downvote

• Oct 15, 2004

• #9

BigShyBear

MIS

Mar 29, 2004

110

US

If you have NMAS installed, remove it. It's a known problem with switches, including Cisco and Dell.
In the Novell client Properties, Service Location tab add in the IP address of the box running SLP.

Mike Gallo

 

Upvote 0 Downvote

• Oct 18, 2004

• Thread starter
• #10

nevets2001uk

IS-IT--Management

Jun 26, 2002

609

GB

We're not having any problems through the cisco switches with the Windows 2000 PC's using Client 4.90 SP1a so am I right in hinking this could still be a problem with XP settings? If so are there any ones I should look at to ensure SLP is not being blocked?

Mike - When you say a box running SLP do you mean the Novell Server or something else?

Thanks so far guys. Perhaps we're getting somewhere!

Steve G (MCP)

 

Upvote 0 Downvote