Dear Pascal,
what if your ISP blocks ports 137-139 by default or if your
cable modem/dsl modem has a build-in filter which drops
connections to that ports? Have you thought about that?
Since you get a successfull response from the internal
network your services seem to run fine. Check your modem
first to see if there is a filter. Alternatively to
telnet you can use
nmap your_ext_ip -p 135-139
to see if there is a response and if you see someth like this:
135/tcp filtered loc-srv
137/tcp filtered netbios-ns
138/tcp filtered netbios-dgm
139/tcp filtered netbios-ssn
it means there is something filtering....
Hope that helps.
Cheers,
Monzai :-)
If you have a lot of samba-machines and you configure them
with swat then you must use Monzai! Ok, you don't have
to, but once you use it, you'll love it! Have look at the
live-demo at
http://www.monzai.com/
crabouif wrote:
> Srange...
>
> I have a server (SuSe 8.1) vith 2 network card.
> - eth0 on dhcp cable external network
> - eth1 on internal network with fix address 192.168.0.1
>
> Samba is running and work fine on local network. But when I try to
> acess Samba from external computer, no response, like Samba is not
> listening on eth0...
>
> This is not the firewall because I try with firwall stopped, and I
> open 137:139 port...
>
> In my tests, I try with telnet:
> - telnet 192.168.0.1 139 -> From internal, work fine
> - telnet my_ext_ip_address 139 -> From external, no response (time
> out)
> - telnet my_ext_ip_address 80 -> From external, work fine
>
> And that with or without firewall...
>
> I'm not understanding...
>
> Anyone help me, thanks.
>
> Pascal
Similar Threads
Linear Mode
