Forums: Nc.exe - Forums

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Nc.exe problem with binding

#1 User is offline   blackP0ster 

  • Private First Class
  • Icon
  • Group: Members
  • Posts: 129
  • Joined: 02-December 03

Posted 07 January 2004 - 04:05 AM

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
0

#2 User is offline   temptation 

  • Private First Class
  • Icon
  • Group: Members
  • Posts: 80
  • Joined: 30-November 03

Posted 07 January 2004 - 04:15 AM

Well i tried ...

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 ...
0

#3 User is offline   blackP0ster 

  • Private First Class
  • Icon
  • Group: Members
  • Posts: 129
  • Joined: 02-December 03

Posted 07 January 2004 - 04:22 AM

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!
0

#4 Guest_polax_*

  • Group: Guests

Posted 09 January 2004 - 02:54 PM

I to have had the problem I to test that thx
0

#5 User is offline   FiStEh 

  • Private First Class
  • Icon
  • Group: Members
  • Posts: 58
  • Joined: 30-November 03

Posted 13 January 2004 - 04:32 AM

Didnt you see the difference? :P

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 :)
0

#6 User is offline   t_gillum 

  • Private
  • Icon
  • Group: Members
  • Posts: 16
  • Joined: 06-January 04

Posted 13 January 2004 - 05:31 AM

Well i was about to say something but someone took my answer
0

#7 User is offline   The Storm 

  • Sergeant
  • Icon
  • Group: Members
  • Posts: 200
  • Joined: 25-December 03

Posted 13 January 2004 - 06:31 AM

on my pc it only works with e:\winnt\system32\cmd.exe only cmd don`t work. Its quite funny i think!
0

#8 User is offline   TheSpider 

  • Private
  • Icon
  • Group: Members
  • Posts: 13
  • Joined: 21-September 03

Posted 13 January 2004 - 10:11 AM

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.
0

#9 Guest_PhYtoN_*

  • Group: Guests

Posted 16 January 2004 - 11:05 AM

Shell is failure...
0

#10 Guest_tstngry_*

  • Group: Guests

Posted 16 January 2004 - 09:50 PM

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. ;)
0

#11 Guest_PhYtoN_*

  • Group: Guests

Posted 17 January 2004 - 01:40 AM

Try this one : nc.exe L -vv -p [PORT]
0

#12 User is offline   ctx 

  • Private
  • Icon
  • Group: Members
  • Posts: 11
  • Joined: 02-January 04

Posted 17 January 2004 - 03:33 PM

thnx 2 all in this post - i just learnt something new :)
0

#13 User is offline   h3llraz0r 

  • Private First Class
  • Icon
  • Group: Members
  • Posts: 144
  • Joined: 31-August 03

Posted 17 January 2004 - 05:01 PM

this command had always worked for me from any dir

nc.exe -L -d -e cmd.exe -p 1111
0

#14 Guest_Blast3rPL_*

  • Group: Guests

Posted 17 January 2004 - 11:39 PM

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 ?
0

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users

  • Share



Our Sponsors:


SwiftLayer Affiliate Web Hosting