[TerminallyIll]

Just started learning Winsock and decided to make a RAT, it does what I want when ran on the local machine, using a Netcat listener but when I run it on another computer on the same network it doesn't work. Help me please.

[YouthInAsia]

Are you connecting to the correct ip and port of the machine?

[aeiro]

Just started learning Winsock and decided to make a RAT, it does what I want when ran on the local machine, using a Netcat listener but when I run it on another computer on the same network it doesn't work. Help me please.

make sure you're connecting to the local ip not the external.

[TerminallyIll]

Oh wow. Thanks a lot guys. Have any tips to learn Winsock and making better RATs?

[malpwn]

Oh wow. Thanks a lot guys. Have any tips to learn Winsock and making better RATs?

Here's your tip :

DON'T

[aeiro]

Here's your tip :

DON'T

and why not?

[YouthInAsia]

Here's your tip :

DON'T

You're a moron. In terms of interface there's practically no difference between BSD nd Winsock. Only the implementation comes down to Microsoft. In terms of core networking functionality whatever you compile on Linux is practically the same on WIndows. It changes when you get into more abstract interfaces like epoll and iocp. But I'd argue even the implementation of BSD sockets is better on Windows than it is on Linux. And unless you want to alter the TCP stack yourself which comes down to driver development (Which I highly doubt the OP wants to do) it makes no F U C K I N G difference of whether they're on WIndows or Linux. Because most retards end up using select anyway or recv with nonblocking flag.

[malpwn]

You're a moron. In terms of interface there's practically no difference between BSD nd Winsock. Only the implementation comes down to Microsoft. In terms of core networking functionality whatever you compile on Linux is practically the same on WIndows. It changes when you get into more abstract interfaces like epoll and iocp. But I'd argue even the implementation of BSD sockets is better on Windows than it is on Linux. And unless you want to alter the TCP stack yourself which comes down to driver development (Which I highly doubt the OP wants to do) it makes no F U C K I N G difference of whether they're on WIndows or Linux. Because most retards end up using select anyway or recv with nonblocking flag.

Wrong quote ? :v

[Torrendo™️]

Wrong quote ? :v

I think so lol bit of a long for a DON'T don't you think

[TerminallyIll]

Guys please stop fighting xD.

[malpwn]

No that was 100% directed towards your stupidity

I literally said DON'T as a sarcasm and you had to write a long ass essay on the difference between socket implementation on linux vs windows
When clearly there's wasn't even a mention of any OS dependence leave alone writing a driver
P.S please pass me what you are smoking over there looks like you are on some good shit

I think so lol bit of a long for a DON'T don't you think

Rethink ^^^^^^^^^