Strange network behavior

[lancherider]

I'm running Steam on OS X 10.8.3 and am seeing some strange networking issues. Namely, I get the "Could not connect to Steam network, bla bla bla" error message. When I run a packet capture, it looks like the Steam client is trying to connect through my home router, even though I am not on my home network. This is not an OS setting, because no other application is exhibiting this kind of behavior. I have run day-long packet captures and done everything my Mac is capable of doing, and the only time I see my home router's address is when I attempt to use the Steam client. I have removed the application, deleted ~/Library/Application Support/Steam completely and reinstalled the Steam client, but to no avail. Anyone have any ideas where else I might look for a hardcoded router address that Steam is using? Please and thank you!

[cbird1057]

Thanks for posting this, because it helped me to figure out how to restore my account. I ended up with the "Could not connect to Steam network, bla bla bla" for no reason, and since Steam support takes weeks to respond I started troubleshooting on my own.

You mentioned network packets. When I saw that, I thought to myself "Maybe Steam is looking for a specific IP address and then losing it". So I logged on through a VPN network which uses a totally different IP and when I opened Steam it presented the terms and conditions as though I were logging in for the first time.

I was able to change my email address and everything from that one screen, which explains why Steam might have some security issues. I was logging in through an IP address it had never seen before, and the intro screen included the capability to change the email address directly.

One would think there should be a couple of security questions like "favorite pet" or whatever before email address can be changed. No wonder Steam support is so overloaded.

[Gotta Go Relatively Quickly]

Mac's are just too finicky :x

[lancherider]

I'm going to try again tomorrow, but I just logged in from my home network again and it sent me a new verification code for my Mac, so hopefully it'll be fixed.