Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(ASCEND) WinNT remote access

Hi,

sorry for getting back to an old topic... (or am I just weeks ahead of
the next re-occurence of that ever-new topic :-)


On Wed, 20 May 1998 11:11:34 -0400, Maryann Sheehan wrote:

<snip>

>  I have been able to
> successfully connect to Windows NT servers and "browse" Network
> Neighborhood with WINS configured on the Ascend.  We have a typical Windows

...WINS? I thought there is only DNS available on ASCENDs...

> NT company installation where we have lots of NT servers all over the place
> and noone quite knows how they "work".  I am in no way an NT expert and am
> doing my best to try to get our Max to accomodate the remote community.  I
> am getting the feeling the netbeui is something that we do not want and
> have turned bridging off on our Ascend.  I'm wondering how others are
> configuring their Ascends for NT use.


I am routinely monitoring NT networks I have installed with customers
using a Pipeline at my office and the customers' MAX. But I _never_ use
bridging. With us, ISDN line usage is billed on a per minute basis, and
with bridging it would never drop anymore.

The "trick" is to always install TCP/IP together with NetBEUI on NT
hosts. NETBIOS packets are then packaged into IP packets and are thus
_routeable_. MS calls that NBT. 

It really works. Whenever I do a "net use X: \\remotehost\someshare" the
router dials out and routes IP traffic to the WinNT host.

Of course one could drop NetBEUI altogether. It depends on the network
applications your users use. For Netscape, email and ftp only TCP/IP is
used. For mapping drives, reading remote registries, remote printing,
monitoring remote ArcServe installations etc. etc. it takes NetBEUI.
Drive mapping could be done using a NFS client which is not included in
WinNT.

Many of my customers do not want to choose - they will use whatever
application is more convenient. And you needn't choose either.

On the remote side the user should use either the LMHOSTS file or the
Pipeline's local DNS to avoid routine lookups.
And a last caveat: you should modify the remote's registry to extend the
browsing interval from default 12 minutes to, say, 1 day. You'll
partially lose the browsing capability as the browsing tree is
out-of-sync for at most 24 hours. But you still can use "map network
drive" from Explorer or the command line by entering the full UNC. As
with the Net, browsing is for people who are still searching :-)


Just my .02 c.


Best regards,

   Wolfgang

_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
                         B  E  N  E  I  C  K  E
                               EDV-Beratung
________________________________________________________________________
        Netzwerk-Design - 3Com Solution Partner
           ISDN Remote Access - ASCEND Vertrieb
              DIGITAL Partner PC-Systeme und Server
                 ApplePoint
                    Windows NT-Netzwerke
                       Workstation Memories and Storage Solutions

Dr. Wolfgang Beneicke                                 fon +49-6223-48126
Fasanenstrasse 16, D-69251 Gaiberg                     fax +49-6223-5708
...near world famous Heidelberg, Germany
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>