LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 09-24-2009, 06:40 PM   #1
asuderma
LQ Newbie
 
Registered: Sep 2009
Location: Colorado
Distribution: CentOS 6.2
Posts: 20

Rep: Reputation: 0
Lightbulb Samba visible to windows, but not accessible.


I have tried everything I can think of to get this Samba share working. I originally used the KDE built-in GUI in my Centos 5 distro to configure smb.conf, but that wasn't working so I dove into the command line. Here is my smb.conf file:

[global]

workgroup=funkytown
server string = Welcome to Funkytown

netbios name=asudermaserver

interfaces = eth0 lo
#hosts allow = 127. 192.168.12. 192.168.13.

log file = /var/log/samba/%m.log
max log size = 50
security = user
passdb backend = tdbsam


#============================ Share Definitions ===========================

[homes]
comment = Home Directories
browseable = no
writable = yes
; valid users = %S
; valid users = MYDOMAIN\%S

[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
; guest ok = no
; writable = No
printable = yes


[fileserve]
path = /fileserve
writeable = yes
browseable = yes
valid users = andy




When I try to access the share from windows (map network drive //asudermaserver/fileserve with the correct username and password) I get a Network Path could not be found error. Also, the share is visible in my network connections under the workgroup FUNKYTOWN

Last edited by asuderma; 09-24-2009 at 06:41 PM.
 
Old 09-24-2009, 07:11 PM   #2
asuderma
LQ Newbie
 
Registered: Sep 2009
Location: Colorado
Distribution: CentOS 6.2
Posts: 20

Original Poster
Rep: Reputation: 0
Alright, I figured it out. I disabled IPtables and it worked fine.

Last edited by asuderma; 10-01-2009 at 01:07 AM.
 
Old 10-05-2009, 05:53 PM   #3
Rooth
LQ Newbie
 
Registered: Sep 2009
Location: Colorado
Distribution: RedHat 5, SuSE 10
Posts: 9

Rep: Reputation: 1
What version of Samba was it, and what version of Windows was it linking to? I'm trying to get SuSE 10's Samba 3.0.24 to connect to Windows Sever 2008, and as long as I don't put the server into a domain, it works, but only when I map drives. Just plain browsing doesn't work. And as soon as the server is set up in a domain, it doesn't work at all. I know Samba 3.2.x works with Server 2008, but I'm on the prowl for a simpler solution, as it'll take a while to update Samba on that box.
 
Old 10-09-2009, 11:46 AM   #4
asuderma
LQ Newbie
 
Registered: Sep 2009
Location: Colorado
Distribution: CentOS 6.2
Posts: 20

Original Poster
Rep: Reputation: 0
I'm not sure what version of Samba that was. That machine isn't running anymore. I was using CentOS 5.2 and connecting to XP Pro. I was never really able to browse my smb share either, just able to map the drive. I didn't really have any need to browse to the share.
 
Old 10-09-2009, 12:19 PM   #5
SaintDanBert
Senior Member
 
Registered: Jan 2009
Location: Austin, TX
Distribution: Mint-15 with Cinnamon & KDE
Posts: 1,324
Blog Entries: 3

Rep: Reputation: 86
Quote:
Originally Posted by asuderma View Post
Alright, I figured it out. I disabled IPtables and it worked fine.
iptables is your workstation firewall. You really don't want to leave home without it...

By default, windows file sharing is disabled on purpose. Those protocols
are often the source/cause of malicious mischief. When you open this door, make sure to limit access to your own network LAN.

~~~ 0;-Dan
 
Old 10-09-2009, 12:24 PM   #6
SaintDanBert
Senior Member
 
Registered: Jan 2009
Location: Austin, TX
Distribution: Mint-15 with Cinnamon & KDE
Posts: 1,324
Blog Entries: 3

Rep: Reputation: 86
Quote:
Originally Posted by asuderma View Post
I'm not sure what version of Samba that was. That machine isn't running anymore. I was using CentOS 5.2 and connecting to XP Pro. I was never really able to browse my smb share either, just able to map the drive. I didn't really have any need to browse to the share.
Huge books and hundreds of pages have been written about windows network browsing -- "network places" not web browser. Not only do the several windows variants 95/98/Me/NT/.../XP/Home/Vista have their own individual dance, but the dance seems to change based on which variants you try to make play together. Sigh. You can use the SAMBA configuration to enable most of the variants.

Good luck,
~~~ 0;-Dan
 
Old 10-09-2009, 12:27 PM   #7
asuderma
LQ Newbie
 
Registered: Sep 2009
Location: Colorado
Distribution: CentOS 6.2
Posts: 20

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by SaintDanBert View Post
Huge books and hundreds of pages have been written about windows network browsing -- "network places" not web browser. Not only do the several windows variants 95/98/Me/NT/.../XP/Home/Vista have their own individual dance, but the dance seems to change based on which variants you try to make play together. Sigh. You can use the SAMBA configuration to enable most of the variants.

Good luck,
~~~ 0;-Dan
I suppose I wasn't clear when I used the term "browse." I was referring to network browsing via what used to be called "Network Neighborhood" and what Windows XP refers to as "My Network Places."

Last edited by asuderma; 10-09-2009 at 12:30 PM.
 
Old 10-09-2009, 12:29 PM   #8
asuderma
LQ Newbie
 
Registered: Sep 2009
Location: Colorado
Distribution: CentOS 6.2
Posts: 20

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by SaintDanBert View Post
iptables is your workstation firewall. You really don't want to leave home without it...

By default, windows file sharing is disabled on purpose. Those protocols
are often the source/cause of malicious mischief. When you open this door, make sure to limit access to your own network LAN.

~~~ 0;-Dan
I appreciate the advice. As I stated above, that box isn't running anymore. I didn't really like the way I had it set up (It was rather insecure, partly due to the iptables being disabled). I am running a new box and will be configuring samba a little bit differently.
 
  


Reply

Tags
could, found, network, path, samba, windows


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Samba - Windows XP Problem (//Samba is not accessible) Covenent Linux - Networking 20 08-11-2011 04:07 PM
Samba server visible on network intermittent - shares not accessible - UPDATE neoelf Linux - Networking 1 06-17-2009 02:34 AM
samba + some windows xp hosts not visible in entwork neighborhood massoo Linux - Server 0 04-13-2009 02:42 AM
samba share visible not accessible vinod Linux - Security 2 02-04-2007 11:05 AM
samba server visible for linux but invisible for windows morgwai Linux - Networking 7 08-22-2005 08:40 AM


All times are GMT -5. The time now is 01:59 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration