In the OSCAR protocol, Rendezvous is a mechanism that lets two AIM clients exchange the necessary information to establish a direct, peer-to-peer connection—typically used for file transfers.
Back in the early 2000s, most computers were assigned a public IP address directly from their ISP. As a result, when
one AIM client sent its IP address to another, that address was routable on the public Internet. Today, almost everyone
is behind a router performing Network Address Translation (NAT). Consequently, the sender’s machine usually only has a
private IP address (e.g., 192.168.x.x
), which cannot be reached directly over the Internet.
To work around this limitation, Retro AIM Server can substitute your client’s private IP address with the server’s view of your public IP address. However, you still need to configure port forwarding on your router to ensure that incoming Rendezvous connections (for file transfers) are routed to the correct machine.
This guide explains how to configure your Windows AIM client to send files over the Internet using the Send File feature. If you only need to receive a file, no additional setup is required.
Same LAN Scenario
If both Retro AIM server and your AIM client are on the same local network (LAN), you do not need these steps.
Mixed LAN and Internet
If the sending client and the server are on the same LAN while the receiver is on the Internet, this guide may not
work as intended.
Security Notice
Rendezvous makes your IP address visible to the recipient. Opening a port on your home network allows inbound Internet
traffic to reach your computer on that port. Use careful judgment and consider the security implications before
proceeding.
4000
.4000
(or the port you chose)Once everything is set up:
If the receiver is on the Internet and your port forwarding is correct, the direct file transfer should succeed.