help4haas
asked on
Can anyone help me re-establish a lost Novell 4.11 network connection from a newly upgraded Windows XP Pro Client?
I need to describe a little history in order to provide a clear explanation of the problem.
I have a Novell 4.11 Server that has been in operation for more than ten years. It is a file server to six Windows Clients that are also connected to a Windows 2000 Server. The network originally consisted of the Novell Server and six Windows 98 Clients. As a result of a proprietary application/program being upgraded (or downgraded, depending on your server preference) to Windows Server 2000, the clients have all been upgraded to Windows 2000 Pro over the past few years. The Windows 2000 Server was introduced about four years ago and the company that manages the application in question has been progressively building the platform on the Windows Server and removing the associated operations of some clients off from the Novell Server. They have managed to complete enough that four of the clients no longer access the Novell Server for any purpose. All of those functions, primarily POS operations are now handled by the Windows Server.
My issue is with one of the remaining two clients that still use the Novell Server for payroll and customer database resources housed within this program. Both Clients are identical Dell boxes, purchased with Windows XP Pro OS (Windows 2000 Pro pre-installed) and put in service at the same time using the pre-installed windows 2000 Pro OS. They have worked flawlessly until the users were required to upgrade to Windows XP Pro to satisfy a company request a couple of weeks ago. Rather than usig the full blown XP version that came with the Dells, we purchased two upgrade packages. The first upgrade went without a hitch other than needing to download a NIC driver. As soon as the driver was installed and the client was rebooted, the user logged into both servers without any problem and all mapped drives to both servers had access equal to pre-upgrade status. I did not have to upgrade the Client software or make any changes. I just downloaded a Windows XP Pro compatible NIC driver and installed it. The property sheet for that NIC lists the following parameters:
Client Service for Netware
Client for Microsoft Networks
Deterministic Network Enhancer
File and Printer Sharing for Microsoft Networks
QoS Packet Scheduler
NWLink NetBIOS
NWLink IPX/SPX/Compatible Transport Protocol
Internet Protocol (TCP/IP)
Now, the set up for the problem:
FYI, both of these Dells are Intel Pentium 4, 3.0 Ghz, 1GB of RAM
The second Windows XP Pro Upgrade seemed to install normally, but after installing the NIC driver and configuring it, I could not access the Novell Server. The client did not see the tree or server, but the user could connect and log in to the Windows Server. Late Friday evening, after several attempts to make a Netware connection, and fighting with some conflicts between AVG Security Software and Microsoft Outlook, I decided to take the workstation home so I could start from scratch and reinstall the operating system over the weekend.
The machine obviously had issues due to the exorbitant time it took to shut down and reboot when that operation was performed and, after trying in vain several times to run the MS Office Detect and Repair function, and finding that the uninstall process failed multiple times on both MS Office 2003 Pro and the AVG product, I chose to follow this "take it home" path that I believe caused the conundrum I am in now.
Over the weekend, with the client off the domain, I backed up all data on the C drive to a USB external drive, installed Windows XP Pro using the Full OS package that originally came with the Dell machine and re-installed the MSOffice, the AVG, and all drivers. I had it connected to my cable Internet connection, so I downloaded and installed all Windows and Office 2003 Updates. The machine operation was like new as it relates to booting and other functions at this point.
Now to the problem at hand:
Monday, I returned it to the domain and installed the latest Novell Client 4.91 SP5 (which could be my problem) and I was still not able to connect to or log in to the Novell Server. Eventually after much manipulation trying both the Novell Client and the Windows Client for Netware I was able to see the folders in a previously mapped drive on the Novell Server, but the icons I was getting were like a CDROM Drive icon with a blue "e" on them and I could not write to the drive or save a new folder. This same user who has had nothing as far as rights on the Novell Server changed intentionally, logged into and created a profile on the operational (1st upgraded) client and got the same response from that work station. The other user who normally uses that client WS can log in and write to the same mapped drive on the Novell Server and the mapped drive icons are not changed from the original icon.
My suspicion is that I am either using a client that is too advanced for Novell 4.11 and I should probably have used 4.83 because a search I just completed found this remark on a Novell Web Site - (The 4.83 client is still useful because if offers better compatibility with NetWare versions older than 5.0 and also works better on NT 4. The 4.83 SP2 client can be found here, and patches for it can be found here)
Am I on the right track here?
Have I in some way, either by removing the client from the domain to install the OS and drivers, or by using the 4.91 client, caused the access rights for this user to convert to a eDirectory format?
(I'm not even sure if that's possible)
I admit that my Novell experience is limited and worse yet, OLD. My normal work is totally Microsoft Windows 2003 Server and AD related, but I have maintaned this small network for over fifteen years and due to limited changes that required intervention at the server, such as new users to add or rights to administer, and the reliability of Novell Servers - I am very out of touch.
I need to get this user reconnected to the Novell Server with Full Access Rights until they can complete the program update and move her functions over to the Windows Server.
Please help if you can. Thank you in advance!
I have a Novell 4.11 Server that has been in operation for more than ten years. It is a file server to six Windows Clients that are also connected to a Windows 2000 Server. The network originally consisted of the Novell Server and six Windows 98 Clients. As a result of a proprietary application/program being upgraded (or downgraded, depending on your server preference) to Windows Server 2000, the clients have all been upgraded to Windows 2000 Pro over the past few years. The Windows 2000 Server was introduced about four years ago and the company that manages the application in question has been progressively building the platform on the Windows Server and removing the associated operations of some clients off from the Novell Server. They have managed to complete enough that four of the clients no longer access the Novell Server for any purpose. All of those functions, primarily POS operations are now handled by the Windows Server.
My issue is with one of the remaining two clients that still use the Novell Server for payroll and customer database resources housed within this program. Both Clients are identical Dell boxes, purchased with Windows XP Pro OS (Windows 2000 Pro pre-installed) and put in service at the same time using the pre-installed windows 2000 Pro OS. They have worked flawlessly until the users were required to upgrade to Windows XP Pro to satisfy a company request a couple of weeks ago. Rather than usig the full blown XP version that came with the Dells, we purchased two upgrade packages. The first upgrade went without a hitch other than needing to download a NIC driver. As soon as the driver was installed and the client was rebooted, the user logged into both servers without any problem and all mapped drives to both servers had access equal to pre-upgrade status. I did not have to upgrade the Client software or make any changes. I just downloaded a Windows XP Pro compatible NIC driver and installed it. The property sheet for that NIC lists the following parameters:
Client Service for Netware
Client for Microsoft Networks
Deterministic Network Enhancer
File and Printer Sharing for Microsoft Networks
QoS Packet Scheduler
NWLink NetBIOS
NWLink IPX/SPX/Compatible Transport Protocol
Internet Protocol (TCP/IP)
Now, the set up for the problem:
FYI, both of these Dells are Intel Pentium 4, 3.0 Ghz, 1GB of RAM
The second Windows XP Pro Upgrade seemed to install normally, but after installing the NIC driver and configuring it, I could not access the Novell Server. The client did not see the tree or server, but the user could connect and log in to the Windows Server. Late Friday evening, after several attempts to make a Netware connection, and fighting with some conflicts between AVG Security Software and Microsoft Outlook, I decided to take the workstation home so I could start from scratch and reinstall the operating system over the weekend.
The machine obviously had issues due to the exorbitant time it took to shut down and reboot when that operation was performed and, after trying in vain several times to run the MS Office Detect and Repair function, and finding that the uninstall process failed multiple times on both MS Office 2003 Pro and the AVG product, I chose to follow this "take it home" path that I believe caused the conundrum I am in now.
Over the weekend, with the client off the domain, I backed up all data on the C drive to a USB external drive, installed Windows XP Pro using the Full OS package that originally came with the Dell machine and re-installed the MSOffice, the AVG, and all drivers. I had it connected to my cable Internet connection, so I downloaded and installed all Windows and Office 2003 Updates. The machine operation was like new as it relates to booting and other functions at this point.
Now to the problem at hand:
Monday, I returned it to the domain and installed the latest Novell Client 4.91 SP5 (which could be my problem) and I was still not able to connect to or log in to the Novell Server. Eventually after much manipulation trying both the Novell Client and the Windows Client for Netware I was able to see the folders in a previously mapped drive on the Novell Server, but the icons I was getting were like a CDROM Drive icon with a blue "e" on them and I could not write to the drive or save a new folder. This same user who has had nothing as far as rights on the Novell Server changed intentionally, logged into and created a profile on the operational (1st upgraded) client and got the same response from that work station. The other user who normally uses that client WS can log in and write to the same mapped drive on the Novell Server and the mapped drive icons are not changed from the original icon.
My suspicion is that I am either using a client that is too advanced for Novell 4.11 and I should probably have used 4.83 because a search I just completed found this remark on a Novell Web Site - (The 4.83 client is still useful because if offers better compatibility with NetWare versions older than 5.0 and also works better on NT 4. The 4.83 SP2 client can be found here, and patches for it can be found here)
Am I on the right track here?
Have I in some way, either by removing the client from the domain to install the OS and drivers, or by using the 4.91 client, caused the access rights for this user to convert to a eDirectory format?
(I'm not even sure if that's possible)
I admit that my Novell experience is limited and worse yet, OLD. My normal work is totally Microsoft Windows 2003 Server and AD related, but I have maintaned this small network for over fifteen years and due to limited changes that required intervention at the server, such as new users to add or rights to administer, and the reliability of Novell Servers - I am very out of touch.
I need to get this user reconnected to the Novell Server with Full Access Rights until they can complete the program update and move her functions over to the Windows Server.
Please help if you can. Thank you in advance!
When you install the client, are you selecting 'custom install' and selecting 'IPX Only'? That's what you need for Netware 4.x. If you choose the default install it will select IP only and you won't see the tree.
There is almost nothing 4.91 cannot do that 4.83 can (some Zen stuff, but it doesn't sound like you use Zen). I would advise always using the latest client.
There is almost nothing 4.91 cannot do that 4.83 can (some Zen stuff, but it doesn't sound like you use Zen). I would advise always using the latest client.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Did you reinstall the IPX protocol when you rebuilt the machine? You should be able to connect to a 4.11 tree with the latest client. I notice you have installed the client service for Netware, try removing that from the freshly built machine.
Let me know how you get on!