Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 1092 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Deployment problem : using IP instead of server name for shares ?

Pjgfi

Hello,

We have a little trouble when deploying Sophos on our WAN.

It goes quite well for computer in our LAN, but computers in the WAN simply can't see the share, they won't resolve :

\\SophosServerName\ but will succeed with server IP.

Adding our server IP in the computer host file will allow a remote install but we can't patch every single host file, can we ?

Can we safely add or change a share in the console so that remote PCs try with IP instead of server name ? Current share is greyed out...

Many thanks.

PJ

EDIT : looks like it could simply be a DNS problem on our network, but I'd like to know the answer about IP anyway.

:23455


This thread was automatically locked due to age.
  • 0

    HI, 

    Was it that the clients need a DNS suffix entry to resolve the server by Netbios name?  Can you push this out with GPO?

    You should be able to create a new updating policy and reference the updating share using the IP of the server.  This will then go into the "Initial Install Source" and "Primary Server" tabs.  This way, when the scheduled task is created on the client to install the endpoint software, it will then reference the update share using IP to install and update.

    Out of interest, would putting the FQDN of the server in help?  This would also suggest the DNS suffix problem.

    Regards,

    Jak 

    :23459