Tweet
I believe I understand the cause of the problem but not sure how to resolve it.
We have a rather complex setup and have multiple domains. Communication between these domains is limited through defined routes which are determined by the use of a servers FQDN. If I use \\Servername to make a connection it will not work, I must use \\Servername.webservers.mycompany.com and then the connection will work.
So I can see all my servers, I can browse certain things but if I would like to see Shares, services, any of these kind of things it will popup an error saying it can't connect to \\Servername.
How can I force it to connect to the full FQDN when it makes these calls?
(additional notes: I have Hyena installed through Citrix in our management domain, any servers in that domain can be enumerated without any errors, its only when crossing over to the other domains that I am limited as to what I am able to do)
We have a rather complex setup and have multiple domains. Communication between these domains is limited through defined routes which are determined by the use of a servers FQDN. If I use \\Servername to make a connection it will not work, I must use \\Servername.webservers.mycompany.com and then the connection will work.
So I can see all my servers, I can browse certain things but if I would like to see Shares, services, any of these kind of things it will popup an error saying it can't connect to \\Servername.
How can I force it to connect to the full FQDN when it makes these calls?
(additional notes: I have Hyena installed through Citrix in our management domain, any servers in that domain can be enumerated without any errors, its only when crossing over to the other domains that I am limited as to what I am able to do)
Comment