If I remember correctly, the clients try IP first, then DNS, then NetBIOS. Log on to an arbitrary client and ping the FQDN of your ePO server and repositories to verify DNS entries of server and SA's.
Everything pings properly, just for some reason when I look in the agent_workstation.log file I only see the IP address:
connecting to real server: 10.10.1.1
connected to ePO server: 10.10.1.1
Because it uses the sitelist.xml stored IP to connect.... It will change that if ever stops responding. My first post was incorrect..."The computers with an existing agent installed will attempt to connect back to the ePO server using the following order:
- IP address
NOTE: The agent will attempt to connect to the ePO server 6 times, using the IP address - successfully connect to the server once it uses DNS. At this point the agent will download an updated SiteList.xml file and connect successfully thereafter using the new IP address."
Thanks for the information. So it doesn't seem there's a way to force it to use DNS which is a problem if we wish to use an EPO server in our DMZ (there's a thread about how to do so and it seemed that you had to use DNS in order to accomplish this).
Look into Agent Handlers for DMZ's. They work great.... Download the Agent Handler white paper for appropriate design and firewall port req's.
I'll check that out, although if the workstation is using the IP of the internal server, rather than DNS, not sure how it'll work, but I'll have to read up on the agent handler, as it may just add something to the "list" of what/where to go if the first thing fails.