The first thing checked was the proper connection between the U2000 client installed in customer’s NOC and the server. Therefore, many tests of ping and traceroute using the ports of the different services necessary to connect each other were done. Thanks to this, we detected that webSever port 8080 was blocked.
Then, the port was open in the path, but the fault was still there, because a white screen started to be showed but the information never appeared.
Direct from client of the server
In the troubleshooting analyze it was concluded the necessity of avoid Network elements in the data path, that’s why we tried a direct connection from the client installed in the server. But a white screen was displayed instead of the information of the menu. This behavior was really bizarre because there were not equipments over the path between the server and the NEs able to block any request. This means that the connection throw the DCN was completely transparent.
Therefore, we decided to check out the web configuration of the server and when the WebBrowser used by default was checked we found the following wrong parameters:
Cookie acceptance policy = block cookies
Popup windows = block unrequested popup window
Proxies = Manual proxy configuration
These parameters were changed to:
Cookie acceptance policy = allow all cookies
Popup windows = Not block unrequested popup windows
Proxies = Direct connection to the Internet
1. There must be a direct connection to the servers where the U2000 is allocated. In case of FireWall or other network elements in the path, it is necessary to open all the necessary ports such as: 8080(webServer), 31037(server), 1400(navigator), 20-21(FTP) and so on.