Mark Saunders wrote:
> Hey
>
> Thanks to everyone for the repsponse. It's cool to start an
> interesting thread and get all the penguin people talking! Samba is a
> good thing in that it extends our scope but it is treated with some
> antagonism by the other side of computerdom. I just want it to work
> and be transparent and be able to move stuff around by little home
> network. I am determined to fix it in place rather than the using
> Windows way which is to start removing things and re-installing them,
> only to eventually find you have to re-install Windows. Some fun. I
> should be able to fix this.
>
> To answer several replies I am not using the Linux box as a wins
> server. Everything is tcp/ip and the windows boxes do not have netbios
> enabled (Ms's netbios protocol). I am using host files for the names
> and fixed 192.168.1.1... addresses on a home private network.
>
> The l-box server name is being broadcast and is being picked up by
> Windows Network neighborhood but when I try to access that share name
> Windows reports it cannot find it. The samba log shows no sign of a
> connection attempt. I am getting computer or share not found rather
> than access denied. I think I could probably logic that one out.
>
> I can access the windows box from smbclient - works every time.
>
> I cannot ' Net Use' form the Windos box - I get the "share not found'
>
> I have tried querying the netbios name and the Ip address with the
> same result.
>
> Here is my smb.conf. sandor is my Linux box's network name.
>
> # Samba config file created using SWAT
> # from localhost (127.0.0.1)
> # Date: 2002/04/30 21:00:08
>
> # Global parameters
> [global]
> workgroup = SAUNDERSHOUSE
> encrypt passwords = yes
> server string = Sandors Linux Box
> netbios name = sandor
> preserve case = no
> log level = 100
>
> [homes]
> guest ok = yes
> browseable = yes
>
> [sandor]
> comment = Sandor's Share
> path = /home/sandor
> read only = No
> guest ok = Yes
>
> [kelly]
> comment = Kelly's share
> path = /home/kelly
> read only = No
> guest ok = Yes
>
> I am offering up two shares on the Linux box.
>
>
> If I can't get it to to Samba I'll probably bring the pair of boxes
> over to the Tampa meeting next week. It could be educational.
>
>
> Thanks again for the help.
>
> Mark Saunders
> msaunder@tampabay.rr.com
>
>
>
> Mikes work account wrote:
>
>> can you post your smb.conf file so we can look at it?
>> Michael C. Rock
>>
>>
>>
>
man samba-server, after installing it. Linux does not peer-to-peer well to Windows boxes. Also, make sure you have holes in your server "firewall" for this, please.
You are going, for security reasons, to probably need to tell Linux it is to act like a server with the server IPs in hosts.allow unless you want a range in hosts.allow I think the builtin firewall may be playing with you. Linux is a formal client-server networking O/S primarily, and setting up secure and limited peer-to-peer is HARD.
At a guess, this sequence is part of what is happening:
Linux, with the SAMBA client installed, can access remote hosts (your windows shares), but without the server half of SAMBA installed, it cannot return the favor to Windows boxes. So, looks like you either have only the client installed, and\or the firewall is blocking incoming requests to data.
Client fetches only, server sends out in response to remote request, or accepts incoming changes and validates.
Two-chunk puzzle, looks like I have half of the puzzle here.
John.
-- _______________________________________________________________________________ Registered Linux User #276212, Machine #158988 "Use what works best for your needs, at minimum total cost of ownership."
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:25:31 EDT