Answered by:
Connection to server was reset -- downloading small files remotely (already changed timeout)

Question
-
I recently ran a repair on my system to change my sys drive to a larger/newer model (300gb -> 500gb)
I had to make a few modifications to get everything to run smoothly afterwards as far as remote access is concerned.
First problem i had was the error that requires switching IIS .net properties from 1.1 to 2.0 to even be able to access the remote web site.
Now that i am able to access, if i download anything for more than 30 seconds i get a "connection to server was reset" message
I changed the session timeout globally to 240min, but i'm unsure as to what else can cause this problem.
If someone can point me to another post or has info on troubleshooting steps that'd be greatly appreciated.
thanks
computer guyThursday, January 14, 2010 7:08 PM
Answers
-
Try a server reinstallation to get your remote access web site working again.
I'm not on the WHS team, I just post a lot. :)- Marked as answer by Jonas Svensson -FST- Tuesday, February 9, 2010 1:07 AM
Thursday, January 14, 2010 8:39 PMModerator -
Yes. Based on your description of your issues, it may not have completed, or there may have been some problem during the process that resulted in your current situation.
I'm not on the WHS team, I just post a lot. :)- Marked as answer by Jonas Svensson -FST- Tuesday, February 9, 2010 1:07 AM
Thursday, January 14, 2010 9:31 PMModerator
All replies
-
FWIW, I also had to delete my web.config file in the remote folder to get homeserver.com/remote page for it to stop giving me a runtime error...
it recreated the web.config on its own, but now it says "your session has timed out" when i get to the login screen regardless of whether i had ever actually logged on.
computer guyThursday, January 14, 2010 8:37 PM -
Try a server reinstallation to get your remote access web site working again.
I'm not on the WHS team, I just post a lot. :)- Marked as answer by Jonas Svensson -FST- Tuesday, February 9, 2010 1:07 AM
Thursday, January 14, 2010 8:39 PMModerator -
the re-installation was what caused this problem in the first place...but you suggest i do it again?
computer guyThursday, January 14, 2010 9:10 PM -
Yes. Based on your description of your issues, it may not have completed, or there may have been some problem during the process that resulted in your current situation.
I'm not on the WHS team, I just post a lot. :)- Marked as answer by Jonas Svensson -FST- Tuesday, February 9, 2010 1:07 AM
Thursday, January 14, 2010 9:31 PMModerator