Solved

connecting to windows 2003 server with novell client with fpnw

Posted on 2004-04-11
5
440 Views
Last Modified: 2008-02-01
I presently have a Novell 6 network (2 servers) with Groupwise 6 (1 server) and want to migrate to Windows 2003 server (Active directory, DNS, DHCP etc.) I have all Windows XP SP1 clients using the Novell Client to access the Netware servers. I have built a new Windows 2003 box and made it a domain controller and installed FPNW (file and print services for Netware). For some reason I cannot get clients to connect to that Windows server without a password box popping up. I know it is something very simple I am not doing when configuring the clients on the new 2003 box, but their is virtually no documentation included with FPNW and very little info out their on the net on this subject. I need to get the Novell clients to synchronize their passwords with this 2003 server and NDS so I can migrate files and printing off the Novell server somewhat seamlessly. Any help would be much appreciated. If someone can give me a detailed explanation of how to accomplish this and maybe some advice to migrate from Novell to Windows 2003 in the easiest manner I will be very happy.
0
Comment
Question by:jml6278
[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
  • 2
5 Comments
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 10801763
The password box is coming up on the 2003 box?

You need to make sure all your clients belong to the domain. If they are 2000/XP clients right click on My Computer and click "Network Indentificiation" (or I think that tab is called "Computer Name" in XP) and change to the domain name. When prompted add you Administrator account and password to add the client to the domain.
0
 

Author Comment

by:jml6278
ID: 10801910
Maybe I haven't explained the situation well enough. Right now all users are just accessing the Novell servers for file and print services and authentication. I want them to be able to authenticate to the Windows 2003 server also, so I can move the printing services to that computer, and eventually migrate the files from the novell server to that computer. I don't want any of the users to have to enter a user name or password to use any services from the new Windows box. I want to point them to the new server for their printing (HP 8100dn printers) by having them click on an executible package that I have created using HP's Installation Wizard (point and click to add printers from the windows side) Then after that has been completed I will migrate their directory structure after I know that authentication works. I was under the impression I needed to create the user on the Windows server with the identical name as the user had on the Novell side and then check the Novell compatible login box which is now a tab in Active directory users and computers since I installed FPNW, and that the password would then synchronize between the novell and windows servers.  Thanks for any help that can be offered.
0
 
LVL 31

Accepted Solution

by:
Gareth Gudger earned 200 total points
ID: 10803367
That could work.
If you dont want to enable user/passes on the 2003 box yet you could simply enable the "guest" account and the server should just accept whatever the clients throw at it (ie the Novell user/pass)
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

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

Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

707 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