Innerspace Firewall Ports

Jynicks · Post by **Jynicks** » Thu Jul 03, 2008 5:08 pm

When i use my neighbor's wireless internet, innerspace works without any problems, but when i use my home internet, it says innerspace cannot connect to the server. I think it is due to the firewall ports being closed. Can anyone tell me which ports need to be opened for innerspace to run?

Post by **Lax** » Thu Jul 03, 2008 5:15 pm

None.

Inner Space uses only outgoing connections.

Ethereous · Post by **Ethereous** » Fri Jul 04, 2008 5:26 am

You can need to open ports even if you only make outgoing connections. That said, I cannot answer sorry.

eqjoe · Post by **eqjoe** » Fri Jul 04, 2008 10:37 am

Your destination port will be TCP 11500 with a random source port over 1024. If you are filtering ports over 1024 outbound, you will have to open that up to 208.64.39.116. Of course, your return packet will be on source port 11500 with the same random destination port over 1024 for that connection.

-j

Post by **Lax** » Fri Jul 04, 2008 11:34 am

You can need to open ports even if you only make outgoing connections. That said, I cannot answer sorry.

I realize this, but I haven't met a router that an average user would be using and filtering Inner Space's outgoing traffic... So you and eqjoe just inundated this poor soul with information that probably makes no sense to him, and now he's probably gone into his router and opened incoming port 11500 or set himself DMZ, neither of which will have any effect

Secondly, I checked his connection history, and he has been successfully connecting from his PC on two different ISPs (likely his own and his neighbor's as he described) ... but has not connected since the 2nd. He would have had to install new equipment or new firewall rules on the night of the 2nd, or day of the 3rd, in order for this to be a firewall issue. Frankly, I don't think this is the issue.

Jynicks, have you made sure you didn't block Inner Space from connecting via Windows Firewall or other firewall software? It's very unlikely to be port-based blocking, it is most typically application-based.

Jynicks · Post by **Jynicks** » Fri Jul 04, 2008 7:45 pm

Lax wrote:
You can need to open ports even if you only make outgoing connections. That said, I cannot answer sorry.
I realize this, but I haven't met a router that an average user would be using and filtering Inner Space's outgoing traffic... So you and eqjoe just inundated this poor soul with information that probably makes no sense to him, and now he's probably gone into his router and opened incoming port 11500 or set himself DMZ, neither of which will have any effect

Secondly, I checked his connection history, and he has been successfully connecting from his PC on two different ISPs (likely his own and his neighbor's as he described) ... but has not connected since the 2nd. He would have had to install new equipment or new firewall rules on the night of the 2nd, or day of the 3rd, in order for this to be a firewall issue. Frankly, I don't think this is the issue.

Jynicks, have you made sure you didn't block Inner Space from connecting via Windows Firewall or other firewall software? It's very unlikely to be port-based blocking, it is most typically application-based.

Hmmm. I don't know. How would i check if my firewall is blocking innerspace? Thanks for the responses so far by the way.

Post by **Lax** » Fri Jul 04, 2008 11:48 pm

Go to Control Panel, and open the Windows Firewall control panel. In the Exceptions tab, check if InnerSpace.exe is there. If it is, make sure the box next to it is checked. If it is not, click Add Program, and in the Add a Program window, click the Browse button and find InnerSpace.exe where you installed it to (typically c:\program files\innerspace), then click OK. Double check that the box next to the new InnerSpace.exe entry you just made is checked, then click OK and you should be done with it.