CRM software on the Terminal will periodically error and boot out (data is set on the Primary server)

I have done nslookup on the terminal (no issue), it could ping primary server (and see the 192.168.50.2 IP Address)..

After a while, it works again (in allowing people to sign in). Then again, I get these errors and can't sign in.. I have done hardware diagnostic on both servers, swtich, and replace patch cables.. The issue seems to persist..

I searched online and I have checked the DNS time and time again (no issue).. When the Terminal Server is failing, I could log in on the primary server via RDP (without issue)... Check Terminal Server Licensing (per user), it seems to see the licensing (when I could sign into the TS)..

Any input would be greatly appreciated on what else do I need to tackle...

Additional Notes:

1) If a sesson pre-existed, you could sign in though any user profile not in session will not be able to sign in

2) CRM database is somehow not found when this happens (which is why I think they are correlated)

3) I think it could be hardware (some stated to try out drivers but the drivers has been on the machine for 4 years without issue until now)

4) Windows Update could be a culprit but not those I have googled and searched online (This is recent)

At the end, I think the machine could be going bad (and diagnostic did not pick anything up)... I just can't explain why this is happening

2 Replies

1st Post

Just those message as I stated... Nothing on the primary server on any issue... That is why it is perplexing.. It seems like it sees the server and if there is an update or something (not sure what), it does not see the primary server (which is also the DNS) and then does eventually...

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.