Claude1864: Thats good to know thank you. I didnt even think to restart the comp. much appreciated
nipsen: It has no effect, even if the connection issues were local. You don't rely on listening to incoming requests, the program just polls a portal/gateway and receives new addresses that you will use for a while. Some then become unavailable, and you switch.
And Windows doesn't automatically flush dns-cache on reboot, things like that. So if the connection issues come from RSPs bouncing you to unresolved server locations (instead of just being unavailable or overpopulated), you just need to wait until your dns-server is current (or there are free slots - that someone else got booted). Rebooting in that case has the same effect of waiting 30-40 seconds and trying again.
But since this kind of stuff is essentially what occupies an entire industry of customer service folks, I suppose I shouldn't be mean about it. Surely telling people to spin around on their office chair three times while spilling salt behind their backs to fix problems would be much more fun - but who am I to judge what people do to waste other people's time.
I can wait all day when it's not connected, it's still not going to connect. The post I read said it was coded into the game that once you log off that's it, it's not going to reset until the computer is rebooted. That seems to be the case, I can go for hours, and did, and it will never have a connection when I fire up the game. On the other hand, if I reboot, there it is, connected. So I'll go with what works. Sorry if doesn't fit your theory, I like results.