| > Is it possible to have network browsing support for WIN95 clients over
> such a dial up PPP link. I have had no success with this in the past.
> The clients are configured to run Netbeui as well as TCPIP.
In order to browse a network, you *must* have configured some transport
which can carry NetBIOS traffic from the PC onto the LAN. Both TCP/IP
and IPX/SPX can satisfy this requirement. In addition, the PC clients
must be able to resolve NetBIOS names to network addresses, since the
standard method of using broadcasts can not be used (the DNAS software
does not currently pass broadcast traffic over the slower dial-up serial
lines since doing so could easily consume the limited amount of available
bandwidth).
To resolve names without using broadcast messages, several methods can be
used. WINS (Windows Internet Naming Service) is a service which can
translate NetBIOS names to and from IP addresses. WINS runs on a LAN-
attached host, possibly the domain controller, and interacts with WINS
servers in other domains to learn all names available on a network. You
can also use a static text file named "LMHOSTS" on each PC client to
translate names to addresses. Microsoft clients can also use DNS to
resolve NetBIOS names.
In my opinion, the easiest way to allow network browsing is to turn on
WINS on your domain controller. You can probably get more information
on WINS, browsing, domain controllers, etc. in the WINDOWS-NT conference.
Jim
|
| I recently had to write up something for a customer on the subject of
browsing. I thought I'd post it here for the benefit of others... and so
I know where to find it when I have to answer this question again later!
Some of this information came from a paper written by Kevin Brosnan.
Thanks, Kevin.
Jim
===========================
> I wonder if there is any public forum or newsgroups on Netrider discussion
> (especially for MS windows client) which can be accessed from the web page.
> I have a question on the "Dial-up Network" in Windows 95 with Netrider and
> can't find any on-line support on that.
I'm not aware of any "official" DIGITAL-sponsored NetRider forum or
newsgroup, but some of the same issues are discussed in other more general
forums. Many people are trying remote access for the first time, using
Microsoft clients and various dial-up access servers. Problems with client
configuration isn't something specific to DIGITAL's family of remote access
servers, so often these types of questions can be answered in newsgroups
such as comp.dcom.servers, comp.dcom.lans, or comp.dcom.modems. You can
also always contact DIGITAL's service organizations for further assistance.
> Question : When I check the network neighborhood, I can't find any other PC
> on our simple workgroup and thus, can't share any network drive. Is this
> supported by Netrider?
Yes, NetRider does support "workgroup browsing" but you have to set up
Microsoft networking correctly in order to do this. To locate other PCs
in your workgroup or anywhere on the LAN, your PC client must either
broadcast a network message to all other systems on the LAN, or send a
message addressed to one particular system known as the "browse master".
Because a dial-up line can not pass as much data as a LAN network such as
Ethernet, access servers don't typically forward broadcast messages over
dial-up serial lines. Therefore, your PC client should be set up to use
the second method listed above.
Other PCs in your workgroup are identified using "NetBIOS names". In order
to translate NetBIOS computer names to IP addresses so network messages
can be sent directly instead of being broadcast, Microsoft networking uses
one of three methods: DNS lookup, a host-to-address mapping file on the
PC (\windows\system\lmhosts), or something called "WINS".
WINS stands for Windows Internet Naming Service. An NT domain controller
can function as a "browse master" by enabling WINS on that NT system. If
your PC running Dial-Up Networking has the address of the WINS server
defined on it, the PC will send a message directly to that WINS server,
which in term will provide to the PC client the information the PC needs
to browse or see other members of your workgroup.
To define the address of a WINS server on your PC, right-click Network
Neighborhood on the PC's desktop and select "Properties". In the top
window, select "TCP/IP -> Dial-Up Adaptor" and click "Properties". Select
the "WINS Configuration" tab and enter addresses for your primary and (if
available) a secondary WINS server. I recommend you enable WINS on your
NT system which functions as the domain controller for your workgroup.
You can also enter NetBIOS names and their corresponding IP addresses in
the "lmhosts" file mentioned above (the "lm" stands for Lan Manager).
This file contains the mappings of IP addresses to NetBIOS names in the
following format:
16.20.180.1 myserver #PRE #DOM homeoffice
In this example, the IP address for \\myserver is specified. The optional
#PRE tag specifies that the entry is preloaded into the PC's NetBIOS name
cache for faster response. The #DOM tag associates the entry with the
HOMEOFFICE domain, which effects how browsing and logon services function
in the TCP/IP environment.
Microsoft clients also allow the option of using DNS (Domain Name Service)
to resolve NetBIOS names. If the name cannot be resolved via NetBIOS name
resolution or the lmhosts file, the PC client uses DNS name resolution by
adding a domain suffix to the NetBIOS name and querying a DNS Server.
Follow the directions above to locate the "WINS Configuration" tab, but
instead of selecting that tab, select the "DNS Configuration" tab. Click
on "Enable DNS" and enter host and domain names, and IP addresses for one
or more DNS servers.
In the above example, "myserver" would become myserver.whatever.com prior
to attempting DNS resolution. Like NetBIOS, DNS can use a local ASCII file
(called "hosts") for name resolution rather than querying a server.
In summary, the easiest way to enable browsing on your PC is to first enable
WINS on an NT system on your LAN, such as your workgroup's domain controller.
I suggest this host since it's usually always available and performs other
workgroup functions already. Second, "teach" your PC to send WINS name
resolution requests to that system by defining that system's IP address in
the PC's "WINS Configuration" property page. That should be all you need
to get up and browsing remotely.
Happy browsing!
Jim
--
Jim Cahill ([email protected]) \ Digital Equipment Corporation
Internetworking and Remote Access / 550 King Street, LKG1-3/A11
DECserver Network Access Software \ Littleton, MA 01460-1289 USA
|