• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 429
  • Last Modified:

Mac OS X to Ubuntu SMB connection fails from 1 IP address only

I have a cloud based Ubuntu 10.10 server running smbd for a single shared directory. I am Linux n00b, but have successfully installed SMB and several other services.

I can connect perfectly to it from any location except my home IP address. argh. Using my Mac laptop from another Internet connection works fine. So I know it is not an issue with the laptop.

Connecting from any machine behind my public IP address fails.

Here is what does work from the machines that can't connect to the samba share :
• SSH into the server
• Ping server
• resolve host name
• ftps into server

There are no firewalls in place on either end. I can also connect to a SMB share I have running on a Mac server here in my office remotely so I know that my ISP is not blocking port 139 at all. I have also confirmed with the cloud server host that they are not performing any filtering.

There are no allow.hosts or deny.hosts entries.

I am at a total loss as to why just connections from my IP address on multiple computers would not work.

Is there some kind of max connections or max failed attempts in a configuration file that would cut me off?
  • 4
  • 3
1 Solution
Have you tried connecting from the Linux server via SMB to one of your macs on your local LAN?
You don't have a firewall rule forwarding SMB traffic through your firewall to a specific address do you?  Have you ever had a remote connection into your LAN for SMB traffic?
Just re-read your post and you already answered the SMB question...

How are you doing authentication both ends?
MazarothITAuthor Commented:
Thanks for your idea Roy.

I have not tried to make a connection from Ubuntu server to my Mac Server here at the affected IP address ( home office )

I'll try that next.
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

MazarothITAuthor Commented:
Authentication is handled by smbusers mapped to ubuntu users.

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
   security = user
   username map = /etc/samba/smbusers

I don't think its an authentication issue though, works everywhere else...
MazarothITAuthor Commented:

F-ING COX. blocking outgoing 136-139 and 445. Even after they told me there was no filtering on the phone.

...as Sherlock Holmes surmised; once you eliminate the impossible, what ever remains, no matter how improbable, must be the truth.. .. :) or something like that :p
MazarothITAuthor Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now