RE: Network Computers

[Bill Farrell <billfarr ages com>]

Matt:

Thanks for the tips.  I'll look in the Netscreen to see if it can be
convinced to pass broadcast packets along the VPNs.  You're right:  even
with the bandwidth hit, it's better than manually maintaining the LMHOSTS
files.  Been there, done that and it's a nasssssty job :-)~~

My office is sitting on a 5Mb wireless connection to the 'net and the NL
office has a 1.5Mb down, so in relation to what we're already passing back
and forth, the additional load shouldn't be that great an impact.  At home
there are only 3 workstations on a 1.5Mb downlink, so I'm not going to worry
about soaking up bandwidth there much, either. :-)

I haven't seen anything in the Samba docs about replication, but then again
I haven't looked that closely.  (It wasn't an issue up until now.)  I'll
take myself over to the samba.org site and have a nice, long study.  If
necessary (Goddess help me) I can always throw WINS back on the NT
servers--I KNOW they'll push/pull with minimal encouragement.  I must say,
though, that a Windoze network works SO MUCH more smoothly with Linux/Samba
running it :-)

Cheers!
Bill Farrell
Webmaster
http://www.ages.com
http://www.vaspartsonline.com

************

Please visit us at www.vaspartsonline.com for quotes, order updates,
specials, AGES / Volvo Aerospace general information, and related aviation
news.

All price quotations are provided for information purposes only and are
subject to change, prior sale, lease, or removal from the market of the
material quoted, without prior notice. Any contract for purchase of material
is expressly conditioned upon buyer`s acceptance of AGES` terms and
conditions of sale. Any material sold and shipped to a Customer, and/or
resold and shipped (to a third party, etc.), MUST comply with U.S. Export
Regulations. No material can be sold or shipped to a debarred entity or
country embargoed by the United States of America. Verification of parts
offered as potential alternates and/or interchangeables, is ultimately the
responsibility of the quote requester.

All AGES` purchases must have full traceability to a regulated source
faxed/e-mailed beforehand, and must accompany parts. All parts purchased
must be non-incident related, and statement faxed, e-mailed, etc.
beforehand, and must also accompany parts. All NEW parts purchased must have
traceability documentation back to the OEM! All parts must have U.S. Maint
8130, Canadian DOT 24-0078, or JAA FORM 1, and company C of C, when
applicable. Any HAZMAT material purchased, such as Oxygen, Fuel, Oil,
Hydraulic, etc. type related material, must include Material Safety Data
Sheets, if applicable. All applicable HAZMAT documentation and labeling must
accompany HAZMAT shipped material.

This e-mail message/fax, may contain legally privileged and/or confidential
information. If you are not the intended recipient(s), or the employee or
agent responsible for delivery of this message/fax to the intended
recipient(s), you are hereby notified that any dissemination, distribution,
or copying of this e-mail message/fax is strictly prohibited.

If you received this message/fax in error, please immediately notify the
sender and delete this e-mail message/fax from your computer.


-----Original Message-----
From: Matt Drew [mailto:mdrew redhat com]
Sent: Thursday, April 05, 2001 11:50 AM
To: 'redhat-install-list redhat com'
Subject: RE: Network Computers


On Thu, 5 Apr 2001, Bill Farrell wrote:

> This is an interesting discussion for me right now, as I have similar
> questions.  I understand "normal" (*nix) TCP/IP but M$'s take on it is
still
> a bit confusing.
>
> I have three LANs (separate locations).  The "whole" network is
> 172.24.x.y/16 (implicitly), with location "A" (main office, 15 servers) is
> 172.24.0.y/24, home (three Win98 workstations) is 172.24.1.y/24, and a
> location in the Netherlands (via VPN) is 172.24.5.y/24.

The important thing to remember is the separation of TCP/IP and NetBIOS.
The whole PDC/N'hood/computer name thing is all NetBIOS that runs on top
of TCP/IP (in your case).

> I set the netmasks so that I could use "internal" addresses behind the
> firewall and allow the firewall (a Netscreen 10 [LOVE it!]) to do VPN
> routing for me.  Is this configuration wrong?
>
> There are 15 servers at my office: two NT PDC's and the rest are RH6.2
> running Samba.  Up until I turned on the NL VPN I was blithely unaware
that
> the WAN wasn't doing what I thought it was :-(~~~
>
> Under the Net'hood either from my office or from home I can see all
> computers and both NT domains in the US (172.24.0.y and 172.24.1.y).  I
> can't see doodly from the NL LAN (172.24.5.y) with the Net'hood, but
> everything is pingable.  That is, I can't see the third domain that lives
in
> the Netherlands in "Entire Network".

This is because broadcasts have been disabled across the WAN link.  There
are a lot of good reasons for this, but it stops NetBIOS (which is a
broadcast-based protocol) from functioning across the WAN link.

> Now, without pissing off the VPN routers, how can I see all three domains?

Short Answer?  Enable broadcasts across the WAN link and eat the bandwidth
chunk that it takes.

Right Answer?  Set up two WINS servers and configure replication across
the WAN link.  There is also the choice of running the entire site as one
domain, with BDC's at the remote sites to handle logins.  Both ways are
not that simple, and Network Neighborhood replication still won't work
across the WAN link.

Ugly Answer?  Build up LMHOSTS files for all the machines involved, and
use those.  Still no Network Neighborhood, but you can use machine names.
Downside is manual maintenance of all the LMHOSTS files. :(

> Mind, this is a "nice-to-have" and not absolutely necessary.  NFS and rcp
> work just fine for most data sharing between all three locations.  But my
> business partner in NL is more NT-familiar and would like to use the
Windoze
> Explorer and drag-and-drop.

This isn't necessarily a problem -- you should still be able do SMB
sharing by mounting the share via IP address instead of machine name.
SMB by itself does not rely on broadcasts.

> We can't all be perfect Linux-heads :-)
>
> Life was wonderful up until I had to support NT.  Has anyone else done
this
> setup?  Have suggestions?
>
> > I am having trouble trying to figure out why I can ping each computer,
but
> > can not view the computers under Network Neighborhood. All entries in
the
> > LMHOSTS and HOSTS file are correct. I can ping using the IP address of
> each
> > and ping using the alias. Any suggestions?
> >
> > Thanks, Alvin
> >
> >
> >
> > _______________________________________________
> > Redhat-install-list mailing list
> > Redhat-install-list redhat com
> > https://listman.redhat.com/mailman/listinfo/redhat-install-list
> >
>
>
>
>
> _______________________________________________
> Redhat-install-list mailing list
> Redhat-install-list redhat com
> https://listman.redhat.com/mailman/listinfo/redhat-install-list
>
>
>
> _______________________________________________
> Redhat-install-list mailing list
> Redhat-install-list redhat com
> https://listman.redhat.com/mailman/listinfo/redhat-install-list
>

-- 
Matt Drew
Peer Review team lead and Bughunter
Red Hat Consumer Services



_______________________________________________
Redhat-install-list mailing list
Redhat-install-list redhat com
https://listman.redhat.com/mailman/listinfo/redhat-install-list