Howdy folks,

Just set up Samba, and something odd is happening. From my Win98 box, I can see my Linux box (Localhost - lame name, I know) in Network Neighborhood. But when I click on it, I get the message:

\\Localhost is not accessible.
The computer or sharename could not be found. Make sure you typed it correctly, and try again.

I can ping it, and I can ping the 98 box from the Linux box. But I don't even get a password prompt from Network Neighborhood when trying to access the Linux box.

Ideas?
Thanks,

)M.

Did you start the Samba server, under the status menu you have to start the smbd and nmbd server. That sounds like the message I get when Samba is not running.

If you can see the servername listed on your Net 'Hood then smb is running.

Did you add users to smb (smbpasswd -a -U username) --> required for user level access.

What kind of service have you setup on the smb server? (share/user/server)

Have you set up any shares on the server? Do they have the correct access controls on both the smb.conf and unix permissions.

The domain name whould be the same as the workgroup name. This can all be changed in Network Neighborhood properties. You also have to set up the Microsoft network client.

You only need to set up the "Client for Microsoft Networks" and the TCP/IP protocol. If you can see the server name (the NetBIOS name) in your Network Neighborhood window then you've already got it. You don't need to set up "File and Printer Sharing" as that is only needed to share files + printers _from_ the Windows client.

Howdy and thanks for the quick replies!









In response to your questions and suggestions:









* Samba is running the SMB and NMBD services. When I start Samba from a command line, they both startup "OK"









* The Domain and Workgroup name are the same on the Windows box.









* The Microsoft Network Client is setup as the default login. (This computer used to be on a Windows network).









* TCP/IP is setup correctly on the windows box for the adapter. Both Windows and Linux are on the same subnet and use the same gateway.

The windows ip is 173.111.111.113 and linux is 173.111.111.112






When I use 'smbclient -L localhost I get:



_______________

SSL: Error setting CA cert locations: error: 00000000:lib(0):func(0):reason(0)

trying default locations.

added interface ip=173.111.111.112 bcast=173.111.255.255 nmask=255.255.0.0



Domain = [WORKGROUP] OS=[Unix] Server=[Samba 2.0.7]



Sharename / Type

--------------------------

homes / Disk

tmp / Disk

/mnt/zip100.0 / Disk

IPC$ / IPC



Server

---------

LOCALHOST



Workgroup

---------------

WORKGROUP



______________________________



And here's my configuration file:

______________________________

# Global parameters

[global]

encrypt passwords = Yes

log file = /var/log/samba-log.%m

max log size = 50

dns proxy = No

wins support = Yes

comment = Red Hat Samba Server

hosts allow = 173.111.111.113/255.255.0.0

strict locking = Yes

volume = Red Hat 7.1



[homes]

comment = Home Directories

path = /home/matt

guest account = matt

writeable = Yes

create mask = 0750

guest ok = Yes

strict locking = No



[tmp]

comment = Temporary file space

path = /tmp

writeable = Yes

guest ok = Yes



[/mnt/zip100.0]

path = /mnt/zip100.0

guest account = matt

writeable = Yes

guest ok = Yes

strict locking = No



_______________________



Another weird thing is happening. On the Windows box, when I go to Network Neighborhood, I initially don't see the linux box. But then I ping it, and it's there!



But I still get the same message: //Localhost not accessible.



Been toiling at this on and off all week... Needless to say any new insight is much appreciated!!!



)M.

I don't know if you confirmed it or not, but did you set up an encrypted user password on your linux box? If no, windows is sending a hashed p/w and linux isn't reading it. Be sure to run where <username> is the login name from your windoze box and the password matches. Restart the daemons and you should be able to connect.

this is my smb.conf. All I can say is,...remove everything from the file and use ONLY what you need. This is what I used to get mine working,.........finally,....lol

Your 'hosts allow' is a little on the funky side. If you want the entire subnet to see it, you should use 173.111.0.0 255.255.0.0 as the bitmasking will be, well, different. I'm too lazy to find it right now, but if you look through the Net2 HowTo you should be able to find the netmask section. Have a look.

A 'netbios name' for your server might help windows see the server.

If you have 'win support = yes' then you might also want to add ' name resolve order = wins lmhosts host bcast '

Gotta run - We're having a garage sale and it's super busy!

Thanks for all the posts - even while having a garage sale! Hope it went well. I've worked at many a garage sale that's gotten out of hand and gave me nightmares about haggling with the oddest of people.

If anything, I'm learning a lot about my system, but still no luck with an actual connection to Samba from my Windoze box. (//BigRed not accessible...)

Here's the latest:
GATEWAY (windoze):

