Socket error

[limohabs]

Hi
All our clients are receiving the error SOcket Error - Connection to remote host timed out
We are using Wingate Gatekeeper 6.6.4 Build 1338, on a virtual Windows XP SP3 machine (VMWare ESXi 5.0)

Windows Update are turned off.
A major change happened a few weeks ago on our AD. We upgraded our domain and forest from 2000 to 2003. Microsoft LYNC requires that upgrade. During this installation we also need to create a DNS _sipinternaltls entry, which uses port 5061. That's the only change I could think of, but as I said we did that a few weeks ago, and the socket error just happening

Thanks for any help you could provide.

Martin

[adrien]

Hi

it's possibly a DNS issue. DId you recently alter configuration on your new AD DNS servers? E.g. change or remove forwarders configuration?

If the WinGate computer is using the AD for DNS, this could cause WinGate to no longer be able to do DNS lookups on the internet.

Regards

Adrien

[adrien]

Hi

what did you want me to expand on? Are you seeing the same problem as the original poster?

Regards

Adrien de Croy