Search results

I remember one difference between the to operating systems. When I first started the HWInfo's Remote Center dialog on the win10 the Firewall asked me to open all ports for further communication. On the WinServer2016 this did not happen and I created the Firewall rules manually.

@Martin: I have checked it again. There is no rule at all to block 27007. Is 27007 the port for the connection? If so should I see any special communication with WireShark?

@nero With a non domain monitoring PC on the same subnet we have exactly the same behaviour as described above.

@Martin Can you specify what you mean with "enabled in your network" ? While we were testing we created Firewall rules specific for the HWInfo to enable all ports for TCP and UDP both ways and on both machines. This did not help.

@Martin It is not commercial, it is an educational environment where the students try to find out which are usefull analysis methodes and which are not. @nero Thanks for the hint. As I suspect most policies are default in this enfironment. We will test the communication with a non domain...

@Martin No, it is the free version. Does that make any differece? @nero Of course group policies are used inside the domain mainly to change some user specific settings. Can you specify in more detail what kind of settings can make such problems? Especially as the server PC is "only" host of...

The Win10 is part of a Microsoft domain network, the servers network is private as it is the host of several VMs which are the domain servers. And I try to control the hardware of this underlying host machine.

Yes, I tried it both ways. The Windows Server is able to collect the data of the Windows Client. I switched the Settings of HWInfo apps the other way round. The main problem is that HWInfo called on the W10 PC is not able to establish a connection to the HWInfo called on the Windows Server2016...

I have the same issue. A Windows 10 PC can be found by a HWINFO Server application as a Winsows Server 2016 PC is not connected by a HWINFO server running on a W10 PC. Defining Firewall rules for HWInfo64 TCP and UDP on both PCs did not help.