Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WinXP and Netware client, maybe

Status
Not open for further replies.

Granvillew

IS-IT--Management
Mar 23, 2003
65
AU
This is most like an XP issue as I have successfully set up PCs with DOS, Win95, Win98 and Win2000 on this network without any problems.

The environment - WinXP SP1 with Netware client 4.90 - Win2000 Server (for Exchange only); Netware 3.12 for print services and Netware 4.11 for apps and file server + plus some printing.

My problem is that I cannot access the files, and hence the printer service, on the Netware 3.12 server. I can access the fileserver itself but I only get a blank "items view".


BTW, I'm out of the office until the 6th January, so if you don't hear back from me for a while it's 'cos I'm lying back somewhere cool and shady with a drink in my hand.

Season's Greating to all!

 
Do you have IPX/SPX loaded?

Iolair MacWalter
 
Hi Iolair,

Yes, at least "NWLINK IPX/SPX/NetBIOS Compatable Transport Protocol" is loaded and set to auto detect frame type and is set as the preferred protocol for the Netware Client.

I've checked and there is not a dedicated IPX/SPX protocol available. Is that the problem?

Thank you.
 
Install the client doing a custom install and select "IPX AND IP".

You might also need to manually set the frame type and network number.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
 
Hi Marvin,

I usually do a manual install and select IPX & IP. Just to be certain I have re-installed and done so...no change.

I have also set the frame (802.2, after checking the server) and the network address...again, no change.

On the client setup I am still seeing "NWLink IPX/SPX/NetBIOS" under the protocol and not a dedicated IPX protocol. Sorry, hadn't noticed this before.

Another thing that I have only just pickup on is that when I attempt to map to the 3.12 server (in the login script) I get an error 8884. The only reference to this on Novell's site is about WinNT client being used, as opposed to client32!?!

Thank you
.
 
Oops, very embarrassed.:~/ I actually had a look for a later version but missed the SP!

I’ve now applied that but there doesn’t seem to be any change, except that the connection time to the 4.11 server may be quicker.

Thanks for the help, if I find a fix I’ll post it here.
 
You might try this TID...
Also try setting your preferred protocol on your client to IPX. Or you could also unbind IP from the Novell client. In Windows go to Network Properties, Network Connections, Advanced Tab, Advanced Settings, Local Area Connection, Novell Client for Windows... Uncheck IP.

Another thought is this. I've seen cases where it's necessary to use 802.3 instead of 802.2 when using windows XP. (have to do it on both server and workstation) This goes against the grain though and I've gotten a lot of hassle for it from Novell techs in the past. But if it works, why argue the point.






Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top