🚀 go-pugleaf

On Thu, 10 Sep 1998 04:25:05 GMT, "Paul Chui" <pchui@yahoo.com> wrote:

>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.

Are you *absolutely* sure of that?  Trevor Fiatal has publicly stated
that they're not blocking any ports.  I don't know if the individual
franchises have the option of doing things their own way or not...

>I can ping the machine's IP address, but can't NET USE it.

That doesn't mean the port is blocked... it's pretty tricky to get NBT
going over the Internet.  I've tried and failed a couple of times...
:-)  The closest I ever got was being able to see a Windows '95
machine over the Internet with NT Workstation 4.0.

Open C:\Windows\hosts.sam with Wordpad or something and read it...
it'll help.

-- 
If you want to reply to me, do it in the newsgroup... It's 
been too long since I've received anything other than spam 
in my mailbox from posting my address in the newsgroups.

>Are you *absolutely* sure of that?  Trevor Fiatal has publicly stated
>that they're not blocking any ports.

I confirmed this with someone I know at the main @Home corp site here in
California. At first, @Home technical support first denied that they were
blocking any ports. Later, they appologized and said that they were blocking
NetBIOS.

Any thoughts on PPTP over the @Home connection. If NetBIOS is blocked, will
PPTP work?

Paul Chui wrote in message <1bUJ1.27$gp1.203202@news.rdc1.sfba.home.com>...
>>Are you *absolutely* sure of that?  Trevor Fiatal has publicly stated
>>that they're not blocking any ports.
>
>I confirmed this with someone I know at the main @Home corp site here in
>California. At first, @Home technical support first denied that they were
>blocking any ports. Later, they appologized and said that they were
blocking
>NetBIOS.


A2000, a Dutch Cable ISP did the same: thank all the Nuke program writers
and users for killing a great service....

Marc du Bois

This is false. I believe the cable modems themselves filter NetBIOS
*broadcasts*, but not NetBIOS ports -- this would explain why you can't see
your @Home 'node-neighbors' in your Network Neighborhood.

I have my y: drive mapped to a shared drive on an NT server (on a different
ISP) via the internet right now... My z: drive is mapped to an @Home
node-neighbor. Like the guy said: check out your lmhosts.sam file and go
from there.

-=Lord Sludge=-

Paul Chui wrote in message <1bUJ1.27$gp1.203202@news.rdc1.sfba.home.com>...
>>Are you *absolutely* sure of that?  Trevor Fiatal has publicly stated
>>that they're not blocking any ports.
>
>I confirmed this with someone I know at the main @Home corp site here in
>California. At first, @Home technical support first denied that they were
>blocking any ports. Later, they appologized and said that they were
blocking
>NetBIOS.
>
>Any thoughts on PPTP over the @Home connection. If NetBIOS is blocked, will
>PPTP work?
>
>
>

In any event broadcasts don't travel past a router/gateway on a subnet
unless special processing (or relay) is provided on the router.

Regards
Tom

Lord Sludge wrote:
> 
> This is false. I believe the cable modems themselves filter NetBIOS
> *broadcasts*, but not NetBIOS ports -- this would explain why you can't see
> your @Home 'node-neighbors' in your Network Neighborhood.
> 
> I have my y: drive mapped to a shared drive on an NT server (on a different
> ISP) via the internet right now... My z: drive is mapped to an @Home
> node-neighbor. Like the guy said: check out your lmhosts.sam file and go
> from there.
> 
> -=Lord Sludge=-
> 
> Paul Chui wrote in message <1bUJ1.27$gp1.203202@news.rdc1.sfba.home.com>...
> >>Are you *absolutely* sure of that?  Trevor Fiatal has publicly stated
> >>that they're not blocking any ports.
> >
> >I confirmed this with someone I know at the main @Home corp site here in
> >California. At first, @Home technical support first denied that they were
> >blocking any ports. Later, they appologized and said that they were
> blocking
> >NetBIOS.
> >
> >Any thoughts on PPTP over the @Home connection. If NetBIOS is blocked, will
> >PPTP work?
> >
> >
> >

On Thu, 10 Sep 1998 16:37:17 GMT, dont.reply@this.address (John
Oliver) wrote:

>On Thu, 10 Sep 1998 04:25:05 GMT, "Paul Chui" <pchui@yahoo.com> wrote:
>
>>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.
>
>Are you *absolutely* sure of that?  Trevor Fiatal has publicly stated
>that they're not blocking any ports.  I don't know if the individual
>franchises have the option of doing things their own way or not...

On 7-16-98 Trevor Fiatal posted the following:

        Nope.  No filters on customer IP space except the NetBIOS 
        ones on the individual cablemodems to avoid problems with
        folks exporting their entire hard drive to the Internet.

        -Trevor

I saved the message :- )

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?

That's NetBEUI.  NetBIOS is routable.

In article 
<E0515B57C5CBF507.B67A44DC214AB91B.45A0A3BA1FF14C6C@library-proxy.airnews.net>, 
loge@valhalla.org says...
>
>
>That's NetBEUI.  NetBIOS is routable.

Bzzzttt! Niether is routable. The only way to route this stuff is to 
encapsulate the packets in TCP/IP. The only other way to get this stuff to 
another segment is to bridge the protocol through your router. (but then you're 
not routing).

MikeM

NetBIOS is a programming interface for network communication. BetBEUI is a
non-routable protocol for transport, used exclusively with NetBIOS based
networking.

When you remove NetBEIU, NetBIOS name resolution and carried on via TCP/IP or
IPX/SPX.

I understand that NT 5.0 Server and WS will allow for the elimination of
NetBIOS entirely, providing all services via Windows Sockets (the other
Windows programming interface for locating and talking to remote computers).

In article <6tsbjl$h7t$1@as4100c.javanet.com>,
  mandulak@mail1.nai.net (Mike Mandulak) wrote:
> In article
>
<E0515B57C5CBF507.B67A44DC214AB91B.45A0A3BA1FF14C6C@library-proxy.airnews.net>,
> loge@valhalla.org says...
> >
> >
> >That's NetBEUI.  NetBIOS is routable.
>
> Bzzzttt! Niether is routable. The only way to route this stuff is to
> encapsulate the packets in TCP/IP. The only other way to get this stuff to
> another segment is to bridge the protocol through your router. (but then
you're
> not routing).
>
> MikeM
>
>

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum