Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I have a small network about 45 workstations, running windows 95 or 98, the server is running Novell 4.11 with service pack 6, the net work is ethernet running 100 half.
Am I going to have any problems with upgrading my workstations to Windows ME? Besides the fact that its a Microsoft product.
I am running a Windows ME station client version 3.3 on a Novell 4.11 network Service pack 7. I have had no problems yet.
0 
I was running client 3.21 with Windows ME on a Gateway laptop and a 4.11 novell server and couldn't get the client to run right. So I switched it to 98 SE and it worked great!
0
i have a lot of problems with windows me. some of them i had with windows 98.for example when i am make a search on internet explorer after i wrote the searh contents, i click the "serch" button the internet explorer windows gets stock for a few seconds than it continues the search
another problem that i faced in win98(se) too is when i click on the outlook express icon it takes ~ half minute until it opens. and allso athe file search (start\search\files and folders...) i can't make any search at all
file naming- why can't i rename filenames with the"/\:*etc" symbols ?
i can't rename the cdrom drive from "compact disc" to something else
did i bore you ? sorry
0
I had a number of problems installing the novell client on ME workstations - apparantly novell don't support it. My advice is stick with 95/98 it'll be much more stable!
0
Problems that I have experienced from a clean load with ME is that the Novell Client 3.21 doesn't function proberly for mobile clients. Novell tends not to recongize the PPP conection through the ME Dailup adapter. However, if I upgrade from 98se to ME and load the client, the Novell Login window pops up fine, and prompts for user login info. My suggestion since Novell Supports 95/98 upgrade from their, or just go with linux.
0
I have a client with a Netware 4.11 server (I don't think it was patched since purchased - but it has been running fine for a couple years - so didn't fix what wasn't broke). The workstations (15 of them) are running mixed Win95 and Win98 workstations with either older Intranetware and newer NW Client32 3.3 and all has been fine. Until yesterday.
Someone came in with a Dell Notebook Inspiron with Windows ME. With Microsoft compatible ipx it would see the Netware server and prompt for login. But the login seemed to be in bindery mode as it did not run the container login script. When I downloaded and installed NW Client32 3.3 it installed but wouldn't display the red Netware login box nor would login to the server regardless of either the Microsoft or Netware was set as default in Network properties (with both clients or only Novell client). No matter how I configured the network setting with Novell alone or with Microsoft it wouldn't show a login box. Yet under network it showed the Netware volumes but wouldn't display anything. Only when I used the Microsoft client for Netware and ipx comptible mode did I get a Microsoft login box with the third line showing the server.
But again, never ran the container login script.Thought maybe I could use the older MS NDS client (found the msnds.exe file on the net) which I had run on older Win95 workstations and worked on those older workstations). I downloaded and installed it. But on the reboot, got VFAT errors and Windows ME said that I needed to run the system restore or reinstall Windows! Originally couldn't get into safe mode unless I ran step by step and didn't run the native isfmgr. Got in with safe mode and luckily Win ME had a snap shot from day before at 3:00 pm when I began the whole nightmare. Ended up restoring to that point. Don't, Don't run the Microsoft NDS patch for Win95 on Win ME boxes!!!
Got back into Win Me and ended up using the Microsoft ipx compatible protocol and wrote a .bat file to map the network drives (which I added to the startup folder, for now).
Maybe this is just quirky on the Dell. Might need to patch the server after all?
The NIC was a Linksys 10/100 which worked fine on another Win98 Dell Notebook.
Any help would be most appreciated.
Thanks
0
It's not Just the Dell .. tried a Toshiba with a 3com card .. seemed to work at first then just went pear shaped.
Can't even login to an NT4 domain correctly.
As far as I can figure from the Novell and MS sites its down to the Novell client not seeing the PCMIA card (as the processor is too fast, and it hasn't been initialised yet).
Novell have had this sort of problem for a couple of years (they talk about PII 400 pcs having the problem with client 3.1)
No easy solution springs to mind .. come back W98!
0
hi folks, this is windows ME vs netware client 3.3 (Server NW 5.0). this is a
1GZ dell laptop (8000)
I have the same symptoms as described above;
can't get the login box, vxd errors reported on startup, yet can go through the network neighborhood and retrieve files from the server. aggravating.
please let me know if someone discovers a cure....
0
Try this:
Using REGEDIT HKEY_LOCAL_Machine|Network|LocalThis is where you'll find that reference to the PrimaryProvider is inaccurate... I've seen it as "" (in other words, missing), as "WindowsFamilyLogon" which is wrong. Replace whatever you have entered there to: "Novell_Netware"
Another entry to check out:
Username ... if it is set as "Default" change it to the appropriate.The PrimaryProvider, though, is the important change!
Additional tips: Prior to Novell client install, uninstall the Virus Protection software (don't just disable it) plus, remove the Client for Microsoft Networks from the Network list.
Good luck!
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
