PS3 error 80710092

[Y3k Bug]

Sorry, this turned into a long post:

Okay guys, I'm looking for some help. For the past 3 days I have been unable to connect to the Playstation Network on my PS3. When attempting to sign in, it always returns the error 80710092.

I have tried everything I know to correct the problem and have run out of ideas. If any of you know what's wrong and/or how to fix it, please let me know!

First some useful information:
My PS3 is on a wired connection to a router w/ built-in firewall. This in turn is connected to my cable modem which is in turn connected to the cable outlet. I am able to use the browser on the PS3 to view webpages and I am able to up/download packets for folding@home. I have been able in the past to log in to the PSN without any trouble. On all of the failed attempts, I did check the Playstation website to make sure the network showed as being up.

What I've already attempted:
First I checked to see if I had connectivity by checking the browser and folding@home. That worked...

Next I went into Network setup on my PS3 to reset all the settings. Using the auto-configure option, it would obtain an IP address, but could not connect to the server (the second check). Hmm, strange...

My next thought was perhaps my router decided to block something (or was maybe crapping out), so I hooked up my PS3 directly to my cable modem and power-cycled it a few times. Ran the setup again and still received the error.

After that I went to the Playstation website and ran a search for that error on the forums. I got a few returns (it seems a few people have had the problem starting in August) but found no concrete resolutions.

Contacted Playstation support and just received an email detailing the ports used and requesting that I make sure my firewall is allowing them to be used. Since I've already eliminated that possibility I'll have to give them a call Saturday to try and get it fixed if it's not working by then.



So, is there anything else you guys can think of that I should try? Perhaps one of you has run into the same problem and figured out how to fix it already?