If an instance of orchestration is attached to the debugger, the same
instance cannot be attached to the debugger from a different machine.
No, I was able to FTP but not FTPS when disabling the firewall. After I have
posted this message, I found an article on IIS.net which indictaes 4 steps to
follow to a special rule in the firewall in order to make the FTP server
runs/works while Firewall is activated.
http://blogs.iis.net/jaroslad/archive/2007/09/29/windows-firewall-setu...or-micr
This allowed to do FTP with Firewall activated but not FTPS. I could not
find info how to configure the ports. I tied using
C:\Users\Administrator>netstat -n -a -o -b (as indicated in the article)
When doing FTPS in Zilla, using the following parameters :
ftps://my machine
username : Administrator
password : mypassword
Port 443 (Which I czan
I get the following
*******************************************************************
Status: Selected port usually in use by a different protocol.
Status: Resolving IP-Address for 200832b
Status: Connecting to 192.168.1.8:443...
Status: Connection established, initializing TLS...
Status: Verifying certificate...
Status: TLS/SSL connection established, waiting for welcome message...
*********************************************************************
Which indicates that port 443is used by another application. It is my web.
In FTP server, I didn't see where I can configure / add a binding for ftps
protocol and associated port as in the web server.
Anyway, I changed the web server HTTPS binding to listen to port 444, it
made it worse,I get right away
*************************
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving IP-Address for 200832b
Status: Connecting to 192.168.1.8:443...
Error: Could not connect to server
************************************
According to the article, I ran
C:\Users\Administrator>netstat -n -a -o -b
and saw that FPTS is running on port 21
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING 1572
ftpsvc
[svchost.exe]
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 828
RpcSs
[svchost.exe]
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
TCP 0.0.0.0:2103 0.0.0.0:0 LISTENING 1700
[mqsvc.exe]
TCP 0.0.0.0:2105 0.0.0.0:0 LISTENING 1700
[mqsvc.exe]
TCP 0.0.0.0:2107 0.0.0.0:0 LISTENING 1700
[mqsvc.exe]
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1180
Dnscache
[svchost.exe]
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 528
[wininit.exe]
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 616
[lsass.exe]
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 892
EventLog
[svchost.exe]
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING 1008
Schedule
[svchost.exe]
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING 1700
[mqsvc.exe]
TCP 0.0.0.0:49157 0.0.0.0:0 LISTENING 604
[services.exe]
TCP 0.0.0.0:49160 0.0.0.0:0 LISTENING 2644
[msdtc.exe]
TCP 192.168.1.8:139 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
TCP 192.168.1.8:1801 0.0.0.0:0 LISTENING 1700
[mqsvc.exe]
TCP [::]:21 [::]:0 LISTENING 1572
ftpsvc
[svchost.exe]
TCP [::]:80 [::]:0 LISTENING 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
TCP [::]:135 [::]:0 LISTENING 828
RpcSs
[svchost.exe]
TCP [::]:443 [::]:0 LISTENING 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
TCP [::]:445 [::]:0 LISTENING 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
TCP [::]:2103 [::]:0 LISTENING 1700
[mqsvc.exe]
TCP [::]:2105 [::]:0 LISTENING 1700
[mqsvc.exe]
TCP [::]:2107 [::]:0 LISTENING 1700
[mqsvc.exe]
TCP [::]:3389 [::]:0 LISTENING 1180
Dnscache
[svchost.exe]
TCP [::]:5357 [::]:0 LISTENING 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
TCP [::]:49152 [::]:0 LISTENING 528
[wininit.exe]
TCP [::]:49153 [::]:0 LISTENING 616
[lsass.exe]
TCP [::]:49154 [::]:0 LISTENING 892
EventLog
[svchost.exe]
TCP [::]:49155 [::]:0 LISTENING 1008
Schedule
[svchost.exe]
TCP [::]:49156 [::]:0 LISTENING 1700
[mqsvc.exe]
TCP [::]:49157 [::]:0 LISTENING 604
[services.exe]
TCP [::]:49160 [::]:0 LISTENING 2644
[msdtc.exe]
TCP [fe80::3189:2d10:c122:ac38%10]:1801 [::]:0
LISTENING 1700
[mqsvc.exe]
UDP 0.0.0.0:123 *:* 1096
W32Time
[svchost.exe]
UDP 0.0.0.0:500 *:* 1008
IKEEXT
[svchost.exe]
UDP 0.0.0.0:3702 *:* 1096
FDResPub
[svchost.exe]
UDP 0.0.0.0:3702 *:* 1096
FDResPub
[svchost.exe]
UDP 0.0.0.0:4500 *:* 1008
IKEEXT
[svchost.exe]
UDP 0.0.0.0:5355 *:* 1180
Dnscache
[svchost.exe]
UDP 0.0.0.0:49156 *:* 1096
FDResPub
[svchost.exe]
UDP 127.0.0.1:49184 *:* 3644
[iexplore.exe]
UDP 192.168.1.8:137 *:* 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
UDP 192.168.1.8:138 *:* 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
UDP [::]:123 *:* 1096
W32Time
[svchost.exe]
UDP [::]:500 *:* 1008
IKEEXT
[svchost.exe]
UDP [::]:3702 *:* 1096
FDResPub
[svchost.exe]
UDP [::]:3702 *:* 1096
FDResPub
[svchost.exe]
UDP [::]:5355 *:* 1180
Dnscache
[svchost.exe]
UDP [::]:49157 *:* 1096
FDResPub
[svchost.exe]
"SalamElias" wrote:
> Thanks Wen, asI said in my 2nd post, both server and laptop are behind the
> firewall that connects to Internet, they are on the same Lan (192.168.1.*). I
> can FTP another w2k3 server.
> I reverted back and configured a normal ftp site, I used FileZilla for both
> FTP and FTPS, then I swithced to my old commande line, did
> > FTP myserver
> after a while I get "unkown error has happened", on the server I can not
> find any trrace.
> regarding the w2k8, I turned the firewall of.
>
> ""WenJun Zhang[msft]"" wrote:
>
> > Hi Salarm,
> >
> > Which FTP client are you using on the laptop to connect the FTPS site? Most
> > of common FTP clients cannot support FTPS connection. Also, have you
> > verified firewall setting on the server?
> >
> > Happy holidays.
> >
> > Sincerely,
> >
> > WenJun Zhang
> >
> > Microsoft Online Community Support
> >
> > ==================================================
> >
> > Get notification to my posts through email? Please refer to:
> > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> > ications.
> >
> > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> > where an initial response from the community or a Microsoft Support
> > Engineer within 1 business day is acceptable. Please note that each follow
> > up response may take approximately 2 business days as the support
> > professional working with you may need further investigation to reach the
> > most efficient resolution. The offering is not appropriate for situations
> > that require urgent, real-time or phone-based interactions or complex
> > project analysis and dump analysis issues. Issues of this nature are best
> > handled working with a dedicated Microsoft Support Engineer by contacting
> > Microsoft Customer Support Services (CSS) at:
> >
> > http://msdn.microsoft.com/subscriptions/support/default.aspx.
> >
> > ==================================================
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > >> Stay informed about: IIS 7 FTP