My Humax Forum » Freeview HD » HD FOX T2

Problem-Samba on a "modified" HD-Fox-T2

(19 posts)
  1. User has not uploaded an avatar

    welly

    member
    Joined: Jul '11
    Posts: 27

    offline

    Hi folks,
    not sure if this is the correct forum, but here goes.
    I am running FTP (FileZila), Telnet and the browser I/F to my HD-Fox-T2 with external HDD ok. I have also used the "bootHDRmode" to successfully copy programes to the virtual disk.
    The only problem I have is trying to use Samba. When I try to map a network drive I keep getting a error message
    "network path \\HUMAX\Media" could not be found. I am trying to connect pc running Windows XP SP3 with the pc set up in a workgroup named WORKGROUP. The only readme notes on the use of Samba I came across seemed to be in Raydons media+file server bundle for the FoxsatHDR but I'm not sure how relevant they are to the HD-Fox-T2. Any one else having problems with Samba or any ideas what I am doing wrong - or not doing right?
    thanks, Ian

    | Mon 14 Nov 2011 12:54:40 #1 |
  2. User has not uploaded an avatar

    raydon

    special member
    Joined: Feb '11
    Posts: 159

    offline

    welly - 1 day ago  » 
    Hi folks,
    When I try to map a network drive I keep getting a error message
    "network path \\HUMAX\Media" could not be found. I am trying to connect pc running Windows XP SP3 with the pc set up in a workgroup named WORKGROUP. The only readme notes on the use of Samba I came across seemed to be in Raydons media+file server bundle for the FoxsatHDR but I'm not sure how relevant they are to the HD-Fox-T2. Any one else having problems with Samba or any ideas what I am doing wrong - or not doing right?
    thanks, Ian

    From telnet enter the command "hostname" to determine the hostname of your box. If it says "humax" then map a drive to "\\humax\Media". You can also use the IP address instead of the hostname when mapping a drive "\\xxx.xxx.xxx.xxx\Media"

    | Tue 15 Nov 2011 14:16:10 #2 |
  3. User has not uploaded an avatar

    welly

    member
    Joined: Jul '11
    Posts: 27

    offline

    Hi Raydon,
    following your suggestions the results :-

    1. Used telnet to query hostname result was humax (lower case).
    Therefore tried to map drive using \\humax\Media same result as my original post.
    2. Tried to map drive using \\192.168.1.3\Media, result - connected straight away.
    Interestingly drive is shown as Media on
    "Samba HDR-Fox-T2(192.168.1.3)" so should I have used Samba HDR-Fox-T2? Anyway using the IP address seems to work fine.

    many thanks, Ian

    | Tue 15 Nov 2011 16:47:45 #3 |
  4. User has not uploaded an avatar

    raydon

    special member
    Joined: Feb '11
    Posts: 159

    offline

    welly - 57 minutes ago  » 
    Interestingly drive is shown as Media on
    "Samba HDR-Fox-T2(192.168.1.3)" so should I have used Samba HDR-Fox-T2? Anyway using the IP address seems to work fine.
    many thanks, Ian

    No, that's just the samba server ID string. The netbios name is derived from the hostname and a "hosts" file is created dynamically on each bootup. You can display the contents of this file by entering "cat /tmp/hosts" from telnet. Sounds like the dns is not being resolved if you can't use the hostname. Try "ping humax" from telnet on the box itself, then again from a command line on your PC. Both should work.

    | Tue 15 Nov 2011 17:58:20 #4 |
  5. User has not uploaded an avatar

    welly

    member
    Joined: Jul '11
    Posts: 27

    offline

    OK now things are getting really confusing :-
    1. Unable to run cat/tmp/hosts from telnet prompt results in a invalid command response.
    2. Ping humax from command line on pc results in
    pinging humax (192.0.2.100)- requests timed out.
    3.Ping humax from humax 64 bytes from 192.0.2.100 requests returned ok.
    Not sure where 192.0.2.100 is, or where that is being picked up from?

    | Tue 15 Nov 2011 18:53:40 #5 |
  6. User has not uploaded an avatar

    Martin Liddle

    special member
    Joined: Feb '11
    Posts: 4,619

    offline

    welly - 2 minutes ago  » 
    OK now things are getting really confusing :-
    1. Unable to run cat/tmp/hosts from telnet prompt results in a invalid command response.

    You are missing a space; should be cat /tmp/hosts

    | Tue 15 Nov 2011 18:57:21 #6 |
  7. User has not uploaded an avatar

    welly

    member
    Joined: Jul '11
    Posts: 27

    offline

    Hi, hanks Martin

    result of cat /tmp/hosts
    127.0.0.1 local host
    192.0.2.100 humax (so we have the "mystery" IP address).

    Does this explain anything?

    Ian

    | Tue 15 Nov 2011 20:37:23 #7 |
  8. User has not uploaded an avatar

    raydon

    special member
    Joined: Feb '11
    Posts: 159

    offline

    welly - 15 minutes ago  » 
    Hi, hanks Martin
    result of cat /tmp/hosts
    127.0.0.1 local host
    192.0.2.100 humax (so we have the "mystery" IP address).
    Does this explain anything?
    Ian

    Hmm, very strange. The IP address in the dynamic "hosts" file is parsed from information outputted by the "ifconfig" command.
    If you enter "ifconfig" from a telnet session this will display a list of information about the ethernet port "eth0". The assigned IP address will be in the second line.

    | Tue 15 Nov 2011 21:02:44 #8 |
  9. User has not uploaded an avatar

    welly

    member
    Joined: Jul '11
    Posts: 27

    offline

    OK result of ifconfig :-

    second line of o/p
    wlan0 inet addr:192.168.1.3 Bcast: 192.168.1.255 Mask:255.255.255.0.

    | Tue 15 Nov 2011 21:19:25 #9 |
  10. User has not uploaded an avatar

    raydon

    special member
    Joined: Feb '11
    Posts: 159

    offline

    welly - 1 hour ago  » 
    OK result of ifconfig :-
    second line of o/p
    wlan0 inet addr:192.168.1.3 Bcast: 192.168.1.255 Mask:255.255.255.0.

    Are you by any chance connecting your T2 to the network after powering it up ? If so try connecting it to the network before powering up.

    | Tue 15 Nov 2011 22:36:55 #10 |

RSS feed for this topic

12

Reply »

You must log in to post.