Testing: Difference between revisions

Jump to navigation Jump to search
5 bytes added ,  2 October 2021
Line 30: Line 30:
* double [[Testing#check_the_server.2Fservice_logs | check the server/service logs]]
* double [[Testing#check_the_server.2Fservice_logs | check the server/service logs]]


=== (2) from LAN to server ===
=== From LAN to server ===
WAN &#9675; -------&gt; <span style="color:red">&#9679; LAN -------&gt; &#9679; server</span>
WAN &#9675; -------&gt; <span style="color:red">&#9679; LAN -------&gt; &#9679; server</span>


* testing on LAN (local network, subnet scope): Is service alive? The different servers between LAN or with the same ip class (ex: 1.2.3.*) may not have the firewall limit.
Testing on LAN (local network, subnet scope): The different servers between LAN or with the same ip class (ex: 1.2.3.*) may not have the firewall limit.
** connect to localhost ex: {{kbd | key= telnet 172.18.0.1 23}} (1) IP start with 172.18... is [http://www.itcom.itd.umich.edu/backbone/umnet/privateIP.html Private IP Network Numbers] (2) where 23 is the port number where the service running
 
*** If the local service is web server, you can also try to connect the internal ip e.g. {{kbd | key = <nowiki>lynx http://172.18.0.1</nowiki>}} for {{Linux}}
* Is the service alive?
* double [[Testing#check_the_server.2Fservice_logs | check the server/service logs]]
* Connect to the internal IP eg: {{kbd | key= telnet 172.18.0.1 23}} (1) IP start with 172.18... is [http://www.itcom.itd.umich.edu/backbone/umnet/privateIP.html Private IP Network Numbers] (2) where 23 is the port number where the service running
* If the local service is web server, you can also try to connect the internal IP e.g. {{kbd | key = <nowiki>lynx http://172.18.0.1</nowiki>}} for {{Linux}}
* Double [[Testing#check_the_server.2Fservice_logs | check the server/service logs]]


=== (3)  from WAN to server ===
=== (3)  from WAN to server ===
Anonymous user

Navigation menu