🚀 go-pugleaf

drag.
I went through incredible hell trying to figure this out as a newby.

this is common among ISP's.
seems to me especially so with BSD implementations, as aside.

it may be done in both directions or just one.
what's interesting is, if you have port 139 blocked inbound but not
outbound, people outside can still see in to you (but you cannot see them,
peals of sardonic laughter)

The claim is that this block prevents win-nuke. 
Brief test on such a connection let me win-nuke my machine anyway. Hmmm.
I suspect it's more bandwidth issues.

To verify what you're dealing with, telnet in each direction to port 139 on
a win machine.
Samba listens thusly as well, but you need to know that it is listening
normally.
Also it seems to respond differently, so use win machines if you can.

telnet <winMachine> 139

If the port is not blocked, a session will establish.
It will stay up but display nothing, if you type nothing.

If you  touch any key (that I know of) at that session , it will
immediately close the session and give you back what appears as five
non-printing characters. 
I think I once knew the bytes but have forgotten; the last one I think will
come up as some kind of weird f in some fonts (did you say
"simple-minded"?)

If the port is blocked, the session will fail to establish itself and error
to your telnet client very quickly.

So, you most likely have to telnet in to your machine from outside to
verify. 
But it's nice to know if it's in both directions or just one, as,
lumberjack-judging-a-man-as-he-swings-an-ax, it might reflect on the ISP's
commitment for disallowing the little children luser customers from doing
That Which Is Wrong.

I feel this is a very big important issue.
I hope other people feel the same. I'll bet you do.

NOTE; last I checked, AOL of all people were NOT blocking; net use away.


I have tried to come up with ways around this but haven't found anything.

Port 139 seems to be a sacred cow written in stone in ms.
If there is a way to move the service to another port, my guess it's arcane
or more likely at the programming level. Do tell, folks.

The change would also have to be implemented on both machines.
Samba appears to have that port be configurable, haven't tried.

But that is unlikely to help you run VS on your home machine.

"Solution": Please complain to your ISP, and get others to do such if you
can (grandiose cause music)

I did to my ISP, and he was non-committal on the phone, not absolutely for
or against unblocking.


One day while hacking around, I got out to a machine!
I thought I had uncovered the most wondrous hack (slide whistle note slides
up)!
But it turns out the ISP had stopped blocking (slide whistle note slides
down)
Smug-ness rush had been in vain.

But, life changed for the better; I was now able to administer all kinds of
things at work from home, yay (slide whistle morphs to shakuhachi and plays
airy, sparse, philosophically-enhancing melody)


-- 
All this and no job
Leave nospam in Reply To. Yes, works.

: I am trying to access a Windows share on my company's computer through my
: cable modem at home. The touble is my provider, @Home, filters out
NetBIOS.
: I can ping the machine's IP address, but can't NET USE it.
: The application that I'm trying to use (Visual SourceSafe) requires that
the
: folder appear as a Windows share. What can I do to access that machine?