Quote from
Mario on August 2, 2018, 11:09 am
erekyu,
Not sure what you mean by "the static ip is internal and external"?
If you try to connect to antMan using the antsle's IP address you must add port 3000 (antMan is listening on 3000)
http://x.x.x.x:3000
If you are on a Windows machine, it does not resolve .local names by default. This requires an mDNS responder which is installed with iTunes or Apples Bonjour print service for Windows
https://support.apple.com/kb/DL999?viewlocale=en_US&locale=en_US
Check out this forum post:
antsle.com/forum/topic/did-windows-10-update-1803-break-bonjour-local-addresses/
Also, you must be on the same subnet as the antsle to resolve the .local domain names.
Is your ethernet cable plugged into the correct ethernet port? as shown here: http://docs.antsle.com/setup/#2-connect-power-and-network
A third options is to get an 'antsle.us' subdomain through your account on antHill.antsle.com. This subdomain will use the public DNS to resolve your antsle's private IP which is more reliable than mDNS on Windows.
See 'Easy HTTPS to antMan' here: https://docs.antsle.com/https/
erekyu,
Not sure what you mean by "the static ip is internal and external"?
If you try to connect to antMan using the antsle's IP address you must add port 3000 (antMan is listening on 3000)
http://x.x.x.x:3000
If you are on a Windows machine, it does not resolve .local names by default. This requires an mDNS responder which is installed with iTunes or Apples Bonjour print service for Windows
https://support.apple.com/kb/DL999?viewlocale=en_US&locale=en_US
Check out this forum post:
antsle.com/forum/topic/did-windows-10-update-1803-break-bonjour-local-addresses/
Also, you must be on the same subnet as the antsle to resolve the .local domain names.
Is your ethernet cable plugged into the correct ethernet port? as shown here: http://docs.antsle.com/setup/#2-connect-power-and-network
A third options is to get an 'antsle.us' subdomain through your account on antHill.antsle.com. This subdomain will use the public DNS to resolve your antsle's private IP which is more reliable than mDNS on Windows.
See 'Easy HTTPS to antMan' here: https://docs.antsle.com/https/