Search results for query: *

I am about to do what you are currently doing only a slightly larger scale. From what I have read though you neet your NT 4.0 server to be patched to at least SP5 or higher. Once this is done I will be doing an Exchange 5.5 to 2003 migration. Naturally, I am curious about your experiences with...

Well it turns out that this impacted DHCP and WINS configurations. I removed both and reinstalled dhcp with the same scope and wins. It seems to be working now. Thanks, Gary

Sorry, I forgot this. The server is Windows 2000 running on a Dell P4 2.4ghz with 512mb RAM.

Our system took a power hit last night and although I have got the server up no one can login to the system from their PC. The TCP/IP address was changed somehow. I switched it back to 192.168.1.50 for the internal gateway service. DHCP is handing out ip addresses OK and we can get to the...

I hope it is not to late to help you here. If you have not progressed to far with new information going into your rebuilt 5.1 server then there is hope for you. Novell has pretty good intructions in their knowledge base on how to remove a dead server from your tree and the procedures for...

I have seen this problem on rare occasions on both 4.x and 5.x servers. What is interesting to me is that by merely unloading and reloading the monitor.nlm the problem goes away. Good luck.

Das, I have seen this problem as well. Usually all I have to do is a ctl-alt-del and select end task for it to continue loading Win98 on my system. Occassionally, I have to reboot to resolve this issue. It doesn't seem to happen with the NetWare client ver. 3.21. Good Luck, Gary.

If I recall correctly, the frame types for IPX/SPX changed when NetWare 4.x was introduced. Try adding an 802.2 frame type to the 3.x box and see if you can see both servers then.

Novell doesn't mention the maximum amount of memory on their site (at least I couldn't find it). However, they do provide a formula for the recommended amount of memory and you can find it at http://support.novell.com/cgi-bin/search/searchtid.cgi?/10027635.htm Good luck, Gary.

You might want to try this out. This is for Compaq servers but it might work with others as well. http://www.compaq.com/support/files/server/us/download/10570.html Regards, Gary.

I would start by checking your Novell client to determine what protocol is the primary protocol selection and then check the printer to be sure it is talking that protocol. You may have to disable ip or ipx/spx on the printer as a method of determinig where the problem lies. You can do this...