Remote Annex Example - Bay Networks Remote Annex User Manual

Appendix A Browsing for Resources on a Microsoft Network
Number of PCs on the
Subnet
A-6
Remote Annex Server Tools for Windows NT

Remote Annex Example

The Remote Annex forwards IP broadcasts from a remote access client
to the network that the Annex is on. If that network is a subnet that has
no PCs capable of being a master browser, the remote client must be
configured to use WINS to be able to browse Microsoft resources.
Another possible option might be to configure the router to pass IP
broadcasts, but this is probably not desirable.
Another issue to consider is the number of PCs on the subnet that can act
as master browsers. The number and type of machines may give
unpredictable behavior for a remote access client. Consider for example,
a remote client that is not configured to use WINS. During the day, the
subnet dialed into has several Windows 95 stations that can act as master
browsers. The PDC and other resources are on a different subnet. When
the client dials in during the day, a broadcast finds one of the Windows
95 systems and browsing works as expected. However, it is company
policy to shut down PCs at night, so when everyone goes home all
Windows 95 machines are shut down. Now the remote client dials in,
broadcasts to the subnet, but no master browsers are available. Browsing
works during the day, but not at night. WINS would overcome this
problem by finding the DMB when the Windows 95 machines were not
available.
Note also that the ip_forward_broadcast parameter on the Annex
controls broadcast traffic from the ethernet to the remote client. It has no
effect on broadcasts generated by the client for the ethernet. Client to
ethernet broadcasts are on and can not be configured off. Replies to the
client browser broadcasts are directed datagrams and will not be affected
by the ip_forward_broadcast setting.
®
User Guide