Eric,
I am busy trying to grasp the browse list concept. We have subnets and
dial-in accounts. From what I have read you may have to get your Linux
box act as aWINS server and have to dial-up user use the wins server to
resolve names on the brows list. The browse list is updated every 12-15
minutes ao your dial-up account might not show upat first. This has
caused me some trouble at first as I expected the list to be up-todate
as the PC logs on.
Hope this sheds some light on your problem.
Regards
-------------------------------------------------------
Shaun Lennox Tel : 27-83-270-5132
P.O. Box 94 Fax : 27-21-54-6605
Eppindust mailto:shaun@countyfair.co.za
South Africa,7475
System Administrator (AIX) County Fair Foods
-------------------------------------------------------
> > I am busy trying to grasp the browse list concept. We have subnets and > > dial-in accounts. From what I have read you may have to get your Linux > > box act as aWINS server and have to dial-up user use the wins server > to > > resolve names on the brows list. The browse list is updated every > 12-15 > > minutes ao your dial-up account might not show upat first. This has > > caused me some trouble at first as I expected the list to be up-todate > > as the PC logs on.Your dial-up doesn't really need to appear. If you use the /etc/ppp/options entry of "ms-wins", you can get all the browse info for your domain. Since machines register as they come on, the only problem *should* be when a machine is down and no longer available but this will be unknown for 12-15 minutes. Even if a machine doesn't appear in your browser, you can map it manually by name under Tools/Map Network Drive in Windows Explorer, and if you've connected before, there'll even be an entry of the correct machine as a possibility in the pull-down menu. Bill
> > Regarding remote network browsing: > We have had mixed success browsing Network Neighborhood from > PPP-connected Win95 PCs. Our servers are all SAMBA, no NT here :-) > The Win95s have WINS-server defined correctly in the network > setup (checked by running winipcfg). We wait a couple of > minutes after establishing PPP-connection, then try to > browse. Now, some Win95s (my OSR2.1, for example :-) browse > without problems, but others with a supposedly similar > setup cannot browse. Is the problem with older Win95 > versions, or something entirely different ? Note that > we are all dialing in to the same IBM-8235 router, so > everything ought to be the same, yet the Win95s seem to > behave differently.This may not be related, but make sure you have the latest drivers on problems like this - I've had old 3Com905 original Windows drivers refuse to browse properly, and the new ones do fine. There might be something very significant that got updated in Win95 PPP-TCP/IP code in later service packs and releases.
Bill Eldridge <bill@rfa.org> wrote:>> Now, some Win95s (my OSR2.1, for example :-) browse >> without problems, but others with a supposedly similar >> setup cannot browse. Is the problem with older Win95 >> versions, or something entirely different ? Note that >> we are all dialing in to the same IBM-8235 router, so >> everything ought to be the same, yet the Win95s seem to >> behave differently. > > This may not be related, but make sure you have the latest > drivers on problems like this - I've had old 3Com905 > original Windows drivers refuse to browse properly, and the > new ones do fine.This seems unrelated. The Win95 PC connects to the network via modem, and our SAMBA DMB is an IBM RS/6000. And some Win95 PCs work fine with this setup, while others don't.> There might be something very significant > that got updated in Win95 PPP-TCP/IP code in later service > packs and releases.Yup, I guess that is the question that I'm asking. Does anyone out there know ?? Ole Holm Nielsen Department of Physics, Building 307 Technical University of Denmark, DK-2800 Lyngby, Denmark