Using Smart client to connect works but the video does not come through. Says Connection failed..retrying. However, the smart client on the server works, and i can get video on a mobile client no problem. Even using the web client works. Thoughts? Ports being blocked maybe?

It is now also saying the "Surveillance system communication through the service channel is unstable. If changes are made on one part of the system, other parts will not be updated. Report this service channel problem to the surveillance system administrator.” Is this related to the name resolution?

The 7563 is the port to the recording server service, if you get a splash screen without specifying a port then you are reaching IIS on the server.

Generally check the two below articles
Adding a Recording server to Milestone without DNS
Description:

If you expect video to stream from recording server(s) in XProtect® Corporate or XProtect® Expert deployments, there are two main requirements of an XProtect® Smart (or Management) Client PC. The client must be able to:

a) Resolve the recording server's DNS hostname
b) Connect to the recording server on port 7563

In situations where the port 7563 is reachable but there is no DNS server or name resolution, it may be necessary to modify the recording server's configuration (RecorderConfig.xml) file. This is to ensure that the clients connect to the server's IP address instead of hostname.

Solution:

On the recording server PC(s), the configuration file typically resides in C:\ProgramData\Milestone\XProtect Corporate Recording Server (Win2008).

To edit this file:

- Stop the Milestone Recording Server service
- Open the RecorderConfig.xml in a text editor such as Windows Notepad
- Search for "<host />" in the file's contents and follow the instructions to modify the tag to look like the one below. (10.10.10.10 is an example only, use the actual IP address of the server.)

<host>10.10.10.10</host>
<port>7563</port>
</webserver>

After modifying the RecorderConfig.xml, you must restart the Recording Server for the modification to take effect.

TIP: After the Recording Server restart, you can verify in the Management Client that the IP is used by selecting the Recording Server, then clicking the Info tab to ensure that "Local web server address" is corrected.

Note: You can find additional information and troubleshooting protocols in KB article #331. Editing the Windows HOSTS file on client PCs is an alternative solution to this problem when DNS name resolution is impossible.



For the service channel

http://www.milestonesys....base/?articleNo=00000220