Windows Server DDNS, Networking and Me

[Christopher Evers]

Okay, let me start off with a run down on the situation:

At one point the security system in the building was connected to the Internet and able to be accessed remotely and now is not. The Tech, that still rules the network but never comes to the building, still has all the information for running the equipment, and is not allowing me to use any of it. I can't log on to any router, switch, server (other than my own) or coffee maker in the building. This as you could imagine is making my ability to do the job very difficult, no matter what the task. Being that the system worked before, I can only speculate that no settings have changed, though I have to guess because the IT is not informing me on how he had it set up beforehand. The security system is apparently very old, because the manufacture doesn't want to acknowledge that it ever existed, so technical support is little to none. Looking at the system it uses 3 DDNS systems embedded in the OS, though 2 of them do not exist anymore and the other is a pay to use (DynDNS), boss is not excited about that. I did start working with no-ip to get it working. I have the client installed on a machine running Windows Server 2008 Enterprise R1 and attempting to run a web page with IIS 7. The security system runs through a web browser, so as long as I can get traffic to flow from the Web, to the server, to the security system it will work as needed. The issue that I am running into is, I think the router is not allowing inbound connection to the server, and this is preventing a connection. Neither port 80 or 8080 will connect, though I am able to ping the URL. I did read in a place about how no-ip requires port forwarding and DynDNS does not.

My questions are:

Is my ability to ping the URL only because no-ip is in the middle or, is it actually connecting to the server? Without access to the routers do you know of a way to accomplish this task?

I hope that I have provided enough information. Any feedback you can provide would be much appreciated.

 

[ChatGPT]

Given the complexities you're facing with the security system connectivity and the challenges with the IT setup, here are some insights and suggestions to help address your issues:
1. Ping vs. Web Connectivity:
- Pinging a URL simply verifies network connectivity, not necessarily web server access. The fact that you can ping indicates basic network connectivity.
- It's essential to differentiate network connectivity from application-level connectivity (like HTTP requests for a website).
2. Port Forwarding:
- Port forwarding is crucial if you want to access the server from the external network. Without proper port forwarding rules on the router, inbound connections won't reach your server.
- Ensure that port 80 (HTTP) and 8080 (alternative web server port) are correctly forwarded to the internal IP address of your server in the router settings.
- If you don't have access to the router, you need to work with the network administrator or IT personnel who can configure the port forwarding rules for you.
3. Security System Connectivity:
- As your security system runs through a web browser and relies on web connectivity, you must ensure that the proper ports are open and forwarded.
- Verify that the security system's web interface doesn't rely on other ports apart from 80 or 8080. Some systems might use non-standard ports, so check the system's documentation if available.
4. DynDNS vs. no-ip:
- Both DynDNS and no-ip provide Dynamic DNS services to map a domain name to a dynamic IP address. The choice between the two typically comes down to personal preference and specific requirements.
- Ensure that the DNS settings are correctly configured for the chosen service and that the dynamic IP is updating properly to reflect your current public IP address.
5. Accessing Routers:
- If you don't have access to the routers or the IT is uncooperative, it limits your ability to troubleshoot network issues directly.
- Communicate the urgency and impact of the connectivity issues to the IT department or the individual responsible for the network configuration in your organization.
6. Remote Access Options:
- Depending on your organization's policies and setup, you might consider remote desktop services, VPNs, or other remote access solutions to gain access to internal systems for troubleshooting and configuration changes.
In summary, resolving connectivity issues with the security system involves ensuring proper port forwarding, confirming web server accessibility, and possibly collaborating with IT personnel or network administrators to address router configurations if you lack access. By carefully addressing these technical aspects, you can improve the chances of establishing the required connectivity for the security system to function correctly.