Discussion Locked

Workstation to Server Connection

0 helpful
25 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am having a small issue.... I have currently set up an small office with 6 pc's running XP Pro and a Server running small business server 2003. I have created a domain for them, which they are currently logging into. They were fine for about 2 days than suddenly they are complaining that the pc's are loosing connection to the server thru out the day, which is causing the pcs to lock up. They are get a message that is trying to connect to the server and they eventually do. Why would the connection drop??

25 replies

by bfilmfan

How many user or device Client Access Licenses did they purchase would be the first question I would ask.

Secondly look at LSASS and make sure that it is not locked at 100% utilization. If it is, this will cause the RPC service to fail and clients will lose connectivity and "lock up."

What is being recorded in the client and server event logs?

by lopez_danny

I purchased all 6 pc and server from dell. I will check the lsass utilization this afternoon. Any other ideas??

by lopez_danny

I am not sure if it is a virus.. I have not checked... could that also cause it to lose connection?

by hyoi

You might take a good hard look at your switch/hub. This sounds more like an infrastructure issue than anything else. Either that or the server has a virus, or you got hit with a network aware virus. I would consider the virus thingy less of a likelihood.

To troubleshoot this, I would try pinging the server from the workstation when they lose their connections. Then ping from the server to the workstations. If both fail, I would think that it is likely that you're facing either a wiring issue (interference on the cables), or your switch is going bad, especially if all of the Workstations started losing connection all at once.

HTH

by cliff680

Certainly sounds like a switch or hub problem to me. I just had a similar problem at one of my clients and I found out the the HUB was the problem. Try switching it out to see if communications improve.

by lopez_danny

The Hub is new. Here is the full Message:

Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40961
Date: 1/1/2005
Time: 12:30:45PM
User: N/A
Computer: COMPUTERNAME
Description:
The Security System could not establish a secured connection with the server
DNS/prisoner.iana.org. No authentication protocol was available

by cliff680

Is your server a DNS server?? If so, your workstations should be pointing at the server for DNS resolution. How is that setup?

by lopez_danny

Yes. The Server is also playing the role of the DNS. The workstations are pointing to it. I created a Forward lookup on the server in DNS. FOr it to give the workstations DNS entries. I might have missed a step. They were getting disconnected thru out the day. Can you help me out? THe are using DSL thru earthlink. I would appreciate the help

by cliff680

OK, how are the PC's getting their IP stack, did you assign it statically, or is it coming through DHCP?

by cliff680

I would setup DHCP and have that also pass out the DNS information to your workstations. The primary DNS server should be your server. You can also setup a reverse look zone.

Out of curiousity can any of the machines get to the internet? What is the primary DNS IP address on the workstations?

by lopez_danny

Yes they could. They need to because they use a webbased app. The primary dns on the wkstations is 192.168.1.2 whic is the server IP address

by cliff680

The error message that you gave to me indicated that this is a DHCP/DNS problem. You could try to institute DHCP and see if that doesn't help out. Just try it out on a couple of PC's to start, to see if communication improves. I think that using DHCP might help you out.

by lopez_danny

OK, So i should go ahead and setup DHCP to give out the IP address along with the DNS info to the workstations? I just have to put the range 192.168.1.x thru 192.168.1.x into DHCP? WOuld it still work even though they are 192.168.1.x IP?

by cliff680

Yes, go ahead and setup DHCP to give out IP addresses, gateway's (router) and DNS info. Just make the range 192.168.1.20 to 192.168.1.40. In the scope options enter your DNS and router (gateway info)
Yes DHCP will work for 192.168.1.x addresses.

by lopez_danny

Hey, I really appreciate your help. I am just getting my feet wet in the consulting business. It is good to meet someone who willing to share info and help. My name is Danny. My email address is lopez_danny@sbcglobal.net. What is your name? If I get stumped somewhere else can I email you somewhere?? I will give that a try tomorrow and try one at a time.

Thanks again

by cliff680

No problem, I go to this site as well when I have questions. I'll e-mail you my address.

This discussion is closed to new replies.