Unable to connect to IP Address (General questions)
by Ogedei, Friday, August 31, 2007, 23:35 (6293 days ago)
I have recently switched from the COM to the .NET version of DLX.
A site I was able to connect to in COM can not be reached in .NET
I get a An existing connection was forcibly closed by the remote host message when I try and connect.
I am using the Simple.VB sample and I am getting the same results.
I can not provide you access to the site it is HIPAA protected but here is the IP
oFTP.Blocking = True
oFTP.Hostname = 68.72.52.204
oFTP.LocalPath = procedure.LocalDir
oFTP.Login = FTP.UserName
oFTP.Passive = FTP.Passive
oFTP.Password = FTP.Password
oFTP.Port = FTP.Port
'oFTP.Protocol = CType(CType(FTP.Protocol, wodFtpDLXComLib.ProtocolsEnum), WeOnlyDo.Client.Protocols)
oFTP.Protocol = CType(FTP.Protocol, WeOnlyDo.Client.Protocols)
'WeOnlyDo.Client.Protocols.
oFTP.RemotePath = procedure.RemoteDir
oFTP.Timeout = FTP.TimeOut
If oFTP.State = WeOnlyDo.Client.States.Disconnected Then
oFTP.Connect()
End If
Please assist. thanks
Re: Unable to connect to IP Address
by Ogedei, Friday, August 31, 2007, 23:40 (6293 days ago) @ Ogedei
FileZilla and IE FTp connections work fine but no luck with DLX.
Re: Unable to connect to IP Address
by woddrazen, Friday, August 31, 2007, 23:54 (6293 days ago) @ Ogedei
Hi Brian,
We have recently fix some issue with WS FTP server. Can you please re download wodFtpDLX.NET from our website and reinstall it.
If problem persist which protocol you are using?
Let us know how it goes.
Regards,
Drazen
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 00:22 (6293 days ago) @ woddrazen
downloaded version 1.2.2.87 on 8/27/07 and uninstalled and reinstalled and no luck.
This is FTP and I have another site with FTPSWithDAta and it gives me a can not get certificate.
thanks
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 01:08 (6293 days ago) @ Ogedei
OK the new file worked thanks a bunch
but I am now stuck on a FTPSWithData
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
My timeout is 120.
Do i need to do anythign specila to accept the certificate?
Re: Unable to connect to IP Address
by wodSupport, Saturday, September 01, 2007, 01:16 (6293 days ago) @ Ogedei
I'm not sure why do you think connection failed because party didn't respond..... error is related to certificate? Can you explain?
Kreso
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 01:17 (6293 days ago) @ wodSupport
same error is ocurring with your sample files.
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 01:19 (6293 days ago) @ Ogedei
Not really earlier i got a certifiacte error, with same site.
Now I do not know why I can not connect to a site i USed to be able to connect to with the com object.
Re: Unable to connect to IP Address
by wodSupport, Saturday, September 01, 2007, 01:30 (6293 days ago) @ Ogedei
Are you running your app as a service? or from ASP page?
Kreso
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 01:32 (6293 days ago) @ wodSupport
Service
and why can I not compile your sample app and run it on a different machine?
Re: Unable to connect to IP Address
by wodSupport, Saturday, September 01, 2007, 01:34 (6293 days ago) @ Ogedei
Service? In that case it's local firewall issue. Please disable firewall on your local network adapters.
As for running sample on another PC, did you set LicenseKey property?
Kreso
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 01:38 (6293 days ago) @ wodSupport
i do not like that answer one bit.
why did it work as a com component and now I need to diable firewalls.
Please advise.
This is friday at 5:30 and it is a 3 day weekend and I need this fixed. can we go to voice?
Re: Unable to connect to IP Address
by wodSupport, Saturday, September 01, 2007, 01:40 (6293 days ago) @ Ogedei
Did you run it as service before too?
Kreso
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 01:41 (6293 days ago) @ wodSupport
yes all that changed was the upgrade from your com component to your .NET component
Re: Unable to connect to IP Address
by wodSupport, Saturday, September 01, 2007, 01:43 (6293 days ago) @ Ogedei
Please disable the firewall. If then it starts to work you can tweak firewall. We've seen this before.
Service runs with different privileges, and windows firewall tries to be smart and drops local packets.
That's why you receive 'timeout error'. If things are right you would either receive connection refused or success - but not timeout like noone's there.
So, please, disable the firewall and try again.
Unfortunatelly, as explained at
http://www.weonlydo.com/index.asp?support=1
we do not provide phone support. But I am sure we can handle it here.
Kreso
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 01:47 (6293 days ago) @ wodSupport
NIC firewall is not on
Service runs under a domina administrator account
Re: Unable to connect to IP Address
by wodSupport, Saturday, September 01, 2007, 01:50 (6293 days ago) @ Ogedei
Control panel / Windows firewall is off? Then some other firewall is running.
If application does run as desktop app but doesn't when running as service, but gets timeout error instead, this is firewall issue. Please double-check firewall settings.
Kreso
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 01:56 (6293 days ago) @ wodSupport
Firewall is not on
I can not get your sample exe to run on desktop so I know nothing else
I get a cant find component from the exe sample1
Re: Unable to connect to IP Address
by wodSupport, Saturday, September 01, 2007, 01:59 (6293 days ago) @ Ogedei
I'm not sure I'm following you.
Your app that runs as a service and uses our component works with the timeout error.
But at the same time you cannot run our samples because you can't find the DLL? Only thing I can suggest is that you search for WeOnlyDo.Client.FTP.dll on your disk and copy it to same folder where EXE resides.
Depending on your OS, it is in Application Data\WeOnlyDo\Assembly or in Program Files\WeOnlydo\Assembly so that's place to start search for.
Kreso
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 02:04 (6293 days ago) @ wodSupport
yes trying to run the sample apps on the same machine as the service I get the following error
System.IO.FileNotFoundException: Could not load file or assembly 'WeOnlyDo.Client.FTP, Version=1.2.2.89, Culture=neutral, PublicKeyToken=e066bfc6dc58a05b' or one of its dependencies. The system cannot find the file specified.
File name: 'WeOnlyDo.Client.FTP, Version=1.2.2.89, Culture=neutral, PublicKeyToken=e066bfc6dc58a05b'
at SimpleVB.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLMSoftwareMicrosoftFusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLMSoftwareMicrosoftFusion!EnableLog].
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
SimpleVB
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Documents 20and 20Settings/All 20Users/Desktop/SimpleVB.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging= true />
</configurati
Re: Unable to connect to IP Address
by wodSupport, Saturday, September 01, 2007, 02:11 (6293 days ago) @ Ogedei
So you searched hard disk and copied it to same folder as EXE and got that error, like I suggested in previous post?
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 02:13 (6293 days ago) @ wodSupport
yes I did and now I am rebooting the server, if still not work and I verify version is right I will uninstall and reinstall
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 02:18 (6293 days ago) @ Ogedei
tried repair nothing
tried uninstall nothing
have dll in GAC
have dll in folder with exe
i get nothing but can not find dll
going to try a new compile
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 02:35 (6293 days ago) @ Ogedei
got exe to work finally
trying connection from server
get these messages
STATECHANGE to Connecting to server (from Disconnected from server)
STATECHANGE to Initializing secure connection (from Connecting to server)
STATECHANGE to Setting data channel security (from Initializing secure connection)
and I wait does not seem to matter if I am blocking or not
Re: Unable to connect to IP Address
by Ogedei, Saturday, September 01, 2007, 02:54 (6293 days ago) @ Ogedei
when I connect to this site with filezilla it asks me to accept the certificate.
How does DLX handle the accept certificate issue?
