Re: Samba Resolution Problem: named.conf?
joe.beasley_at_jubjub.org
Date: 05/26/04
- Next message: RR: "Re: Funny Critique of Linux, True in Many ways"
- Previous message: Glenn Sondemack: "Re: Funny Critique of Linux, True in Many ways"
- In reply to: Webmaster: "Samba Resolution Problem: named.conf?"
- Next in thread: Webmaster: "Re: Samba Resolution Problem: named.conf?"
- Reply: Webmaster: "Re: Samba Resolution Problem: named.conf?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 26 May 2004 02:32:14 GMT
Add and entry to the lmhosts file on the windows box. Search for
lmhosts.sam on your system for an example. Place the lmhosts in the same
directory as the lmhosts.sam.
Webmaster wrote:
>
> -Problem: my Windows XP box at 192.168.12.1 can see, but can't access
> Samba at 192.168.30.1.(Mudhost)
>
> -Windows XP is routed through 192.168.12.10
>
> -I believe that when windows tries to access //mudhost, which is the
> name of the sambashare, it fails to resolve it to the correct ip.
>
> -I believe if I could set it up so Windows could ping mudhost and get
> a response, this might solve the problem. Can anyone suggest how I
> might configure named.conf for correct name resolution?
>
> -Windows uses 192.168.12.10 as a name server.
>
> Thanks
> Josh Beck
- Next message: RR: "Re: Funny Critique of Linux, True in Many ways"
- Previous message: Glenn Sondemack: "Re: Funny Critique of Linux, True in Many ways"
- In reply to: Webmaster: "Samba Resolution Problem: named.conf?"
- Next in thread: Webmaster: "Re: Samba Resolution Problem: named.conf?"
- Reply: Webmaster: "Re: Samba Resolution Problem: named.conf?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
