Forum Discussion
- akihiro1Moderator
I actually tried the VSR Manager via VPN in my environment.
But I could not add the Agent to VSR Manager via VPN.
To add Agents to VSR Manager, TCP135, 137, DCOM port and TCP4443 need to be accessible from VSR Manager to the Agent.
(In case of VSR Monitor, TCP135, 137, DCOM port need to be accessible from VSR Monitor to the Agent.)
So I used Wireshark in order to investigate the cause in my VPN environment.According the packets on Wireshark, VSR manager or VSR monitor tried to firstly access TCP135 of Agent.
In my VPN environment, TCP135 port was blocked.
In addition, I tested a Powershell command "Test-netconnection <IP address> -port <port number>".
As the results, TCP135, 137 and 4443 were not accessible. The below result is a sample for TCP135 in my environment.*********
PS > test-netconnection x.x.x.x -port 135
WARNING: TCP connect to (x.x.x.x : 135) failedIn general,
ComputerName : x.x.x.x
RemoteAddress : x.x.x.x
RemotePort : 135
InterfaceAlias : Ethernet 4
SourceAddress : y.y.y.y
PingSucceeded : True
PingReplyDetails (RTT) : 292 ms
TcpTestSucceeded : False*********
In general, VPN provides the secure network. So I guess that VSR Manager or Monitor may be unavailable in VPN environment.- AlexNtowGHLevel 4
Thanks for your response.
Is there any way to monitor these separate VSR installations in a different workgroups in a dashboard.
The VSR manager works only on the workgroup level.
Thanks
- akihiro1Moderator
We can add computers in both domain and workgroup to VSR Manager.
Regarding "these separate VSR installations in a different workgroups", Concretely what environments do you consider ?Thanks,
Akihiro
Related Content
- 2 years ago
- 8 months ago
- 7 months ago