We created a virtualized server and tried to connect to it with its authorized IP.
But this error is coming up.
I looked it up and I don't think it's a common error, but I don't know the solution.
Server param. I'm using the p-module.
Server EXE program.
The port is 15003, and the IP is the AWS EC2 server PUBLIC IP.
The server firewall has been disabled and SECURITY GROUP has allowed all traffic.
I turned off the firewall.
Error in that state.
Error Contents: server socket listen failure. make sure that the TCP or UDP listening port is not already in use. , socket creation failure : TCP listen socket, socketerror:10049> static UDP socket, socketError:10049>
After entering the server parameters, the m_server.start error occurs when there is no IP on the Internet, but I don't know if something else is needed.
aws socket server
Once you create a server socket, try 0.0.0.0 for the address you want to BIND.
The error itself was caused by a missing NIC corresponding to the address.
https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx (See WSAEADDR NOTAVAIL)
Cannot assign requested address.
The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote computer (for example, address or port 0).
As a basic socket example, I made a window instance in aws and tested it.
The firewall on the Windows server seems to be blocking it by default. Turn off the firewall on the Windows server and test it.
Firewall Settings
Control Panel > System and Security > Windows Firewall
© 2024 OneMinuteCode. All rights reserved.