Hylafax Mailing List Archives

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: Problem with whfc via dialup




see www.transcom.de/whfc  -> faq
"ERROR: WSAENOTSOCK or WHFC hangs"
...

i cannot ping from the hylafax server to both interfaces on the windows
client!
When time permits i will have a look at the routing on the hylafax server
box.

Bernd


> -----Original Message-----
> From: owner-flexfax@celestial.com [mailto:owner-flexfax@celestial.com]On
> Behalf Of Manuel Bessler
> Sent: Friday, March 10, 2000 8:23 PM
> To: flexfax@sgi.com
> Subject: flexfax: Problem with whfc via dialup
>
>
> Hi
>
> i have a problem with whfc (1.0.5) over ISDN dialup (PPP).
> the windows machine has ethernet with ip 192.168.1.13 (not
> connected to network)
> on ISDN dialup it gets the ip 192.168.100.13
>
> my hylafax/samba -server has address 192.168.0.10
> everything is working fine (finally ;) i can ping, i can browse
> samba shares,...
>
> but when i start WHFC, hfaxd tries to establish the data conn to
> 192.168.1.13
> (the address of the ethernet dev) instead of 192.168.100.13 .
>
> it seems that whfc has problems with multiple network devices.
>
> when i try to view faxes or go to url ftp://192.168.0.10:4559/recvq/
> netscape works fine, eg. i can browse/view the faxes
>
> has anyone encountered such behaviour before ?
>
> Manuel
>
> --
> ---use Linux
>



Home
Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services