We are trying to find wyse terminals that are on subnets external to our firewall (Microsoft ISA Server 2006). WDM appears to initially contact the device on port 80. Our firewall determines that the traffic is not valid http and rejects it. To try and get around the problem we changed the port number in IIS to 8081 and restarted the server. Now if we manually add the WDM server IP address and port 8081 into the WDM properties on the client it will successfully register itself into WDM the next time the client restarts. However, the “find devices” option within WDM still does not work because WDM is still trying to talk to the client on port 80. Is it possible to change which port this initial discovery takes place on?
Thanks for the quick reply, ConfGen.
The majority of our clients are S30’s. I think our real problem is that they connect through to our main site with IPSEC tunnels set up on Zyxel routers, which also give out DHCP. As far as I can see, we can’t config the Zyxels to help find the WDM server like you would with Windows DHCP, so I’m a bit stumped as to how we can get these devices descovered without manually putting the WDM server address onto the terminals’ WDM client config.
I’m completely new to this, so I may have made some wrong assumptions on how we should be setting this up, so any guidance on standard practice would be greatly appreciated.