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

Forum Forums Freeview HD HD FOX T2 Problem-Samba on a "modified" HD-Fox-T2

  • This topic has 18 replies, 4 voices, and was last updated 14 years ago by Anonymous.
Viewing 15 posts - 1 through 15 (of 19 total)
  • Author
    Posts
  • #12472
    Anonymous
    Inactive

    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 \HUMAXMedia” 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

    #28387
    raydon
    Participant

    welly – 1 day ago  » 

    Hi folks,

    When I try to map a network drive I keep getting a error message

    “network path \HUMAXMedia” 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 “\humaxMedia”. You can also use the IP address instead of the hostname when mapping a drive “\xxx.xxx.xxx.xxxMedia”

    #28388
    Anonymous
    Inactive

    Hi Raydon,

    following your suggestions the results :-

    1. Used telnet to query hostname result was humax (lower case).

    Therefore tried to map drive using \humaxMedia same result as my original post.

    2. Tried to map drive using \192.168.1.3Media, 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

    #28389
    raydon
    Participant

    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.

    #28390
    Anonymous
    Inactive

    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? 😥

    #28391
    Martin Liddle
    Participant

    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

    #28392
    Anonymous
    Inactive

    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

    #28393
    raydon
    Participant

    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.

    #28394
    Anonymous
    Inactive

    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.

    :?

    #28395
    raydon
    Participant

    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.

    #28396
    raydon
    Participant

    raydon – 3 hours ago  » 

    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.

    Just realised you are connected to network using a wireless dongle. Would you mind posting the whole of the output from the “ifconfig” command

    #28397
    Anonymous
    Inactive

    humax# ifconfig

    lo Link encap:Local Loopback

    inet addr:127.0.0.1 Mask:255.0.0.0

    UP LOOPBACK RUNNING MTU:16436 Metric:1

    RX packets:12 errors:0 dropped:0 overruns:0 frame:0

    TX packets:12 errors:0 dropped:0 overruns:0 carrier:0

    collisions:0 txqueuelen:0

    RX bytes:726 (726.0 B) TX bytes:726 (726.0 B)

    wlan0 Link encap:Ethernet HWaddr 7C:DD:90:01:A0:0D

    inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0

    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    RX packets:61225 errors:0 dropped:0 overruns:0 frame:0

    TX packets:93080 errors:0 dropped:0 overruns:0 carrier:0

    collisions:0 txqueuelen:1000

    RX bytes:5034186 (4.8 MiB) TX bytes:139306668 (132.8 MiB)

    Hi raydon, yes T2 connected via wireless, above is dump of ifconfig.

    #28398
    raydon
    Participant

    Hi welly, I’ve been in touch with af123, the author of the custom firmware package for the HDR Fox T2 regarding your problem. He has replied with the following

    Quote:
    192.0.2.100 is the address that is assigned to the ethernet interface before it has been initialised, (IIRC wlan0 gets 192.0.2.101 initially)

    The /sbin/modinit script always puts the address of eth0 into the hosts file and therefore doesn’t work properly with a wireless dongle. I’ll come up with a fix for that!

    Thanks for letting me know.

    So there you have it. Look out for the bugfix release on hummy.tv 😉

    regards

    raydon

    #28399
    Anonymous
    Inactive

    Hi Raydon,

    thanks for your help and feedback.

    Nice to have an answer, if not a solution!

    I must have tried to install and uninstall Samba a dozen times – ah well looking forward to some good night sleeps.

    Ian

    🙄

    #28400
    Anonymous
    Inactive

    Welly, would you mind posting the output of the route command from your Humax?

    I have an updated firmware ready with a fix in it but just want to check one last thing.

    Thanks

Viewing 15 posts - 1 through 15 (of 19 total)
  • You must be logged in to reply to this topic.

The inner genius!