*There's a dail up TCP/IP, which I don't touch.

*The Ethernet TCP/IP settings are:
IP: 192.168.1.2
Sub: 255.255.255.0
Wins: 192.168.1.1 (Linux)
No Gateway or DNS are defined, since it didn't seem to help any.

*The login I use is the same as my main LInux user (non-root).

*Network neighborhood will sometimes show the linux box (I successfully changed the hostname to BigRed), and other times it will not show it, and only show Gateway or say that the network is not browseable. It seems to mostly show BigRed after a reboot. Then if I close the NN window and reopen it, there's either nothing except the Entire Network icon, sometimes joined by Gateway.

*I added BigRed to the C:/Windows/host.sam file, and also created an Lmhosts.sam file:
192.168.1.1 BigRed #PRE
But this doesn't seem to matter as I can only ping BigRed by IP, and not name.

BIGRED (linux):
*Active Interfaces:
lo 127.0.0.1
eth0: 192.168.1.1
No default Gateway or Device specified.

*smbpasswd file:
matt:500:long encrypted password

*For the smbusers file, I added the last line as an experiment, which didn't help:
root = admisitrator admin
nobody = guest pcguest smbguest
matt = smbuser user

*Hosts file:
127.0.0.1 BigRed.localdomain
192.168.1.1 BigRed
192.168.1.2 Gateway (Windoze)

And lastly, here's my smb.conf file:

# Global parameters
workgroup = WORKGROUP
server string = Samba SMB Server
security = share
encrypt passwords = yes
ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt
wins support = yes

[public]
comment = public
path = /home/public
read only = no
guest ok = yes
public = yes

[data]
comment = Data
path = /home/samba/data
read only = no
guest ok = yes
public = yes

___________________

If you've read this far - Thank you! I"ve been banging my head against the wall for most of my weekend (some weekend!)

Any help is much, much, mucho appreciated.

)M.

So get this,

I added 255.255.255.1 as the gateway on both computers.

I can use the :

smbclient "\\\Gateway\\d"

command and samba over to the shared drives on my PC, no problemo. But, I still get that damn message from Windoze when trying to log onto LInux. What gives?

)M.

At risk of insulting you...
1 Setup network.... ping your localmschines
2 Setup Samba ..... see yourlocalmachines
3 Setup NAT via IPTables i.e. minimum
echo =1 /proc/sys/net/ipv4/ipforward
or something like that.
There are multiple posts on these boards about NAT and I don't have access to my RH machine to tell you exactly what you need to type, but that's nearly it!
Jim

I've removed the gateway, since it was causing problems with the modem and isn't needed on my little LAN, as I found out.

*******************************************

For those of you following this thread, I've started another one called:

Dualing Browse Masters?
Which is here:
http://www.linuxquestions.org/questi...&threadid=6127

And the adventure continues...

)M.

ps. Picked up Craig Hunt's Samba Admin book. It's great and well written (a rarity in computer books), and I'm learning a ton, but still no resolution on this particular problem.

I had the same problem for many days and many hours. (Yes, I'm a newbie to linux.) I even bought that Craig Hunt book. Today, I determined myself to fix it and found out that my ipchains firewall was configured to disallow all inbound connections except a few. I'm running redhat 7.1, and I configured the firewall when I installed it.

Here's my updated /etc/sysconfig/ipchains file:

# Firewall configuration written by lokkit
# Manual customization of this file is not recommended.
# Note: ifup-post will punch the current nameservers through the
# firewall; such entries will *not* be listed here.
:input ACCEPT
:forward ACCEPT
:output ACCEPT
-A input -s 0/0 -d 0/0 22 -p tcp -y -j ACCEPT
-A input -s 0/0 -d 0/0 80 -p tcp -y -j ACCEPT
-A input -s 0/0 -d 0/0 21 -p tcp -y -j ACCEPT
-A input -s 0/0 -d 0/0 139 -p tcp -y -j ACCEPT (***added***)
-A input -s 0/0 -d 0/0 139 -p udp -y -j ACCEPT (***added***)
-A input -s 0/0 -d 0/0 901 -p tcp -y -j ACCEPT (***added***)
-A input -s 0/0 -d 0/0 -i lo -j ACCEPT
-A input -s 64.79.64.4 53 -d 0/0 -p udp -j ACCEPT
-A input -s 64.79.64.5 53 -d 0/0 -p udp -j ACCEPT
-A input -s 0/0 -d 0/0 -p tcp -y -j REJECT
-A input -s 0/0 -d 0/0 -p udp -j REJECT

I added the three lines to enable samba on port 139 and swat on port 901 and it worked.

Shailesh