[Samba] browse ntfs files from *nix

2003-02-07 Thread pippo
I am not quite clear on how to browse windows files from FreeBSD.
I have found two possibilities - sharity-lite and smbclient for Win32. 
However, I have no idea of how to use smbclient for Windows. My setup is 
FreeBSD 4.7 with Samba installed and working well. I can access kFBSD from 
WinXP  other machines with no problem.
But how do I read files on Windows? Google wasn't much help... :((
Thanks in advance.
PJ


--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Win files from *nix?

2003-02-07 Thread pippo
At 05:17 PM 2/7/2003 -0700, you wrote:

You should be able to use smbclient (command line only) it will give you
an ftp style interface.


On the FreeBSD machine?
PJ



Kevin

On Fri, 2003-02-07 at 17:05, [EMAIL PROTECTED] wrote:
 How can I browse Windows from Unix?
 I'm using FreeBSD 4.7, Samba, and KDE3. I'd like to be able to browse also
 from command line.
 I have not found instructions on use of smbclient-win32 and do not want to
 use sharity. smbclien-win32 comes with and exe file and cygwin dll's - but
 what are you supposed to do with them, copy the dll's to system or 
system32
 foler and just run the exec? and then what?
 I don't care if I sound stupid, but surely somebody could suggest where to
 find the information? Google was of no help. :((
 Thanks,
 PJ


 --
 To unsubscribe from this list go to the following URL and read the
 instructions:  http://lists.samba.org/mailman/listinfo/samba


--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba



[Samba] Win files from *nix?

2003-02-07 Thread pippo
How can I browse Windows from Unix?
I'm using FreeBSD 4.7, Samba, and KDE3. I'd like to be able to browse also 
from command line.
I have not found instructions on use of smbclient-win32 and do not want to 
use sharity. smbclien-win32 comes with and exe file and cygwin dll's - but 
what are you supposed to do with them, copy the dll's to system or system32 
foler and just run the exec? and then what?
I don't care if I sound stupid, but surely somebody could suggest where to 
find the information? Google was of no help. :((
Thanks,
PJ


--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] xp problem

2002-12-23 Thread pippo
At 08:27 PM 12/21/2002 +, you wrote:

Pippo,

We will need more information than this to help you. Please explain in
detail what happens when you try to access the WinXP machine from Win2K
and vica versa.

You need to explain how your samba is configured as well as how the
Win2K/XP systems are configured. Without this information we would be jst
guessing - not very productive.


Sorry, but I don't quite understand. I thought I had explained my setup 
fairly concisely. The Win2k and XP boxes are configured for workgroup file 
and printer sharing. There is no domain or domain server.
FBSD is running samba as a file and printer server. I can only see the XP 
machine in My Network Places and the samba connection to the FBSD machine.
When FBSD is running, I can connect from the XP machine both for file and 
printer access. When I try to connect to one of the other computers in the 
workgroup, I get the message: the path could not be found.

Perhaps I am not clear enough: Before installing XP_Pro, I was able to see 
and connect between Win2K machines as well as the FBSD both for file 
shareing and printing. After installing XP, I can ping between the 
machines, I can map to the shares, I can print from the XP but I can no 
longer see the machines in the WORKGROUP on Network Neighborhood or Network 
Places (Childish nomenclature by MS).

If I disconnect FBSD from the LAN, the Windows machines can, once again, 
intercommunicate.

Perhaps I should dump the NetBEUI protocol on Windows and just map the 
shares on each machine. (Kindof a pain, IYAM)

Maybe I just don't understand what the relationship should be between the 
samba machine and the others.

The static address (192.168.1.240) of the FBSD machine show up as 
WORKSTATION and not as COMPUTER_NAME.

If I may make an observation, it looks to me that MS is getting 
kprogressively bloated an unecessarily complicated as it evolves. I am 
trying to get away from it as much as possible but that is a little 
difficult as too many common people are still brainwashed by MS.

Please let me know  what specifics I should provide. I have been searching 
the documentation and the HOW_TO's with little success.

Pippo

On Sat, 21 Dec 2002 [EMAIL PROTECTED] wrote:

 I would appreciate it if someone can point me in the right direction.
 I am having a problem connecting to other computers on my LAN.
 Configuration is this:
 1. XP machine, 2 Win2K's, 1 FreeBSD running Samba (current or latest 
version).
  From XP, I can connect and read/write and print to FBSD but cannot connect
 to Win2k's.
 Win2k's cannot connect to XP.
 I suspect it has to do with the domain master and the os level settings
 for, when the FBSD machine is off, connections between XP and Win2k are ok.
 What do I have to to to be able to connect to Win2k's at the same time as
 the FBSD (Samba)?
 I am not running a domain, workgroup only. :))
 Thanks in advance,
 Pippo


