Results 1 to 7 of 7
Hi all,
When I give the command:
winexe --interactive 0 --user <user>%<password> //<ip_address> 'cmd /C dir'
I receive the message:
ERROR: Cannot open control pipe - NT_STATUS_ACCESS_DENIED
The source machine ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 12-02-2010 #1Just Joined!
- Join Date
- Dec 2010
- Posts
- 5
winexe
Hi all,
When I give the command:
winexe --interactive 0 --user <user>%<password> //<ip_address> 'cmd /C dir'
I receive the message:
ERROR: Cannot open control pipe - NT_STATUS_ACCESS_DENIED
The source machine is a RedHat EL4 server.
The target machine is a Windows XP Home SP3 pc.
Note: when I give the same command to another pc all works fine. The other pc is a Windows XP Prof SP3.
Thanks in advance.
- 12-02-2010 #2Linux Enthusiast
- Join Date
- Apr 2004
- Location
- UK
- Posts
- 678
Hi there,
Just a shot in the dark, but is the XP home user set up with no password? IIRC XP home disables remote access unless a password is set. SMB File sharing and printer sharing would be affected, and trying to access a share on the home box from the professional box would encounter the same problem.
Let us know how you get on.To be good, you must first be bad. "Newbie" is a rank, not a slight.
- 12-02-2010 #3Just Joined!
- Join Date
- Dec 2010
- Posts
- 5
Hi,
User in XP Home has password set, as the XP Prof. The two PCs have same users with same passwords.
I have defined a shared directory on each PCs, with same name and permissions.
When I use smbclient I can see the content of a share directory in both PCs.
But, if I try to use winexe on WXP Prof all it's ok, when I use winexe on WXP Home no.
I've also defined winexesvc service running on each PCs.
Thanks.
- 12-02-2010 #4Linux Enthusiast
- Join Date
- Apr 2004
- Location
- UK
- Posts
- 678
Hi there,
This post seems to be relevant: opensourceinfo: winexe
You may be out of luck I'm afraid.Standard Windows installation with enabled remote sharing and administration (Windows XP Home do not support remote administration)
Let us know how you get onTo be good, you must first be bad. "Newbie" is a rank, not a slight.
- 12-03-2010 #5Just Joined!
- Join Date
- Dec 2010
- Posts
- 5
Oh my God!
Thank you very much. I read the post you suggest: there's no way to escape. I have to think another solution.
Bye.
- 12-10-2010 #6Just Joined!
- Join Date
- Dec 2010
- Posts
- 5
I changed OS. Now I have two PCs with the same OS, Windows XP Professional: one in an internal LAN, the other in internet connected to the LAN by OpenVPN.
Both PCs have the same configuration, as descripted in the opensource winexe file documentation.
When I put a file by smbclient in the two PCs all it's ok.
When I launch winexe to the two PCs one it's ok and the other not.
I don't have idea on this difference of behaviour.
Help!
- 12-10-2010 #7Just Joined!
- Join Date
- Dec 2010
- Posts
- 5
Eureka! I've found the problem.
To use winexe the PCs must sign in the same domain of the server at least one time, for example at the first installation. Then you can move the PCs wherever you want and all will work fine.


Reply With Quote
