Resideo AlarmNet Internet Connectivity Test - Dated 12/20/19

-

1

-

Updated:
12/20/19




Step
-
By
-
Step



Internet
Connectivity Test
for
AlarmNet

And Total Connect Services


The TELNET tool at the DOS Command Prompt can be a useful tool to confirm network
connectivity to a server
. It is best to perform this test from a PC or laptop using the same network

cable that plugs directly into the AlarmNet communicator
or with a Wi
-Fi connection to the same
Access Point
.
NOTE:
Your computer may not have the Tel
net client enabled by default.
When
you try to use the telnet command and get “‘
telnet
’
is not recognized as
an internal or external

command
.....”
it is disabled. Please Google “how to enable the telnet client in Windows
xx
” then
enable telnet on your computer
and then follow test procedure below
.

Telnet
Test Procedure:

1.

Open a DOS command prom
pt window:

•

To do this, click “Start” and then click “Run”.

•

When the dialog box opens type, “cmd” and press .


2.

A valid T
elnet command will be entered like this:
C:\> telnet {Server Name or IP Address} {Port}

3.

As an example, at the DOS prompt “C:
\>”
you will type the following
to test connectivity
to the server named “
auiredir1.alarmnet.com
” over port 443:


telnet auiredir1.alarmnet.com 443


After entering the T
elnet command and clicking , the window should “blank
out” and the cursor will return to the top left and flash.
Note:
When provided, i
t is recommended to perform the telnet test to the server names
(auiredir1.alarmnet.com)
in addition to th
e IP address (204.141.57.100) because this will also test
the DNS service for IP resolution. If the test fails with the server name, but passes when the IP
address is used, there is likely an issue with the network DNS service.

4.

Next, type about 15 – 20 chara
cters, you will see the socket quickly close and your
command prompt will return, “C:
\>”. This indicates connectivity to the designated server
is working. Refer to page
s 4-
6 of this document for the full list of server names, IP
addresses, and ports that
should be tested.



-

2

-

Updated:
12/20/19




Step
-
By
-
Step



If there is a problem
...
1.

The window does “blank out” but when you type a bunch of characters and hit
you get an
HTTP
-type long error
page. Th
is indicates there
is a PROXY server between
the computer being used to TELNET and the Internet. In general,
our communicators will
not work behind a Proxy
, but there may be some network engineering that can be done at
the site to work around this, depending on the equipment being used.


2.

“Connecting to 204.141.57.100...”
followed about 30-
60 seconds later by “Could not
open...” In this case, there was a full failure to connect to the Server or
IP address
requested. The customer (
or Network Administrator) should check and adjust
their router
and firewall settings to verify port 443 is
not blocked for

outbound
traffic
to the AlarmNet
servers
. Please note there is no need to ope
n ports for
inbound

traffic
.

While our units were designed to work behind Firewalls and usually require no additional network
configuration, some networks empl
oy security measures that can
cause connectivity failures.
These may include:

•

Proxy Servers

•

Stateful Packet Inspection (SPI)

•

Packet or IP filtering

•

Any software that attempts to open or look inside our encrypted data packets.

If there is a problem reaching any of the AlarmNet servers, the customer should contact
their network administrator
and ask them to exclude the AlarmNet Servers and IP addresses
from Firewall rules, SPI, and PROXY settings
(
for outbound traffic only
)
.
AlarmNet Technical Support can answer general questions, but cannot assist with making
modifications to the end-
user network. These changes should be made by a network professional

or someone familiar with the network requirements and
other parameters
.
Static or DHCP Settings

AlarmNet Communicators can use either DHCP or Static IP addressing. If problems occur due to
automatic IP releasing
1
on the network, the AlarmNet device should be switched to a Static IP. If
static IP’s are being used, the following information is needed from the Network Administrator
before installation:

•

Static IP address for the AlarmNet device

•

Subnet Mask
•

Default Gateway

•

DNS IP Address




-

3

-

Updated:
12/20/19




Step
-
By
-
Step



1

Automatic IP Releasing: AlarmNet Internet products ping AlarmNet every 20 seconds to verify connectivity; therefore, it releases the previously
assigned IP address at the end of its session and requests a new one each time it checks connectivity.

IP addresses and Servers used for AlarmNet Services


Alarm
Reporting
and other AlarmNet Services

The Host
names and
IP Addresses below are used for alarm reporting
and communication with
AlarmNet over port 443 and are used by c
urrent AlarmNet communicators such as the 7847i.

•

auiredir1.alarmnet.com (204.141.57.100)
port
443
•

auiredir2.alarmnet.com (204.141.57.101) port 443
•

auiredir3.alarmnet.com (
12.149.218.73)
port 443
For Alarm
Net communication and re
porting with
legacy AlarmNet communicators (7845i, 7845i
-
ent) and the 7810 receiver, the following is used:


•

Host name?
204.141.57.102 port 443

Total
Connect
Services

The Host names and
IP Addresses below are used for Total
Connect 1.0 and 2.0 services
.

•

auiredir1.alarmnet.com (
204.141.57.100) port
443
•

auiredir2.alarmnet.com (
204.141.57.101) port
443
•

auiredir3.alarmnet.com (
12.149.218.73) port 443
•

dataserver1.ala
rmnet.com (204.141.58.80) port
443
•

dataserver2.ala
rmnet.com (204.141.58.81) port 443

Total
Connect video
The Server names and IP Addresses below are used for
LEGACY (non
-HD) Total
Connect Video
services (TC1 and TC2)
.

To verify connectivity for cameras
from the user network
, use a
web browser to verify
connectivity to https://video.alarmnet.com/test.aspx
. Bypass the warnings for an invalid certificate
and continue on. Once connected, you should see a page that shows the public DNS for one of the
AlarmNet video servers.
To verify that cameras will be able to upload video clips, use a web browser to verify connectivity
to https://files.alarmnet.com/test.htm
- you should get back a screen that says “This is a test...”

If the problem is on a mobile app
, use a browser to verify successful connection to

https://video.secure.alarmnet.com/test.aspx



-

4

-

Updated:
12/20/19




Step
-
By
-
Step



Compass:

The Host
names and
IP Addresses below are used for Compass IP Downloading
over port 443.
Test these at the AlarmNet communicator and programming
PC/laptop.
•

auiredir1.alarmnet.com (204.141.57.100) port
443
•

auiredir2
.alarmnet.com (204.141.57.101) port 443
•

auiredir3.alarmnet.com (
12.149.218.73) port 443
•

controlserver.alarmnet.com (204.141.58.115) port 443
•

dataserver1.alarmnet.com (204.141.58.80)
port
s 443
•

dataserver
2.alarmnet.com (204.141.58.81) ports 443

Enabling Telnet in
Windows Vista/Windows 7

1.

Open “
Control P
anel
”
2.

Go to “
P
rograms and F
eatures
”
3.

Click “
Turn on W
indows
F eatures O
n or O
ff
“

4.

Select “
Telnet Client
”

5.

Click on “
OK
”
6.

Now follow procedures to Telnet