--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba



[Samba] xp problem

2002-12-21 Thread pippo
I would appreciate it if someone can point me in the right direction.
I am having a problem connecting to other computers on my LAN. 
Configuration is this:
1. XP machine, 2 Win2K's, 1 FreeBSD running Samba (current or latest version).
From XP, I can connect and read/write and print to FBSD but cannot connect 
to Win2k's.
Win2k's cannot connect to XP.
I suspect it has to do with the domain master and the os level settings 
for, when the FBSD machine is off, connections between XP and Win2k are ok.
What do I have to to to be able to connect to Win2k's at the same time as 
the FBSD (Samba)?
I am not running a domain, workgroup only. :))
Thanks in advance,
Pippo


--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


[Samba] incomprehesible quirk

2002-12-10 Thread pippo
I am really quite puzzled as to why I have to edit smb.conf every time I 
want to print to the FreeBSD machine from Win2K. (Running FBSD 4.7, samba 
2.2.7 and cups 1.1.15.1_4.
When I log onto FBSD with username, password, I see the folders for the 
printers, home, tmp, etc. but no printer. (Only 1 installed - Epson Stylus 
Color 900).
I can access the shares on FBSD from Win2k, but there is no printer.
If I edit smb.conf, with insignificant changes not affecting the printer 
sections (Printers and Print$) the printer appears.
As a side note, I think that the Printer$ section may not be needed if I do 
not install any Windows or other special drivers - frankly, I don't know 
why it is even there :((
 It appears that editing smb.conf forces the smbd program to reread the 
smb.conf file. But why would it not have read it correctly in the first place?
Anyone out there understand this?
thanks in advance
PJ


--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] incomprehesible quirk

2002-12-10 Thread pippo
At 07:51 PM 12/10/2002 -0500, you wrote:

You could just kill sighup smbdprocessid
On linux it is kill -1.


Why would I do that?
The machine is running, smbd is running; I just want to log on and print. :))
I don't want to go through the contortions of shutting a process down and 
then restarting it just to do a simple function (printing).

You might post your smb.conf.
Have you run testparm?


Of course, I did. :))
As a matter of fact, I even deleted the [print$] section in my latest edit 
and print saga...

I'll post the smb.conf file tomorrow. It's been too long a day...
PJ


Joel


On Tue, Dec 10, 2002 at 06:45:44PM -0500, [EMAIL PROTECTED] wrote:
 I am really quite puzzled as to why I have to edit smb.conf every time I
 want to print to the FreeBSD machine from Win2K. (Running FBSD 4.7, samba
 2.2.7 and cups 1.1.15.1_4.
 When I log onto FBSD with username, password, I see the folders for the
 printers, home, tmp, etc. but no printer. (Only 1 installed - Epson Stylus
 Color 900).
 I can access the shares on FBSD from Win2k, but there is no printer.
 If I edit smb.conf, with insignificant changes not affecting the printer
 sections (Printers and Print$) the printer appears.
 As a side note, I think that the Printer$ section may not be needed if 
I do
 not install any Windows or other special drivers - frankly, I don't know
 why it is even there :((
   It appears that editing smb.conf forces the smbd program to reread the
 smb.conf file. But why would it not have read it correctly in the first 
place?
 Anyone out there understand this?
 thanks in advance
 PJ


 --
 To unsubscribe from this list go to the following URL and read the
 instructions:  http://lists.samba.org/mailman/listinfo/samba


--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba