A few days ago I had exactly the same problem so I when to HP's forum site (http://forums.itrc.hp.com) and searched for "defragmenter lockup" and found all kinds of clues. The one I used was to use msconfig and remove several startup files that I knew about and it ran just fine.
My home network is made up of a LinkSys wireless router connected to a DSL modem. My XP machine (a fairly new HP from Best Buy) is directly connected to the router while my Win 98 machine (a new install on an old Win 95 PC) connects via the wireless. Only the TCP/IP protocol is installed...
Well, I just added SP2a to 5.1 and it worked. Did you try doing the whole thing over again - starting out with the expansion of the nw51sp2a.exe file? I assume that you have checked the NDS effective rights of admin at both the [root] and at your O=whatever.....
If there is "only" a subordinate on that server, then you "should" be able to remove directory services and then "Install directory services" back on that computer.
I guess I would be sure to have a good backup of NDS before doing anything. Then try a dsrepair first.
You really can't use VLMs with the latest Intel 10/100 cards - at least I haven't been able to - so we've switched to the DOS 32bit client when necessary.
If you have internet access, use an NTP source (e.i., 128.118.25.3:123) and set the hardware clock to off. If this IP addr is no good, yahoo the term "ntp" and you will find lots more.
Bring your 4.11 servers to the latest service pack<br>Upgrade the server that holds the master of the [root] partition first<br>When asked during file copy, be sure to OVERWRITE all files, regardless of date.<br><br>For an in-place upgrade see TID 10021958<br>For across-the-wire upgrade see TID...
Go to <A HREF="http://support.novell.com" TARGET="_new">http://support.novell.com</A> and search for tid 10019972. It gives the appropriate format for using the "tree" command in login scripts...
There is a whole bunch of reasons why you might get double connections including such things as presistent mappings, etc. Go to <A HREF="http://support.novell.com" TARGET="_new">http://support.novell.com</A> and search for - "connections" AND "nw5" -. There are several tids...
I've never installed a SP from a CD, my preference has always been the Internet download. But let's try some debugging techniques. Maybe there is actually something wrong with the CD or maybe something wrong with your CD player, etc. <br><br>I guess I would first make space on one of your server...
Hmmmm, you might try putting the client software on your c: or d:, go to the admin directory in the client software and completely remove the client software and then reinstall it.<br>
What looks like is happening is that somehow the winsock.dlls didn't get updated. During the normal NetWare...
Well, yeah. Anytime your workstation can't see the fileserver, you will get messages like this. Now what's wrong???<br>
1. Protocol problems (server is IPX, ws is IP or server is 802.3 IPX and ws is 802.2 IPX).<br>
2. Someone has actually disconnected your ws from the network.<br>
3. Bad hub...
So far Novell is saying that it is a "cosmetic" error message - in other words, they haven't fixed it yet but don't worry about it. And re IDE drives, you really shouldn't be using them on an active server. Best to be SCSI or RAID. Anyway, for additional info on IDE and timesync, go...
Also, NAT builds a table for those private address users so the returning packet from the Internet can be directed to the correct workstation. This, in effect, is a firewall preventing those from the public side accessing the private numbers. <br>
<br>
Now you can set up static NAT, assign...
NAT is a standard TCP/IP protocol as specified in RFC 1631. Most Cisco routers also include NAT as a option. Soooo..., NAT's primary job is to convert a "bunch" of IP addresses on one side of the router to a single IP address on the other side. <br>
<br>
Typically, one side of the...
Well, that is exactly right. Your IP only server/client only speaks IP and the older server/clients speak only IPX. If you add the IPX stack to both the IP only devices, then they can see and talk to the IPX machines. <br>
<br>
This is the big change with NetWare 5 - it can speak pure IP, never...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.