Database timeouts

Hi, I have an SQL database on my home laptop which my website connects to remotely, this has been working great for about a week now until last night when from nowhere everything seems to have stopped working (including weirdly, now I can also only FTP via active mode whereas before yesterday I had no trouble connecting passively). I feel like this must have something to do with a firewall on the server side?

Just to provide you with the info on my set-up:
I am conneting through port 1433, I have the windows firewall and McAfee turned off now (although I have set McAfee to allow 1433,1434 anyway and like I say this was previously working...but anyway they're off completley at the moment). I have also enabled port forwarding on these ports through my router itself. SQL Express is set to listen on 1433, and the logs are showing :
2009-02-01 13:46:27.63 Server Server is listening on [ 'any' <ipv6> 1433].
2009-02-01 13:46:27.63 Server Server is listening on [ 'any' <ipv4> 1433].
as I believe they should.
I have also set SQL Express to allow Remote TCP/IP, named pipes connections, and SQL Express is set to mixed authentication mode. I have logged in successfully through SQL Management studio with the user/pass that I'm using in my connection string, and I can see the database/tables I require, and have read/write permission on them.

Like I say, all this was working great for about a week, until out of nowhere it suddenly stops and all I get is "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) "

I feel like this must be a firewall issue, especially with the coincidence of FTP passive mode stopping working at the same time?

Would really appreciate some help as my website has been down for nearly 24 hours now, if you need any more info then please don't hesitate to ask.

Thanks alot

 

Are you on a server at the UK data center? There was a problem the other night but it should be remedied now. Some work-arounds that we had to perform required FTP via active mode temporarily. But as of yesterday at 2 p.m. Pacific time everything should be back to normal.