Re: Samba acting weird: name resolution not working. - SMB

This is a discussion on Re: Samba acting weird: name resolution not working. - SMB ; In article , piotr@linuxblast.com says... > I have a question: > My network is rather simple: > 1. Desktop PC (Win XP/Linux): 192.168.1.2 (Gump) > 2. Laptop (Win Me/Linux): 192.168.1.3 (Tux1) > 3. Samba server: 192.168.1.250(Tux2) > 4. Gateway (Cable): ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Re: Samba acting weird: name resolution not working.

  1. Re: Samba acting weird: name resolution not working.

    In article ,
    piotr@linuxblast.com says...
    > I have a question:
    > My network is rather simple:
    > 1. Desktop PC (Win XP/Linux): 192.168.1.2 (Gump)
    > 2. Laptop (Win Me/Linux): 192.168.1.3 (Tux1)
    > 3. Samba server: 192.168.1.250(Tux2)
    > 4. Gateway (Cable): 192.168.1.252
    > 5. Turtle Beach AudioTron: 192.168.1.4
    >
    > Here is the problem:
    > I can see Samba shares from both (1) and (2) but only using IP
    > addresses (not Tux2). Samba server deas not appear in my net
    > neighborhood at all. When I purhased AudioTron it found the /data
    > share with my music on the Samba server. A few days ago I gad a powr
    > loss, and then AudioTron stopped seeing the Samba server. I think the
    > problem could be with NetBios name resolution (since it seems like
    > it's not working), but how was it working for months before?
    > Help!!! How can I get name resolution to work???
    >



    You are correct, this is a netbios name issue. Samba (and windows)rely
    on a correct dns setup in which to operate.
    Assuming this issue only occurs on the audiotron hardware??
    You will have to consult the docs that came with it..


    --
    Regards,
    Mark
    Samba Setup Guide
    www.samba.netfirms.com

  2. Re: Samba acting weird: name resolution not working.

    Mark wrote in message news:...
    > In article ,
    > piotr@linuxblast.com says...
    > > I have a question:
    > > My network is rather simple:
    > > 1. Desktop PC (Win XP/Linux): 192.168.1.2 (Gump)
    > > 2. Laptop (Win Me/Linux): 192.168.1.3 (Tux1)
    > > 3. Samba server: 192.168.1.250(Tux2)
    > > 4. Gateway (Cable): 192.168.1.252
    > > 5. Turtle Beach AudioTron: 192.168.1.4
    > >
    > > Here is the problem:
    > > I can see Samba shares from both (1) and (2) but only using IP
    > > addresses (not Tux2). Samba server deas not appear in my net
    > > neighborhood at all. When I purhased AudioTron it found the /data
    > > share with my music on the Samba server. A few days ago I gad a powr
    > > loss, and then AudioTron stopped seeing the Samba server. I think the
    > > problem could be with NetBios name resolution (since it seems like
    > > it's not working), but how was it working for months before?
    > > Help!!! How can I get name resolution to work???
    > >

    >
    >
    > You are correct, this is a netbios name issue. Samba (and windows)rely
    > on a correct dns setup in which to operate.
    > Assuming this issue only occurs on the audiotron hardware??
    > You will have to consult the docs that came with it..



    Thanks!!!
    I have tweaked with lmhosts file on my smb server and it seemed to
    help. No changes to Audiotron. Weird (well, maybe not for someone who
    knows more about smb).
    Thanks again.

    Peter

+ Reply to Thread