The key here is that the DHCP server has to be on the same segment as the address's your handing out. If this is the same segment as your IAS server your in business your good.
Otherwise you need to do one of the following.
1 - Put DHCP on the IAS server.
2 - Create a second net on another...
If your using Sprints EDO you should know that they don't support DHCP on a Microsoft IAS server. Seems they just didn't want to take the time to do it.
The client authenticates, I see it in the event log. But no IP address is assigned.
Varified all routes.
V that DHCP working.
V all correct protocols working.
If anyone has input it is welcome.
Thanks.
I have a new IAS server that works with a single IP address, no problems. When I switch to point to the DHCP service on the same server a IP address doesn't get assigned to the client.
I have followed the directions completely off several web sites for setting up DHCP, IAS and RAS. but no...
You are already using timesync.nlm, it is loaded by default when the OS is loaded. Netware relies heavily on time synchronization in NDS.
Im assuming that you want to pull time from a NTP timesource on the Internet. Im currently doing this without Winsock installed. using NW5.0 with SP6a...
I made an extensive research for a image product for Netware in June 2003. I found only one existing product, that product is no longer sold.
My findings summary was, sorry your out of luck.
If you go to the following link it discusses in great detail the PerfLib error. While some problems can be resolved with MS q819716, this only resolves the problem for TCPIP Services...
Glad you went ahead with the drive add. I have done this several times with Compaq servers and Raid Arrays without any problems. I do find it irritating that W2K doesn't openly support dynamic adding of drives.
I don't have this problem on my Netware or Linux servers.
I find it significant that the slow server has two processors. This would seem to point to Win2K. I know that we had loads of problems with dual processors and Win2K.
From the hardware side make sure that you have updated the bios on the server. When the Proliant 3000 first came out the bios...
Are you using the latest Client 4.83 SP2. If not uninstall and install from scratch. There are several fixes that might apply.
The only other time that I have seen a problem like this was when there was a syntax error in the script. Some PCs would perform as you describe while some would...
Assuming that your hardware clock stays up to date you can do the following.
If TIMESYNC.CFG is set to "hardware clock = on" it will reset to the hardware clock which is not losing time.
The otherkiwi's idea of setting the NTP time source to a source on the Internet will be your...
I have resolved the issue on my own by comparing the registry entries for TS line for line. The following is what I did.
The registry entry for Terminal Services that defines the location of the video 0 device was missing. Once this line was added and the server restarted Terminal Services...
I have tried all of the above. Not sure about IPSEC, its running on all of our servers but there are no profiles so it shouldn't be performing a function.
I have summarized everything so far below.
Review of issue,
Port 3389 not open on server. Two servers suffering the problem.
Checked...
We had an administrator delete the RDP-Tcp (listener) while using the Terminal Services Configuration tool. When viewing from Terminal Services Manager there is no RDP-Tcp (listener)
Once I found this I went ahead and created a new Connection using the defaults. Failed.
Uninstalled and...
We are having a similiar problem with IIS, accept given enough time more and more people become locked out of sites. We also have the login problem just as you described.
So far we have been able to fix the problem but restarting the IIS service once every few days.
We have premier support...
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.