Home
»
Discussion Forums
»
Kserver Discussions - VSA
»
Web interface repeatedly returns to login screen
Subscribe via RSS
Share this
Similar Posts
Kaseya Web Interface Ticket Logging
by
d2000_07
on
Aug 5, 2016
Login slow, and interface generally slow
by
Appleoddity
on
Feb 22, 2011
KES 2.0 breaks Citrix Server Web Interface
by
LegacyPoster
on
Jan 7, 2009
Web Services API returns strange results
by
mikeelindsay
on
Dec 30, 2016
Not Answered
YOUR Techs running Kaseya Web Interface in Citrix. VNC Issues...
by
far182
on
Nov 29, 2010
View More
Details
7
Replies
0
Subscribers
Posted
over 13 years ago
Kserver Discussions - VSA
Web interface repeatedly returns to login screen
Posted by
LegacyPoster
on
May 10, 2007 6:44 AM
For some reason when selecting any function or page, the program randomly stops for a couple of seconds, then 'gives up' and returns me to the inital login screen. What can be done to stop this, as it is very annoying when it happens several times in a row before succeeding?
Edit:
Now it's randomly saying"
Cookies are required for login.
Enable cookies then refresh this page before proceeding. "
If I ignore this and log in anyway it lets me in. And yes, cookies are enabled.
Legacy Forum Name: Web interface repeatedly returns to login screen,
Legacy Posted By Username: plenfestey
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
Posted by
LegacyPoster
on
May 4, 2007 12:11 PM
This problem only seems to happen on remote pc's, ie not if connecting to 'localhost' on the Kaseya server.
Legacy Forum Name: Server,
Legacy Posted By Username: plenfestey
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
Posted by
LegacyPoster
on
May 4, 2007 3:27 PM
Did this just start happening?
DNS problems resolving your KServer's name from outside the network?
Just throwing out ideas as to what it could be.
Legacy Forum Name: Server,
Legacy Posted By Username: vplaza
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
Posted by
LegacyPoster
on
May 8, 2007 6:44 AM
Well I think it's only just started happening, we've only just started using Kaseya so can't really tell. It was a bit misleading saying it only happens on remote pc's, by that I mean other pc's on the LAN, not from outside. Our external dns is working correctly, but that's made me look at our internal dns, which is probably where my problem lies. For some reason whoever set up our network chose not to implement a dns server inside, so our dns settings point to outside! Duh, no wonder it doesn't work!
Legacy Forum Name: Server,
Legacy Posted By Username: plenfestey
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
Posted by
LegacyPoster
on
May 8, 2007 2:19 PM
Hmm, I put my internal Kserver IP address in HOSTS to remove the dns problem, and it's been fine all morning but now its started doing it again.
Legacy Forum Name: Server,
Legacy Posted By Username: plenfestey
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
Posted by
LegacyPoster
on
May 8, 2007 3:03 PM
Hmm, it still sounds like a DNS issue. Or, it could be a routing issue if you are using different subnets?
Legacy Forum Name: Server,
Legacy Posted By Username: vplaza
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
Posted by
LegacyPoster
on
May 10, 2007 6:43 AM
We've not got different subnets, but I'm starting to agree, DNS is the most likely culprit. Once I can persuade them here to fix the rubbish way our network is set up I'll see what happens then. Our internal network is 193.195.3.0 - an external range!
Legacy Forum Name: Server,
Legacy Posted By Username: plenfestey
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
Posted by
LegacyPoster
on
May 10, 2007 6:44 AM
We've not got different subnets, but I'm starting to agree, DNS is the most likely culprit. Once I can persuade them here to fix the rubbish way our network is set up I'll see what happens then. Our internal network is 193.195.3.0 - an external range!
Legacy Forum Name: Server,
Legacy Posted By Username: plenfestey
You have posted to a forum that requires a moderator to approve posts before they are publicly available.