Re: Inconsistent Access Between Alpha App Server and NoIP Address
I have followed this thread now since its start and to be honest the troubleshooting and documentation of steps taken are a little confusing. It might be in your best interest to simplify the setup and test each piece independently.
For troubleshooting purposes it will be easier if we had a better idea of your network. You mention that you are running the A5 app server on a laptop that has both a wireless and a wired network connection. You do not want to run this type of a setup across the wireless network so disable the wireless card. The fact the machine is a laptop is not a concern and should be ruled out.
You will see a list of network adapters, right click the wireless adapter and select disable.
Next you will need to verify that your wired connection is working. Try to open a webpage; for example google.com or cnn.com. If you cannot get to the webpage check your settings for the wired network card and properly configure them so you do have network access.
Right click on the wired network adapter in the "Network Connections" tool and select "Status" then click the "Support" tab. This will tell you your IP address for that network adapter on that machine. This should be a private non-routeable IP address. This will also be the IP address you do all of your internal testing with. You can also get this info by running IPconfig.exe at a DOS prompt. The /all switch will give more information. Run the command with the /all switch and make note if DHCP is enabled or disabled. Report back what the DHCP status is; depending on the status additional troubleshooting steps may need to be taken.
Next disable any and all firewalls on the laptop. This is a security concern. you should have a edge device firewall between your network and the laptop if not then also disconnect the internet during the this phase of testing. Any software firewall on the laptop is there only to protect the laptop from other machines on the internal network. The edge device firewall is there to protect the network from the internet. Unless your network is infected with malware you will be safe with the internet disconnected.
From another machine on the network ping your laptop. You should get response back. Since you mention that you have disconnects after a couple of hours you can run a ping test with the -t switch. This will continuously ping the laptop until stopped by pressing ctrl-c. Watch for dropped packets/no returns being your on an internal network you should not encounter any.
Assuming everything has worked up till now you will want to test the actual A5 web server software. You have configured the A5 web software to run on a port. Now you are going to test that the port is accepting communications. Telnet is a great tool for this.
If the IP is 10.1.1.12 and port 80 is running the web server type this at a DOS prompt.
The screen will go blank, press the enter key several times, this will sometimes get the software to respond back, or type "Helo" and press enter. A majority of network services will return an error code and is a good way to determine what software is being ran on a particular network port. Google's website returns a HTTP/1.0 400 Bad Request web page when I tried this against their servers. The A5 web server should return something as well.
Or you could open a browser and enter the IP address along with the port of the webpage. If all is working you should see the webpage in the browser.
Try these steps and report back what you have found. Also numerous logs are most likely being kept both by the A5 server and by the machines themselves. Check the logs, look for error messages or status messages let us know what they are showing.
Remember keep it simple, test the basics first then move onto the complex network configurations. Fully document what your testing and what the results are.
From what I gathered from your previous posts all of this should work. These tests are only to eliminate the basics, once that is accomplished then you can start testing the more advanced configurations.
I have followed this thread now since its start and to be honest the troubleshooting and documentation of steps taken are a little confusing. It might be in your best interest to simplify the setup and test each piece independently.
For troubleshooting purposes it will be easier if we had a better idea of your network. You mention that you are running the A5 app server on a laptop that has both a wireless and a wired network connection. You do not want to run this type of a setup across the wireless network so disable the wireless card. The fact the machine is a laptop is not a concern and should be ruled out.
Code:
Start |control panel | Network connections
Next you will need to verify that your wired connection is working. Try to open a webpage; for example google.com or cnn.com. If you cannot get to the webpage check your settings for the wired network card and properly configure them so you do have network access.
Right click on the wired network adapter in the "Network Connections" tool and select "Status" then click the "Support" tab. This will tell you your IP address for that network adapter on that machine. This should be a private non-routeable IP address. This will also be the IP address you do all of your internal testing with. You can also get this info by running IPconfig.exe at a DOS prompt. The /all switch will give more information. Run the command with the /all switch and make note if DHCP is enabled or disabled. Report back what the DHCP status is; depending on the status additional troubleshooting steps may need to be taken.
Code:
ipconfig /all
From another machine on the network ping your laptop. You should get response back. Since you mention that you have disconnects after a couple of hours you can run a ping test with the -t switch. This will continuously ping the laptop until stopped by pressing ctrl-c. Watch for dropped packets/no returns being your on an internal network you should not encounter any.
Code:
ping -t 10.1.1.12
If the IP is 10.1.1.12 and port 80 is running the web server type this at a DOS prompt.
Code:
Telnet 10.1.1.12 80
Or you could open a browser and enter the IP address along with the port of the webpage. If all is working you should see the webpage in the browser.
Try these steps and report back what you have found. Also numerous logs are most likely being kept both by the A5 server and by the machines themselves. Check the logs, look for error messages or status messages let us know what they are showing.
Remember keep it simple, test the basics first then move onto the complex network configurations. Fully document what your testing and what the results are.
From what I gathered from your previous posts all of this should work. These tests are only to eliminate the basics, once that is accomplished then you can start testing the more advanced configurations.
Comment