blackP0ster
Jan 7 2004, 12:05 PM
hiho!
have a problem with nc.exe
[*] searched with google
[*] searched in the forum
i set up nc.exe to listen on port 444 (nc.exe -L -vv -p 444 -d -e CMD.exe)
then i wanna connect from my own pc to my pc
so i type nc.exe -v 192.168.0.4 444
nothing happes..!
in the nc-listening-window i got this error: invalid connection to [192.168.0.4] from (UNKNOWN) [192.168.0.4] 1055
what to do now??
need help
)
black
temptation
Jan 7 2004, 12:15 PM
Well i tried ...
| CODE |
C:\>nc -l -vv -p 123 -e c:\windows\system32\cmd.exe
listening on [any] 123 ...
connect to [127.0.0.1] from localhost [127.0.0.1] 1178 |
And it worked for me perfect ...
EDIT
When it type in "nc.exe -L -vv -p 444 -d -e CMD.exe" it doen't do anything ...
it is important that it shows ...
listening on [any] XXX ...
blackP0ster
Jan 7 2004, 12:22 PM
hm..strange!
now it works! but only if i don't use e:\winnt\system32\cmd.exe
i get an error by doing this..when i use only cmd.exe it works gr8!
thx m8!!!!
black
edit:
jop-everythings working gr8 now! thx again!
polax
Jan 9 2004, 10:54 PM
I to have had the problem I to test that thx
FiStEh
Jan 13 2004, 12:32 PM
Didnt you see the difference?
nc.exe -v 192.168.0.4
versus
nc.exe -v 127.0.0.1
personally i always refer to the pc im on as 127.0.0.1 as it avoids confusion, you can always recognise 127.0.0.1
t_gillum
Jan 13 2004, 01:31 PM
Well i was about to say something but someone took my answer
The Storm
Jan 13 2004, 02:31 PM
on my pc it only works with e:\winnt\system32\cmd.exe only cmd don`t work. Its quite funny i think!
TheSpider
Jan 13 2004, 06:11 PM
i get this error.
connect to [62.168.xxx.xxx] from P3.mshome.net [192.168..xxx.xxx] 1053
Failed to execute shell, error = 3: unknown socket error
Failed to execute shell: unknown socket error
when i try to connect from my other pc.
PhYtoN
Jan 16 2004, 07:05 PM
Shell is failure...
tstngry
Jan 17 2004, 05:50 AM
| CODE |
| nc -l -p 23 -t -e cmd.exe |
This is what i use. I put it on whatever port i want and in whatever directory i choose and it always works. The key is using telnet (i think). If you just add the -t switch nc will accept telnet connections and you will get a shell just the same. Hope this helps.
PhYtoN
Jan 17 2004, 09:40 AM
Try this one : nc.exe -L -vv -p [PORT]
ctx
Jan 17 2004, 11:33 PM
thnx 2 all in this post - i just learnt something new
h3llraz0r
Jan 18 2004, 01:01 AM
this command had always worked for me from any dir
nc.exe -L -d -e cmd.exe -p 1111
Blast3rPL
Jan 18 2004, 07:39 AM
Dude you can connect if you have ip behind NAT. You must have "outdoor" IP address not 192.168.*.* then you can connect.
or if you want to connect to LAN's partner you can do like this 192.168.*.* ...
You know what I meant ?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.
