Very strange to see these errors on a 2003 server currently belonging to a workgroup. Box is used as a web test server by remote user. It has Cognos Series 7, iPlanet, Oracle and SQL loaded and the remote users are complaining they are having issues logging on to the the program, or that it's response time is very slow. I can access the program fine locally, and the server appears to be healthy from a hardware perspective. Being that this box is a member of a workgroup, DNS entries are not neccessary correct? I took this network over a week ago, and have been seeing some strange stuff like this as they are transitioning to a new 2003 domain.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
40960 & 40961
- Thread starter ascore55
- Start date
Try couple of things:
1) check which process is being utilized in task manager. It sounds like one of your agents or services is taking up the CPU.
2) What does your APPLICATION or SYSTEM event log say specifically? What is the SOURCE?
3) Also, which remote prog are they using? Remote Desktop? How are they being connected (LAN) or VPN?
1) check which process is being utilized in task manager. It sounds like one of your agents or services is taking up the CPU.
2) What does your APPLICATION or SYSTEM event log say specifically? What is the SOURCE?
3) Also, which remote prog are they using? Remote Desktop? How are they being connected (LAN) or VPN?
- Thread starter
- #3
1) Explorer.exe is taking up 12,232K.
But the server itself is not having the issue. The latency occurs when users are accessing a Cognos web application, which itself handles the signons.
2) The application log is full of DNS errors of which LSASRV is the source. The description specifically is, "The Security System could not establish a secured connection with the server DNS/xxdns.xxx.xxx. No authentication protocol was available." This box however, is a Windows 2003 server which is a member of a workgroup. I don't beleive it should have any DNS entries.
3) Again, they are accessing the server through the aforementioned web application.
But the server itself is not having the issue. The latency occurs when users are accessing a Cognos web application, which itself handles the signons.
2) The application log is full of DNS errors of which LSASRV is the source. The description specifically is, "The Security System could not establish a secured connection with the server DNS/xxdns.xxx.xxx. No authentication protocol was available." This box however, is a Windows 2003 server which is a member of a workgroup. I don't beleive it should have any DNS entries.
3) Again, they are accessing the server through the aforementioned web application.
> DNS entries are not neccessary correct?
Correct.
Though I am wondering whether the server is trying to r-dns the clients that are connecting and failing?
Is the server setup to use a DNS server or not? If so does this DNS server have a reverse lookup zone?
If you hadn't also try rebooting the server, or just restarting the NETLOGON service.
Correct.
Though I am wondering whether the server is trying to r-dns the clients that are connecting and failing?
Is the server setup to use a DNS server or not? If so does this DNS server have a reverse lookup zone?
If you hadn't also try rebooting the server, or just restarting the NETLOGON service.
- Status
Similar threads
- Locked
- Question
- Locked
- Question