|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Member (11 bit)
Join Date: Nov 2001
Location: Massachusetts
Posts: 1,487
|
Since I got my router I haven't been able to direct connect to people on AIM if I try to d/c, but if they tried to d/c then it worked. But my friend who I direct connected with a lot also has a router. So I figured out by looking at netstat that aim does the following: it opens up port 4443 on the computer that wants to d/c and gets its IP address from the NIC. It tells the other person that it wants to d/c and that its IP is the IP it got from the NIC. Then if they accept it tries to connect to the NIC IP. Of course this won't work because it is the router IP they have to connect to. So if I try to connect to someone, their AIM tries to connect to 12.34.56.78:4443, which doesn't work. But if they connect to my router IP port 4443 with telnet, then it does work. But that isn't what I want.. I want AIM to connect.
Soo.. is there anyway to get aim to get my router IP instead of the NIC IP? Or maybe can I set up a virtual second NIC somehow and set its IP to my router IP and have AIM use that? I know you can tell it to "use alternate internet Address (if error when running AOL or 2 network adapters)" Thanx for any input.. RenegadeKing
__________________
"When the only tool you have is a hammer, every problem starts to look like a nail." |
|
|
|
|
|
#2 |
|
Member (11 bit)
Join Date: Nov 2001
Location: Massachusetts
Posts: 1,487
|
I got it figured out. I assigned a second IP to my NIC with the registry and made it my router IP. Aim sees it and it works now.
RenegadeKing |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|