First time I go online for several months, with a new computer, and I get the dreaded "waiting for guest info" followed by "did not receive guest info. Lost connection to host".
LFS is allowed in both directions by my software firewall.
I've rebooted the router.
It's a fresh, full download of LFS S2Y.
On the rare occasion I can connect, pings are good. I don't appear to have a problem with latency or dropped packets on my internet connection. Nothing else I've used my connection for has so much as hiccuped.
Curious things:
- Clicking "back" on the multiplayer screen (going from the screen with options to set skin downloads and browse servserlist or join specific host, going to the LFS main menu) produces a noticeable delay. I don't remember it being like this in the past.
- Going back to the main menu and then back into multiplayer seems to increase the chances of being able to connect.
- Empty servers are easier to connect to than populated servers.
Any ideas? It's driving me up the wall, and given my previous history with a perfectly good connection and no other system issues, it's looking like an LFS-specific issue.
LFS is allowed in both directions by my software firewall.
I've rebooted the router.
It's a fresh, full download of LFS S2Y.
On the rare occasion I can connect, pings are good. I don't appear to have a problem with latency or dropped packets on my internet connection. Nothing else I've used my connection for has so much as hiccuped.
Curious things:
- Clicking "back" on the multiplayer screen (going from the screen with options to set skin downloads and browse servserlist or join specific host, going to the LFS main menu) produces a noticeable delay. I don't remember it being like this in the past.
- Going back to the main menu and then back into multiplayer seems to increase the chances of being able to connect.
- Empty servers are easier to connect to than populated servers.
Any ideas? It's driving me up the wall, and given my previous history with a perfectly good connection and no other system issues, it's looking like an LFS-specific issue.