Troubleshooting the client and server communications
Follow these guidelines to troubleshoot the client and server communications.
Verify communications between client and server computers
- Ping the client computer from the server computer and ping the server computer from the client computer. Ping is a textual command. To use it, open the Command Prompt window and typeping [computer name], wherecomputer nameis the name of the computer you are trying to contact.
- To verify that there are no name resolution issues, ping the client computer from the server computer and ping the server computer from the client computer using the IP addressping [IP address], whereIP addressis the IP address of the computer you are trying to contact.
Verify IIS
To ping using the computer name, the host must be configured to use a host name. To verify
that this is functioning, open the browser on the client and type
http://<
server computer name
>
.If IIS is working correctly, this opens the default webpage installed when you set up
Internet services (Internet Information Server) on the server. (IIS is required on each SE
Server.)
If you cannot access the webpage, try restarting the IIS server in the IIS manager.
Verify the RSViewSE site
Browse the HMI server from the client using a browser by typing
http://<
computer name
>/RSViewSE
, where computer name
is
the name of the server computer.This should browse to the default webpage that is installed with
the HMI server.
If the client cannot connect to the server, make sure that:
- The client and the server are pointed to the same FactoryTalk Directory.
- The client and the server are of the same version.
Further troubleshoot
If the client still cannot connect to the server after the previous checks, install the
server and client on the same computer and verify IIS and the RSViewSE site. If the
verifications work but the tests fail over the network (the server and client on separate
computers), the problem is with the computers or network configuration.
Provide Feedback