Mailinglist Archive: opensuse (4054 mails)
| < Previous | Next > |
Re: [SLE] Network "Re-Connection" Problem
- From: Eric Hines <eehines@xxxxxxxxxxx>
- Date: Sun, 15 Jan 2006 17:13:08 -0600
- Message-id: <7.0.0.16.2.20060115171156.03570948@xxxxxxxxxxx>
Sorry for the direct post. My emailer is smarter than I am, again.
At 01/15/06 10:59, you wrote:
I set up my lmhosts file on the PC (to try it out before doing it to the laptop, also. There's an lmhosts.sam file at WINNT\system32\drivers\etc that provides a sample lmhosts file and some instructions for its setup.), and I got no effect. That is, after successfully setting up the LAN from scratch, and then rebooting my PC, I still lost the server data from Network Neighborhood, but net view and net use still functioned, so I still had (cumbersome) access to my shares.
I googled on lmhosts and got pointed at MS's Knowledgebase article 150800, from which I extracted the following:
SUMMARY
In TCP/IP-based networks involving routers and multiple segments, it is generally recommended that you implement WINS for name resolution and browsing support. However, as an alternative to WINS, it is possible to have full domain browsing by using only LMHOSTS files on all computers, although there are some limitations that will be discussed in this article.
In either case, it is important to note that a client only participates in domain browsing when the client is using a workgroup name that is equivalent to the domain name (WorkgroupName = DomainName). Windows NT computers can also "join" the domain to gain this functionality, instead of being in a workgroup.
This functionality of LMHOSTS-based domain browsing (over routers) has not been formally documented or tested by Microsoft, and may not be available in future versions of the client and server operating systems. Use this information with discretion.
From this I conclude that the lack of effect of having an lmhosts file would be expected, as I have WINS browsing turned on (WINS Support=Yes, and winbindd is running).
Is there anything else I can try?
Thanks for your help; the information you provided was useful.
Eric Hines
There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action.
--Bertrand Russell
At 01/15/06 10:59, you wrote:
On Monday 16 January 2006 02:52, you wrote:
> At 01/15/06 09:12, you wrote:
> >On Monday 16 January 2006 02:01, Eric Hines wrote:
> > > However, my problem is this: if I have occasion to reboot either (or
> > > both) Windows devices after having successfully formed the LAN, I
> > > can't get back to my shares except through some convoluted
> > > machinations, and the server no longer appears in NN or in
> > > Explorer. For instance, when I run START|RUN|\\lserver0\<share>, I
> > > get access to that share. When I run, from a DOS command line, net
> > > view \\lserver0, I get a listing of all the shares to which I'm
> > > supposed to have access. Net use \\lserver0\<share> returns a
> > > successful completion message. I get this behavior on both devices,
> > > and whether I cold reboot or log off one user and log on another.
> >
> ><snip>
>
I'm no expert on Windows but I've had problems browsing a samba server which
have been solved by adding the Samba Server to the hosts file on the window
machines.
The lmhosts file is slightly different format to the hosts file. The LMHOSTS
file performs NetBIOS name to IP address mapping oriented.
Unfortunately I can't lay my hands on a example for you at the moment, but
you should look at the directives #DOM and #PRE. I suggest you have a look at
the info in lmhosts.sam and the man page lmhosts.
I found this from a google which may be of use
==================================
When to use HOSTS and when to use LMHOSTS ?
<snip>
I set up my lmhosts file on the PC (to try it out before doing it to the laptop, also. There's an lmhosts.sam file at WINNT\system32\drivers\etc that provides a sample lmhosts file and some instructions for its setup.), and I got no effect. That is, after successfully setting up the LAN from scratch, and then rebooting my PC, I still lost the server data from Network Neighborhood, but net view and net use still functioned, so I still had (cumbersome) access to my shares.
I googled on lmhosts and got pointed at MS's Knowledgebase article 150800, from which I extracted the following:
SUMMARY
In TCP/IP-based networks involving routers and multiple segments, it is generally recommended that you implement WINS for name resolution and browsing support. However, as an alternative to WINS, it is possible to have full domain browsing by using only LMHOSTS files on all computers, although there are some limitations that will be discussed in this article.
In either case, it is important to note that a client only participates in domain browsing when the client is using a workgroup name that is equivalent to the domain name (WorkgroupName = DomainName). Windows NT computers can also "join" the domain to gain this functionality, instead of being in a workgroup.
This functionality of LMHOSTS-based domain browsing (over routers) has not been formally documented or tested by Microsoft, and may not be available in future versions of the client and server operating systems. Use this information with discretion.
From this I conclude that the lack of effect of having an lmhosts file would be expected, as I have WINS browsing turned on (WINS Support=Yes, and winbindd is running).
Is there anything else I can try?
Thanks for your help; the information you provided was useful.
Eric Hines
There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action.
--Bertrand Russell
| < Previous | Next > |