blocked port

James Sutherland jas88 at cam.ac.uk
Wed Jun 7 20:29:00 GMT 2000


On Wed, 7 Jun 2000, Ryan Waldron wrote:
> On Thu, 8 Jun 2000, James Sutherland wrote:
> > On Thu, 8 Jun 2000, Ron Alexander wrote:
> > 
> > > I think I have discovered why many of the tests fail between my server and
> > > my pc.
> > > 
> > > It appears that port 139 is blocked between my server and my PC. I am using
> > > the @home network and VPN. Has anyone heard of this happening before, and if
> > > so, how do you 'fix' it.
> 
> It appears that TCI does this in Birmingham, AL, though it likewise
> appears that @Home may NOT do this here (yet).  Apparently, this is
> their excuse for a "solution" to keep neighbors from inadvertantly
> opening up any shared drives on their PC to all their other
> neighbors.
> 
> Never mind how many legitimate uses it breaks; after all, they're the
> cable company, why should they care?

I can sympathise there; I'm still waiting for cable modems to arrive
(promised in 1996...)

Still, as of February this year, dialup Net access is no longer charged by
the minute. That's a BIG improvement...

> As for fixing it, I don't believe you can change the default ports on
> which SMB works on your Windoze boxen; Samba-to-Samba you can, though.

IIRC, Ron is using an NT box (hence the reference to a Registry...)


James.



More information about the samba-technical mailing list