Gamesnert

New Member
Joined
Jan 31, 2009
Messages
6
First off, I'm new on these boards, and if this is a wrong board or anything, just tell me.

So anyway, I'm someone who likes to script for websites. I've set IIS website port to 22004 and it's also portforwarded.

Now when I connect to Link Removed, I get my website. If I do it with my local network adress, it also works. But when doing it with my external IP, it can't find the server.

I'm not a pro in these kinds of things. I more like experimented with small website things, and now decided to really make a website for my MTA server. But I did find something that might be interesting. If I go to the resource monitor>network then tick System, and then look between TCP ports, see in my included picture.

In case you don't trust the picture, that's fine. It basically says my local port is 22004, but my remote one is 55294... Could this mean that for some reason my PC asks my router for information from port 55294? Or is there something else going on? Tell me if you guys need more info.

I've searched for about an hour, and didn't find much. (especially because I didn't know where to look =/)

Thanks in advance,
Gamesnert.
 


Solution
Welcome to the community, Gamesnert! It seems like you're facing an issue with accessing your website hosted on IIS from external networks using your external IP address. The fact that it works locally and through the local network but not via the external IP suggests that there might be a network configuration or firewall issue. The difference in ports you mentioned (local port 22004 and remote port 55294) is normal in a connection because it is using dynamic port allocation. This process is where your PC dynamically selects a port for the connection different from the one you set for your web server. Here are some troubleshooting steps you can take to address the issue: 1. Firewall Settings: Check your router's firewall settings...
Welcome to the community, Gamesnert! It seems like you're facing an issue with accessing your website hosted on IIS from external networks using your external IP address. The fact that it works locally and through the local network but not via the external IP suggests that there might be a network configuration or firewall issue. The difference in ports you mentioned (local port 22004 and remote port 55294) is normal in a connection because it is using dynamic port allocation. This process is where your PC dynamically selects a port for the connection different from the one you set for your web server. Here are some troubleshooting steps you can take to address the issue: 1. Firewall Settings: Check your router's firewall settings to ensure that port 22004 is allowed for incoming connections. You might need to configure port forwarding specifically for port 22004 to your PC's local IP address. 2. Public IP Address: Ensure that you are using the correct public IP address to access your website externally. You can verify this IP address by searching "What is my IP" on Google. 3. ISP Restrictions: Some ISPs restrict certain ports. Check with your ISP to see if there are any restrictions on the ports you are trying to use. 4. Router Configuration: Double-check the port forwarding settings on your router to guarantee that external traffic on port 22004 is correctly directed to the internal IP of your PC hosting the website. 5. Router Restart: Sometimes, restarting the router can resolve temporary networking issues. If after checking these steps you still encounter issues, providing more information like router model, ISP, and any specific error messages received when accessing the site externally can help in diagnosing the problem further. Feel free to provide more details or questions, and the community will assist you in resolving this connectivity issue for your website.
 


Solution
Back
Top