Author Topic: "No answer from remote host" - error  (Read 6736 times)

Offline ILAN

  • Posts: 6
"No answer from remote host" - error
« on: September 05, 2004, 15:58:38 »
Dear Thomas,

What does it mean when 3DWatch continuosuly reports the following problem?

05/09/2004 16:54:13 -1 ourdomain.com: No answer from remote host (please check address and timeout value)

Thanks

ILAN

Offline Thomas

  • Administrator
  • *****
  • Posts: 1249
"No answer from remote host" - error
« Reply #1 on: September 07, 2004, 10:17:31 »
Hi ILAN,

This means that the remote DNS service is not available or that the address of your DNS service provider is not valid. If it worked before, I guess something's wrong with your DNS provider.

Have a nice day!

Thomas
Bitte beachten Sie das Urheberrecht und verstoßen Sie nicht gegen von Ihnen akzeptierte Geschäftsbedingungen.
Please don't violate copyright laws and observe the terms that you agreed to.

Offline ILAN

  • Posts: 6
Found my problem.
« Reply #2 on: September 15, 2004, 11:32:02 »
Dear Thomas,

In Internet Explorer, Tools, Internet Options, Connections - you will see a box for Dial-Up and Virtual Private Network Settings - and a box for Local Area Network (LAN) Settings.  One refers IE how to connect when a particular  dial-up connection is in use, and the other tells IE how to connect when the LAN connection is in use, or so I understand.

Thomas Shinder has quite a good article on this:
http://www.isaserver.org/tutorials/Solving_the_Mystery_of_the_VPNRASWeb_Proxy_Client.html
Here he describes what the differences between the two.

You'll notice that the first box applies to dial-up connections ONLY.
In our list of dial-up entries over there we have 'sentech' - but NB it's not the 'sentech' that 3DWatch uses, that one is stored in C:\Dokumente....\rasphone.pbk.

Basically, Internet Explorer can be configured to either go through the web proxy running on the machine, or use another route, this other route is STRAIGHT through the firewall, which requires a PACKET FILTER in Microsoft ISA Server.  I stand to be corrected, but 3DWatch does not autimatically use IE's proxy settings.  So because 3DWatch is also running on the machine, and 3DWatch cannot be configured to use a proxy (possibly a feature in the next version :D) it requires a packet filter too.

To cut a very long story short,  I needed to create a Packet Filter on the ISA Firewall which allows HTTPS on port 443 out, so that 3DWatch can communicate with DynDNS.org's Secure Pages.

Just wanted to make a note of this so if others get the same error - they know what to check.

Ciao for now.
ILAN