![]() |
Hello Ulrich, Hello everybody, On Tue, 27 Mar 2001, Ulrich Eckhardt wrote: >Hi, > >i don't think this is a problem of the different windows versions. >WHFC runs fine on Windows 98/NT/2000. This looks more like a DNS >or routing problem. Check that reverse mapping of the DNS works >propperly and see the WHFC FAQ topic "I get a message "ERROR:WSAENOTSOCK" >or WHFC hangs". I checked the DNS and indeed found a reverse mapping problem which I corrected. That still didn't change my problems at all; both clients still behave exactly like before. telnetting to port 4559 of the HylaFAX server works fine, though; I get the 220 message; and the clients all have but one network interface (an Ethernet card) so I don't think whfc binds to the worng interface. Furthermore (in reply to someone elses suggestion), the whfc directory is currently set to "full access for Everyone". Does anyone know what I can do now to get rid of this problem, or to at least find out what's the reason's for this problem? Greetings Kasi Mir ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null