wouldn't you know it... I haven't logged onto kgs for what seems like weeks (it may actually have been weeks), and I logon right into the middle of a maintenance activity that appears to have been going on for a couple of hours now.

Thanks, UM. The "normal" Host is goserver.gokgs.com

Yes, thanks for reminding me, Ed.

Once the DNS pools are updated, the users should set the host back to goserver.gokgs.com

Man, I wish I'd thought to come and look here first - I'm re-installing Java for the third time at the moment, thinking something's wrong with my machine!

Ever since the server was moved, I keep lagging and can barely do anything. Before the move I had no problems.

There has now been more than enough time for DNS servers to have been updated. You should set the host back to goserver.gokgs.com. Those of you who are having trouble connecting should try clearing your DNS cache. One help page is at http://www.techiecorner.com/35/how-to-flush-dns-cache-in-linux-windows-mac. If that does not work, please contact your ISP.

I always hate giving advice to key in the IP address. It *always* makes problems later. As we speak, 5 days after we switched servers and 4 days after the last stale DNS entry was cleared, there are still 10 people going through the old IP address. There are all people who thought they were fixing a problem by keying in the IP address of the old location. When I tell the ISP to shut down the old server (and that time is coming very soon), then these people will be cut off.

I *ALWAYS* set up port forwarders. It is *NEVER* necessary to key in the IP address of the KGS server.

Really, I should just take that entry out of the config GUI.

If you mean the entire 'host' option, I'd like to note that it's sometimes very useful to change it. For me and some people I know in particular, the only way to access KGS when in a university hall of residence was to use a proxy at a different address and port.

Without the option to change it, I'm not sure it would have been possible to use KGS at all!

Please don't remove it entirely. I need it for ssh tunneling.

Sigh. Right, I added it for exactly that, tunnelling etc. But every time I switch servers I find people who used it to change "goserver.gokgs.com" into a hardcoded IP address, then they forget and can't figure out why their client breaks when the server moves. No perfect solution I guess.

How about using the default address/port as fallback if the first doesn't work?

_________________
Sanity is for the weak.

I could do that, but I should add a GUI; "You can't connect to blah blah blah, do you want to try the default of goserver.gokgs.com:2379?". Not sure if I'll get around to it or not...

I would have thought anyone savvy enough to figure out ssh tunnelling would be likely to guess why their client is failing to connect.

The people using ssh tunnels and the people wms refers to are probably different groups, but action to help the latter would potentially harm the experience of the former.

Well, yes, you should. But isn't making it try the default server by itself better than doing nothing, and therefore better than waiting until you make the gui control?

Just trying to save you some work.

_________________
Occupy Babel!