> Hello all ....
> I am connected to the internet through a dialup-modem connection to an ISP.
> this ISP gives its users dynamical IPs (non routable and it is applying
> NAT).
> I installed microsoft network client because I used to use windows shares on
> other users' machines (friends). this is done by doing a scan on netbios
> ports on the ips of those machines 10.0.0.x .
> I used to find dosens of machines with windows shares.

10.0.0.x is a reserved range of IP address for internal networks. Which
means that your ISP is very strange and doing NAT (like you said).

> suddenly, it's been several days, I can find no more machines with shares
> ....!! the scanner gives nothing. I thought it's a problem with my ms
> network client, so I reinstalled it. Still nothing ...
> I even used "nbtstat -A 10.0.0.x" from a DOS prompt for some IPs within that
> scope, but it gave " host not found ". But it gave something when I used it
> for my IP ......

nbtstat only shows current connections over NetBIOS. It won't find
anything for you.  Since your scanner isn't giving you anything nbtstat
won't give you anything either because there's nothing to connect to.

> To be more sure, I called a friend that I used to have access to his shares,
> and I asked to him to connect. We made a chat and he gave me his actual IP,
> so I made that nbtstat to his IP. But it gave "host not found". He was sure
> that his netbios ports (137-139) was opened and listening.
> By the way, he couldn't neither see me with that "nbtstat -A myIP".
> What could the problem be ?? I don't understand....I am a real newbie

try doing a "ping *.*.*.*" to see if you can actually reach his computer.
Again, typing nbtstat with his his IP address won't show anything because
you aren't connecting to it.

> Can the ISP do something to prohibit the access to windows shares between
> machine weithin it's local network ???????????? how can this be done ???

They could possibly block the NetBIOS ports (although that is somewhat
unlikely since everyone scans NetBIOS).

@llenn

Reply via email to