Initially when I started using EQBC, I went to whatsmyIP.com and it gave me a 171..... IP address (my router), but that address didn't work for me to connect my two PCs. So, I ran the C prompt to get the IP address for each PC and decided to connect to 192.168.1.4 2112, which thus far has been working great.
Now, I am trying to have another party connect to my PC 192.168.1.4 2112 (runs EQBC appllication (mq2eqbc chat box)), we have also tried connecting to the actual router the IP 171 and that failed as well. That is when I did the following steps:
1. Disabling my computer and router firewall.
2. Establishing the port foward in my router.
3. Enabling my firewall and allowing EQBCS to connect to the internet, send and receive data.
4. Enabling my computer for remote access.
5. Setting the IP addresses in my router to correspond to each perspective hardware (i.e. printer, PC#1, PC#2, Vonage, PS3).
6. I even went as far as to specify which ports EQ sends and receives data per computer.
I think I might have figured it out just by retyping all this. Please guide me in the right direction if I am off track. I need to go back into my router and specify (force/create) the EQBCS server and then assign a port on that particular IP address. If this is the case, I have looked through my router options and created the EQBC server and assigned a port. Lastly, if this is the case, why am I sometimes able to connect to other PCs outside my network, but they can't connect to mine? I will recheck it again this afternoon even if I have to reset the router and start over.
Pretty much on the right track, sounds like.
As far as why you can sometimes connect to someone, there are a couple reasons you could:
- They have the port forwarding/firewall set up right.
- Their cable/dsl modem is directly connected to the PC, intead of a router using NAT.
You need a port forwarding rule for your router so others can connect to your public routeable IP (the one whatsmyip sees), on a certain port, and forwards that traffic to your internal IP (show with ipconfig) on the system running eqbcs.
Forward to IP: 192.168.1.4
Forward to port: 2112
Forward protocol: TCP
And for your firewall, you need to tell it to allow any incoming TCP connection on port 2112. Just telling it eqbcs can "send and recieve" will not work, that is just for connections that app initiates. Any normal firewall will stilll refuse incoming connections that were not initiated by the app you add as an exclusion.
Once you do those, then another person on the net, can connect to your public IP (shown from whatsmyip) on port 2112, and it will be forwarded to 192.168.1.4 port 2112, where eqbcs is listening (and the firewall is allowing the incoming connection), and the connection will work.
I would also suggest having eqbcs listen on 0.0.0.0, not 192.168.1.4. That way if for any reason it changes, you just have to make sure your forwarding rule is up to date, and not screw with also changing the eqbcs configuration. It does not hurt to put in 0. Most people do not have multiple interfaces, and even if they do (wireless + wired for example), not like it will make a difference in eqbcs case.
Finally, while generally speaking, the lease your modem acquires will not expire unless you force it to, you never can tell. It depends on your ISP server the dhcp service is running on, whether it is rebooted, what it does with existing leases at the time, the lease time to begin with, etc. I would suggest registering a free dynamic dns service account, from a service like noip.com, and then running their little tray app to keep it updated. That way, someone can always connect to the host.domain you reg for, instead of having to make sure they have the right public IP.
htw