Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1569
  • Last Modified:

Unable to connect to network load balanced server via RDP

I have a single server that is in a NLB configuration. There used to be two servers but we removed one and I kept the NLB so that I didn't have to change the IP address settings for all of the RDP clients that still connect to the one remaining server.

This was working fine for years until yesterday. None of my users are able to RDP to the termianl server.  I tried to RDP to it via the NLB IP address and the IP address assigned to the server. I am able to ping just fine.

I check the NLB manager and everything appears fine. I right clicked the server in the NLB manager and selected control host and then stop. Then I tried to start it again and received the below error.

"Start" operation result : FAILURE (Cause : Critical Error, Check NLB status on machine)

I had this same issue yesterday so I removed the host from the cluster and then added it again and everything was fine. This morning, I have the same issue again and I am unsure why.

What could cause this and how do I resolve it?

Thanks,

Justin
0
JustinGSEIWI
Asked:
JustinGSEIWI
  • 2
1 Solution
 
xDUCKxCommented:
Since you're not using it, why not disable NLB and then assign the IP Address to the physical host?
0
 
JustinGSEIWIAuthor Commented:
That is an option. I would only like to do that as a last resort though. I want to keep the NLB in case I need it in the future.

Any thoughts on how to resolve the NLB issue?

Thanks,

Justin
0
 
xDUCKxCommented:
Follow the guidelines below to enable/view the logs for NLB:

http://technet.microsoft.com/en-us/library/cc753351.aspx

There should be something in there that will give us an idea of what's going on.  The System Logs should have info also.
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now