I'm also using Hylafax At the moment I have it working as our incoming fax server. I set up getty to always run at start up. To receive the incoming faxes.
I havn't been able to get the win clients faxing through it yet. (Havn't had time) They like using the hard copy fax better anyways. I thought when I first set it up I could send a fax out. But now it doesn't seem to work. :) I've replaced the mother board since and didn't send any faxes. The receiving end of it kept working. So I didn't worry about it. I get this message in kdeprintfax log " Sending to fax using: /usr/bin/sendfax -n -h '192.168.0.3' -d ''@'219-8860' -x '' -c '' -f '' '/tmp/kde-razor/kdeprint_XaSYwMG' Can not reach server at host "192.168.0.3", port 4559 " I guess I need to look into this as well. : ) Jason On Tuesday 08 October 2002 12:20, you wrote: > What are you faxing with? > > I'm trying to get Hylafax going, but it isn't working for me. I can dial > out with the modem via a terminal, and all seems fine, but Hylafax just > pukes. (Sorry I don't have the log quite handy...) If you're using > Hylafax, I'll get more details for you though. Maybe you can help me > through it. > > Kev. > > > > ----- Original Message ----- > From: "Jason Van Dellen" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, October 08, 2002 12:03 PM > Subject: Re: (clug-talk) help with SAMBA > > > Hi Jarrod, > > I tried using SWAT and WEBMIN to configure my SAMBA but it never works > exactly > the way I wanted it. So I would edit the smb.comf file manually. > Here's the conf file off my fax, file and print server. There are win98 > and win2k clients. It's setup so it chmods the files to 777 so windows can > still modify them. > > I set up the permissions on a per IP basis so I didn't need to worry about > users. Could never get that to work, I guess I'll have to look into that > some more. :) > > How this helps. > > # Global parameters > [global] > writable = yes > netbios name = JASON > public = yes > security = SHARE > create mask = 0777 > directory mask = 0777 > > [printers] > path = /var/spool/samba > lprm command = cancel %p-%j > lpq command = lpstat -o %p > comment = All Printers > print command = lpr-cups -P %p -o raw %s -r # using client side printer > drivers. > printable = yes > create mask = 0700 > > [user] > path = /home/razor/User > comment = User files > allow hosts = 192.168.0.18 192.168.0.7 192.168.0.9 192.168.0.14 > > [recvq] > comment = Fax Receive Queues > browsable = yes > path = /var/spool/fax/recvq > public = yes > writable = no > > Jason > > On Saturday 05 October 2002 18:30, you wrote: > > Hey All, > > > > I'm trying to wrestle this SAMBA thing and while I'm making some progress > > I > > > am not wholly successful. I will outline what I have observed as being > > successful and what I would like to achieve. Any help would be greatly > > appreciated. > > > > I've got my little home network behind a gateway. They belong to > > workgroup MYWORKGROUP (fictitious), each machine has a lowercase name > > consisting of one word (the name of the primary user), each machine has > > at least one read-only share set up. The Winbloze machines can see each > > other fine and can access each other's shares just fine. I have > > successfully gotten my Linux Laptop to show up on the Winbloze Network > > Neighborhood but when I > > try > > > to access it I get prompted for a password that I am unsuccessfully > > entering. > > > > I am trying to use my Linux laptop to see the other (Winbloze) machines > > on the network. I appear to have SAMBA set up and installed correctly. I > > have edited my smb.conf file but I believe that I am missing something > > here. > > > > I would like to be able to see the shares of the other machines from the > > Linux Laptop. I would like the other machines to be able to see the > > shares on the Linux Laptop. Is there any way of setting this up so that I > > don't have to create user accounts for each Winbloze machine? I'm not > > sure how > > to > > > say this... can each incoming machine access the same space (user > > account?) > > > on the Linux Laptop. This is basically how each winbloze machine works > > and it would save me to trouble of setting up accounts. > > > > I am also using LinNeighborhood and it appears to get the other machines > > on > > > the network but cannot see their shares. > > > > I would really like to get this working. I have some files to transfer > > and some of them are rather large. Ultimately I believe this endeavor > > could be useful. Thus far I have avoided SWAT for a few reasons. The most > > prominent is that I want to see what I am doing at the configuration > > level. > > > > Thanks in advance. > > > > Jarrod -- ~~~~~~~~~~~~~~~~~~~~~ Jason Van Dellen Trilogy-Net Inc. #4; 1935 - 27Ave NE Calgary, AB T2E 7E4 www.trilogy-net.com Phone (403) 219-8868 Fax (403) 219-8860 Cell (403) 815-1626 ~~~~~~~~~~~~~~~~~~~~~
