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!

Register Log in
  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CMS Login timeout

Status
Not open for further replies.
Warpiggy

Warpiggy

MIS
Nov 8, 2012
30
IE
All,

I have a CMS issue here in the office. We have one user who as of last friday cannot log on to our CMS server. I have trawled through this forum and i found a similar problem where one given solution was removing the cache etc. I have done that and reinstalled the program but it is still producing the same error. The weird thing is, i have removed the profiles from the user's documents, but when i reinstall CMS, it is still saving the session (his name, server info etc) where usally it has nothing saved...i've reinstalled CMS 100's of times in the past and haven't seen this happen yet.

Next weird thing about this...i managed to connect to the server using puTTY once this morning. Then the next time i tried it timed out on me and hasn't let me back in since. I actually have no idea at this stage what is causing the problem [mad][mad]

Has anybody here any experience of something similar?
 
Sort by date Sort by votes
Check the /var/adm/messages log on CMS (as root) - you may have rdns issues.
 
Upvote 0 Downvote
Hmm it gives the same error when i use either the server name or the IP so i think that rules rdns unfortunately. Thanks for the reply tho, much appreciated
 
Upvote 0 Downvote
what is really confusing me is the fact it is saving the user details/ server address and version etc after the reinstall. I have never seen that before and have no idea where it coulsbe saving it. all profiles were manually deleted and registry was checked to make sure there was no trace before i installed it...i'm obviously missing somewhere but don't know what it could be at this stage
 
Upvote 0 Downvote
I am no windows expert, so hopefully someone else will come around to answer that.

Changing the name to ip in CentreVu will only test DNS to the server. The CMS server will check the reverse DNS, and if there is more than one entry (for example you are on a laptop with both a wired and a wireless connection active), the connection back to your PC may fail. This would generate an entry in /var/adm/messages. Check your DNS reverse lookup zones (or ask someone who can), this is a common problem with connectivity to/from CMS (and the windows client will only tell you timeout or some such).
 
Upvote 0 Downvote
Got it in the end...on uninstall, CMS wasn't clearing the registry at all for some reason. When i went and removed EVERY little registry entry and then reinstalled, it worked like a charm!

Thanks for the help!

 
Upvote 0 Downvote
In future use revouninstaller this delets all registry inputs associated with the selected programm , got me out of a few issues like this.

APSS (SME)
ACSS (SME)
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

S
  • Locked
  • Question
【CMS R21】About button icon
Replies
0
Views
271
Sushi Guy
S
Stinney
  • Locked
  • Question
CMS R21 ODBC - Cant Connect
Replies
3
Views
676
phoneguy55
phoneguy55
Furrye
  • Locked
  • Question
CMS API Integration
Replies
9
Views
2K
jimbojimbo
jimbojimbo
Bucky101
  • Locked
  • Question
Scheduling multiple CMS Reports reliably
Replies
1
Views
731
SoftwareRT
SoftwareRT
ncheung
  • Locked
  • Question
AVAYA CMS R20 SLA Report 1
Replies
9
Views
927
SoftwareRT
SoftwareRT

Part and Inventory Search

Sponsor

Back
Top