Any Known Issues with Windows Server 2003 SP2? (General questions)
by Howie, Wednesday, May 23, 2007, 16:46 (6394 days ago)
Recently my projects with SFTP .NET component have started failing. I can run from my develpoment PC with XP Pro and VS 2005 and SFTP installed, but when I deploy up to the server, it fails to connect to the remote server.
Is this happening to anyone else?
I suspect a windows update may have changed something on the server?
Any ideas are appreciated.
Thanks
Re: Any Known Issues with Windows Server 2003 SP2?
by wodSupport, Wednesday, May 23, 2007, 17:01 (6394 days ago) @ Howie
Howie,
do you get any errors? At least 'timeout' should return..
Kreso
Re: Any Known Issues with Windows Server 2003 SP2?
by Howie, Wednesday, May 23, 2007, 17:05 (6394 days ago) @ wodSupport
Thats EXACTLY the error I get...
A timeout error on the Connect command.
Re: Any Known Issues with Windows Server 2003 SP2?
by wodSupport, Wednesday, May 23, 2007, 17:07 (6394 days ago) @ Howie
Does it perhaps run as windows service? If so, can you disable server's firewall, for a test?
Kreso
Re: Any Known Issues with Windows Server 2003 SP2?
by Howie, Wednesday, May 23, 2007, 17:40 (6394 days ago) @ wodSupport
Does it perhaps run as windows service? If so, can you disable server's firewall, for a test?
Kreso
No, its not running as a service.
Windows Firewall is not running on the server, or did you mean our hardware firewall?
Either way, I cannot disable for testing purposes.
This has been running for many many months without a problem, I dont understand why there is a problem now.
Thanks Kreso
Re: Any Known Issues with Windows Server 2003 SP2?
by woddrazen, Wednesday, May 23, 2007, 17:59 (6394 days ago) @ Howie
Hi Howie,
Did you try to connect to that server with some other SFTP client like winSCP for example? What happened? Maybe it's firewall issue and wodSFTP.NET can't connect.
Some customer have a problem with PrivateKey Authnetication and wodKeysManager.NET component which is part of wodSFTP.NET component and missing MSVCR71.DLL .
MSVCR71.DLL file is part of NET 1.1 framework and problem is fixed when that file is copied to Windows System32 folder.
Let us know how it goes.
Regards,
Drazen
Re: Any Known Issues with Windows Server 2003 SP2?
by Howie, Wednesday, May 23, 2007, 19:20 (6394 days ago) @ woddrazen
Hi Howie,
Did you try to connect to that server with some other SFTP client like winSCP for example? What happened? Maybe it's firewall issue and wodSFTP.NET can't connect.Some customer have a problem with PrivateKey Authnetication and wodKeysManager.NET component which is part of wodSFTP.NET component and missing MSVCR71.DLL .
MSVCR71.DLL file is part of NET 1.1 framework and problem is fixed when that file is copied to Windows System32 folder.Let us know how it goes.
Regards,
Drazen
I checked the MSVCR71.DLL file and it exists in the System32 folder on the server. I havent tried connecting to the remote server from a third party client from my server.
I could copy psftp.exe up to that server and try??
Remember, it works fine from my PC behind the same firewall.
Thanks.
Re: Any Known Issues with Windows Server 2003 SP2?
by woddrazen, Wednesday, May 23, 2007, 19:25 (6394 days ago) @ Howie
Howie,
Please try with some other SFTP client so we can be sure that this isn't firewall problem.
Drazen
Re: Any Known Issues with Windows Server 2003 SP2?
by Howie, Wednesday, May 23, 2007, 19:38 (6394 days ago) @ woddrazen
Howie,
Please try with some other SFTP client so we can be sure that this isn't firewall problem.
Drazen
Drazen,
It works from my server with PSFTP.EXE...
Also, this is the message from my .NET application:
Server Error in '/d000300m' Application.
--------------------------------------------------------------------------------
Timeout occured due to inactivity
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: WeOnlyDo.Exceptions.SFTP.TimeoutException: Timeout occured due to inactivity
Source Error:
Line 422: sftp1.Password = xxxxx
Line 423: sftp1.Blocking = *True
Line 424: sftp1.Connect()
Line 425: sftp1.PutFile(filename, remotename)
Line 426: sftp1.Disconnect()
Source File: C:Inetpubwwwrootd000300mProcess.aspx.vr Line: 424
Stack Trace:
[TimeoutException: Timeout occured due to inactivity]
..() +1797
WeOnlyDo.Client.SFTP.Connect() +12
Process.btnConfirm_Click(Object sender, EventArgs e) in C:Inetpubwwwrootd000300mProcess.aspx.vr:424
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +105
System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +107
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210
[color=#abcdef]Text[/color]
Re: Any Known Issues with Windows Server 2003 SP2?
by wodSupport, Wednesday, May 23, 2007, 20:06 (6394 days ago) @ Howie
Howie,
there is one more thing that could be important.. IPV6. Do you specify Hostname or IP address? If you specified hostname and IPV6 address resolves, it will use it - perhaps that's why it fails?
Besides that, if you tried with PSFTP under same account with same environment and PSFTP worked - wodSFTP must work too..
Kreso
Re: Any Known Issues with Windows Server 2003 SP2?
by wodSupport, Wednesday, May 23, 2007, 20:08 (6394 days ago) @ wodSupport
Howie,
this isn't ASP application, right? This is desktop app?
Kreso
Re: Any Known Issues with Windows Server 2003 SP2?
by Howie, Wednesday, May 23, 2007, 20:10 (6394 days ago) @ wodSupport
ASP application.
.NET 2.0 framework
Re: Any Known Issues with Windows Server 2003 SP2?
by wodSupport, Wednesday, May 23, 2007, 20:16 (6394 days ago) @ Howie
ASP? Same rules as service app. Going back to reply #1 :) Please disable Windows firewall on that computer and try again.
PSFTP worked because you run it as regular user.
ASP doesnt' work since it runs as IUSR_GUEST and firewall doesn't let him out. Go to network card properties and disarm the firewall - that is 100 the reason. We had this issue before.
Hope this helps!
Kreso
Re: Any Known Issues with Windows Server 2003 SP2?
by Howie, Wednesday, May 23, 2007, 20:23 (6394 days ago) @ wodSupport
ASP? Same rules as service app. Going back to reply #1 :) Please disable Windows firewall on that computer and try again.
PSFTP worked because you run it as regular user.
ASP doesnt' work since it runs as IUSR_GUEST and firewall doesn't let him out. Go to network card properties and disarm the firewall - that is 100 the reason. We had this issue before.
Hope this helps!
Kreso
Sorry Kreso, I am missing something.
First, this project has been working fine for a long time. It has only been in the past couple of weeks there has been this issue.
Next, as I stated above, Windows firewall is NOT running.
I do not understand the timing of this issue. Why now I am wondering. Thats why I was looking for something to have changed.
The only automatic thing would be Windows Updates...
The timing might have been when we updated to SP2...
Thanks
This is the LOG file from the attempt:
Connect::start
Connect::BeginConnect
Connect:end
MethodNotification:start
MethodNotification:ExtendedStates.Connecting
MyTimerCallback:start
DestroySocket
Re: Any Known Issues with Windows Server 2003 SP2?
by wodSupport, Wednesday, May 23, 2007, 20:26 (6394 days ago) @ Howie
Howie,
I'm 99.99 sure it's something to do with IUSR_GUEST being unable to leave your computer.
I think this was introduced with XP2..
If you somehow can run PSFTP with those privileges, it will fail too.
Kreso
Re: Any Known Issues with Windows Server 2003 SP2?
by Howie, Wednesday, May 23, 2007, 20:28 (6394 days ago) @ wodSupport
Kreso,
Ok, I will pursue that and see what I can find.
I will let you know.
Thanks again!
Howie
Re: Any Known Issues with Windows Server 2003 SP2?
by Howie, Thursday, May 24, 2007, 22:29 (6392 days ago) @ Howie
No luck yet.
It does seem to be a server setting, but I havent found it yet.
Re: Any Known Issues with Windows Server 2003 SP2?
by wodDamir, Thursday, May 24, 2007, 23:10 (6392 days ago) @ Howie
Howie,
I don't have the answer. But since it worked, and stopped for no reason, you should try figuring out when it stopped.
Then maybe you could check for the software which was installed or maybe settings that changed. Or perhaps you could try it on a third computer running the same operating system?
Regards,
Damba
Re: Any Known Issues with Windows Server 2003 SP2?
by Howie, Friday, May 25, 2007, 14:06 (6392 days ago) @ wodDamir
Howie,
I don't have the answer. But since it worked, and stopped for no reason, you should try figuring out when it stopped.
Then maybe you could check for the software which was installed or maybe settings that changed. Or perhaps you could try it on a third computer running the same operating system?
Regards,
Damba
Well nearest I can tell it was the update to SP2. I am not a Windows Server 2003 expert, so its really hit and miss for me.
Thanks.
Re: Any Known Issues with Windows Server 2003 SP2?
by wodDamir, Friday, May 25, 2007, 16:29 (6392 days ago) @ Howie
Howie,
I'm not really familiar with Windows Server 2003 either. But from queries we had on other issues, this does look like what Kreso suggested (lack of access).
Can you try any other ASP.Net application? Can that app get outside of your network?
Could you also try the steps of configurating the web server from the following link: http://support.microsoft.com/kb/324742
Hope this helps.
Regards,
Damba
Re: Any Known Issues with Windows Server 2003 SP2?
by Howie, Friday, May 25, 2007, 16:34 (6392 days ago) @ wodDamir
Howie,
I'm not really familiar with Windows Server 2003 either. But from queries we had on other issues, this does look like what Kreso suggested (lack of access).
Can you try any other ASP.Net application? Can that app get outside of your network?
Could you also try the steps of configurating the web server from the following link: http://support.microsoft.com/kb/324742
Hope this helps.
Unfortunately no, this is the only application that needs access outside of our intranet. AND, it is the only application that uses a 3rd party library. So it is kind of unique.
I will follow that thread and see if it gives me any ideas.
Thanks.
Regards,
Damba
