Samba - Windows client cannot connect to Linux Server.
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Samba - Windows client cannot connect to Linux Server.
I'm having a problem connecting from a Windows client to my home Samba server.
Code:
> testparm /etc/samba/smb.conf
[global]
workgroup = MYGROUP
server string = Samba Server @ dev.neranjara.org
log file = /var/log/samba.%m
max log size = 50
dns proxy = No
valid users = nathacof
hosts allow = 192.168.1., 209.41.163.23
[homes]
comment = Home Directories
read only = No
>
When I attempt to connect from my Windows workstation and enter my password from work I'm getting thrown back to the authentication prompt, whereas from home I can connect with out issue.
My Router has the following ports forwarding to the Samba server:
Code:
Port 135/TCP
Port 137/UDP
Port 138/UDP
Port 139/TCP
Port 445/TCP
root@dev:/var/log# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
root@dev:/var/log#
So since I'm able to connect to the remote server, and it prompts me for authentication, I would assume I'd be able to check the logs for this particular connection.
But when I check the logs for this host they do not exist:
Appears to be. As I said I can connect from home, and it works fine, using that subnet. As a matter of fact it was included in the default smb.cnf file.
The problem is with the connection from the external IP.
I think you should check two issues: external connectivity and sitting of the PC in your work.
1- check the connectivity from work to home. You may enable pinging (ICMP forwarding) in you router or use any other simple services such as apache (port 80). in apache, just add the routing record in your router and try to access it from your work, of course, after testing the apache in your home network. Do you have a firewall at work? Usually, YES. Do the connectivity (tcp ports 139, 445 …etc) to a share folder is allowed? Usually, NO. Is your work connectivity to the internet through proxy or routing? Usually, via proxy. In proxy case, you should check the restriction of the proxy!
2- are you using ms windows active directory in your work? if yes, there are a sitting in the active directory security policy which will prevent some type of connectivity (e.g. file sharing) between the your domain and other domain or even stand alone machine. if your are the admin in your work, i may guide you how to check this sitting.
I highly suggest to try to access your samba from another network rather than your work like internet café. Usually, the PCs there are not part of a domain, there is no firewall, no proxy (routed connection).
Hope that I did not confuse you . I will check your replay to proceed in solving your problem.
Regards,
Yeah I need to speak with my Network Operations team to see if they can open up those ports to our headquarters from my home IP. I've got an Apache Server running already on my home box everything is fine with that.
But fundamentally you guys are right the problem most likely lies with my work's network ACLs.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.