Samba in internet

[The Archimage]

Your ISP may be filtering those ports for security purposes.  Ask them
if that's the case.

BTW - it is an awfully bad idea to allow your Samba box to be available
from the Internet.  I'd suggest a VPN solution.

The Archimage
-- 
It is by caffeine alone I set my mind in motion, 

It is by the beans of Java the thoughts acquire speed, 
	the hands acquire shaking, the shaking becomes a warning.

It is by caffeine alone I set my mind in motion.
	-- with apologies to Frank Herbert


George Schindler wrote:
> 
> Hello all,
> can you help me please with one thing. I have alredy setup samba server in
> our office and everybody can go there by \\server_ip_address\folder and now
> I try to setup it so, that everybody from another location in internet will
> be possible to connect to our server (server has internet ip address, and
> private ip adress too for our office and ftp works there good). But when I
> try from another location on internet connect to this server by smbclient
> //server_ip/public -I server_ip -W workgroup it responds like this:
> Connecting to xxx.xxx.xxx.xxx at port 139
> error connecting to xxx.xxx.xxx.xxx:139 (No route to host)
> Connection to xxx.xxx.xxx.xxx failed
> Of course I can ping there, make ftp connections and so on, after this I
> tryed to nmap this server from another location than our subnet and I get
> information that ports 136-139 are filtered, but ipchains and ipfwadm is not
> there ...
> Can you help me please.
> Thanks
> George