Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

XP cannot login Netware 5

Posted on 2004-04-26
10
Medium Priority
?
242 Views
Last Modified: 2006-11-17
I received a Dell notebook with WIndows XP pro. I have a novell 5.0 server running IPX only. I have several  XP workstations on the network that I have configured and are using the "Microsoft Novell client" without any problems. I cannot get the Dell notebook to log into the Novell server upon entering the proper tree and context it will sit for several minutes and report that it cannot authenticate to the server. I know its not the username as I can go to a workstation and login just fine. My setup is simple add the microsoft client for netware to the ethernet adapter properties and set the tree and context it should then work as my others do. Any ideas?? Many Thanks.
0
Comment
Question by:slgates
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
10 Comments
 
LVL 34

Expert Comment

by:PsiCop
ID: 10928950
Well, my first recommendation is that you NOT run the Micro$oft Client for NetWare - it is a deliberately-crippled piece of garbage-ware. Switch to NetWare Client 32, and you can get rid of IPX while you're at it. NetWare v5.x and later don't need IPX, works with IP very well. You can download NetWare Client 32 for free from http://support.novell.com

I would also check the framing type - do NOT allow Windoze to auto-select the frame type for IPX. Manually set it to whatever it needs to be.

<pet peeve>
"Novell" is a company. "NetWare" is a network OS.
</pet peeve>
0
 
LVL 1

Expert Comment

by:AngelRider
ID: 10943687
But don't forget to load IP as a protocol on your Netware box... :-)
0
 

Author Comment

by:slgates
ID: 10946066
Thanks. I corrected my own issue. I plugged the ethernet cable into a newer switch and all iswell. Not sure why the old switch would not see the Netware server with the new notebook but worked fine with other workstations but not going to spend the time on discovering the cause. Thanks for the suggestions.
0
New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

 
LVL 34

Expert Comment

by:PsiCop
ID: 10949303
Don't forget to post a (free) Question in the Community Support TA and have a Moderator PAQ this one and refund your points. Be sure to include a link to this Question.
0
 
LVL 34

Expert Comment

by:PsiCop
ID: 11688938
Hello?
0
 

Expert Comment

by:wilf_thorburn
ID: 11712497
How do you add the IP protocol to the Netware box
0
 
LVL 34

Expert Comment

by:PsiCop
ID: 11726420
Go to the server (or Remote Console into it) and at the System Console screen (the one with the prompt made up of the server's name and ending with a ":", called the "colon prompt") enter --> inetcfg

You should go into the NetWare network configuration program - you may be prompted to allow it to copy stuff from AUTOEXEC.NCF; if so, let it. From here you can define new interfaces and protocol support and restart the communications sub-system without having to reboot the server.

Before you do that, have an a static IP in hand, know the netmask, default gateway and proper framing type.

NetWare will easily support both IPX and IP protocols, allowing you to migrate your clients from IPX to IP at your leisure. When migrating clients, be sure to remove IPX support from the client.

Note that in order for IP-based clients to see the server, you need to have the IETF-standard Service Location Protocol (SLP) running on the server. Normally, the SLP Service Agent loads automatically when IP support is enabled. You also need to load the SLP Directory Agent, which you do at the colon prompt by entering --> LOAD SLPDA

You'll need to put that LOAD statement somewhere in AUTOEXEC.NCF - at the end is fine.

You're running NetWare v5.x, so it supports SLP v1.0. The DA can run unscoped in v1.0, but when you upgrade to NetWare v6.x, it uses SLP v2.0, and you will have to create, in NDS, an SLP Scope object for the DA to use. Just something to keep in mind for the future.
0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 15759091
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When trying to connect from SSMS v17.x to a SQL Server Integration Services 2016 instance or previous version, you get the error “Connecting to the Integration Services service on the computer failed with the following error: 'The specified service …
On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Visualize your data even better in Access queries. Given a date and a value, this lesson shows how to compare that value with the previous value, calculate the difference, and display a circle if the value is the same, an up triangle if it increased…

704 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question