![]() |
On Mon, Jul 15, 2002 at 01:01:42PM +0200, Danilo Godec wrote: > I have a Win2k machine using Terminal Services. I had WHFC-1.0.8 installed > on the machine for almost a year and I was able to use it (one user at a > time). > > Just recently WHFC stopped working. It simply freezes when it is supposed > to contact hylafax server. > > In my investigation (using a packet sniffer) I have found out, that WHFC > somehow sends a wrong IP in it's PORT command instead of the correct one > (WHFC sends 169.254.83.200 while the correct one is completely different), > so that hfaxd is connecting to that bogus IP. That's a LINKLOCAL address -- a made-up DHCP address, assigned by Windows when it tries to get an address and can't. I had a problem with the same thing on a w2k machine at a clients', last year. For some reason, there's a phantom interface in the OS, and WHFC is apparently binding to the wrong one. Did you service pack the machine recently? Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null