File Sharing between a wireless notebook and a wired desktop managed by tplink in the room is not a default option, but remember that this problem was not solved when the two computers were wired at the same time. In cmd, ping the IP address of the other party. Timeout, although both machines use DHCP to automatically allocate IP address 192.168.1. ×× for the same network segment, Ping is still unavailable.
First, you must know the basic conditions for mutual access between Windows Network neighbors:
1) the computers on both sides are enabled, and network shared resources are configured. Install the nwlink IPX/SPX/NetBIOS compatible transport protocol. In fact, you do not need to install this protocol when sharing files, however, it may be used in LAN Intranet games.
2) The "Microsoft network file and print sharing" service is added to the computers of both parties, enabling the Guest user in "management;
In general, the "Microsoft network file and print sharing" service has been selected in the default properties of the network connection status. The Guest user is enabled because the default Guest user is disabled. Because the shared file is accessed by the Guest account by default, you can choose Control Panel> Administrative Tools> Local Security Policies> Local Policies> Security Options> network access: set the local account sharing and security mode. By default, the user-defined access identity can be changed from guest to classic. We recommend that you set this to improve security.
3) both parties have correctly set the Intranet IP address, and must run "System Properties"-"network ID"-"network ID" in a network segment ", the computer name is unique in the same working group without a domain. This is generally true in 1.1 cases. If the network segment is different, mutual access is definitely not allowed.
4) both computers have disabled the firewall, or the firewall policy does not block access from network peers. In the XP system, select "file and printer sharing", "remote assistance", and "Remote Desktop" in the control panel> firewall settings>.
5) shared folders are required. Otherwise, the system prompts that you do not have the permission to access resources. Set the shared file in the shared folder attribute.
After completing the above five steps, the file exchange is basically done, but the program-> attachment-> communication-> Remote Desktop Connection still cannot respond, this is because Remote Desktop Connection uses the default port 3389, which is usually not enabled by default. Hackers can use some automatic scripts to open port 3389 of bots and perform desktop control. On the local machine, we don't need to be so complicated. We just need to right-click my computer and choose Properties> remote to tick Remote Assistance and remote connection. So far, the Remote Desktop is enabled, and the IP address of the other party is entered. Is it connected? Haha it's that simple ~~~~~
