All the BES components have been successfully installed but we’re experiencing problems when trying to deploy tasks across different subnets.
Directly connected
BES Server/Console directly connected (using a cross-over cable) to intended Client: BES Client Deploy installation successful, loads into Computers list on the Console and able to deploy tasks/fixlets.
Same subnet
BES Server/Console and intended Client connected through a switch (i.e. same VLAN): BES Client Deploy installation successful, loads into Computers list and able to deploy task.
Different subnets
Connected on different VLANs (using a router with switch module): BES Client Deploy installation successful but
does not
show up in the Computers list.
Is there something I need to configure in order for the Server/Console to detect Clients on other networks?!
I can telnet from the Client to the Server/Console port 52311, yes. However I cannot telnet from the Server to the Client - I guess this is expected?
I don’t have a domain configured as this is a test network. Both the Client and the Server are operating on the default WORKGROUP. Does the traffic contact each other by name and not IP addresses then? We do not have DNS configured on the server - does this need to be implemented for it to work?
I checked BES client logs, there is a error found, “GetURL failed”, I forgot to change IP in \windows\system32\drivers\etc\hosts. correct that IP then client connect is successful.