So I have a Buffalo Technologies LS-CHL56B NAS(runs 2.6 busybox kernel) and I am running openSUSE 12.1. I have tried to connect via SAMBA and tried using my web browser (which returns a 404 error) and have not had any luck yet. ZENMAP shows the device with one open port (80) and http service running on that port. What am I missing?
A NAS is often two things: a web server (using Apache to server web pages) and a file server (using Samba to serve shared files). So when you use the web browser you will focus via port 80 on the web server function; since there are no web pages built and placed on the NAS by you, you get the 404 response. So that’s to be expected.
But I suspect (although you didn’t say so) that you are trying to put files on the NAS to share via Samba. Is that right?
At the moment I’m just trying to access the NAS. I just moved everything over to Linux again after being away for several years. Prior to me making the move everything worked wonderfully but of course I was also able to utilize the software provided by Buffalo Technologies.
The NAS most likely has a workgroup name set by you. Set the same workgroup name in the openSUSE machine and generally set it up using this primer: Samba and Suse: HowTo Set up an openSUSE-Windows Home Office LAN/Network. Versions 11.x
No need for any shares on the openSUSE client (unless you particularly want some).
Set the firewall as in the primer (samba server, netbios server, client)
Set the name resolve order correctly
Set the [global] stanza like this:
[global]
workgroup = NAME_OF_WORKGROUP
netbios name = name_of_this_workstation
name resolve order = bcast host lmhosts wins
server string = ""
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
use client driver = yes
map to guest = Bad User
local master = yes
os level = 33
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = False
Choose appropriately for “NAME_OF_WORKGROUP” and “name_of_this_workstation”
Turn off AppArmor (probably it’s off by default)
If the RPM “systemd-sysvinit” is installed, uninstall it and replace it with the RPM “sysvinit-init” (see sticky at begin of network forum).
On 2012-03-31 05:06, swerdna wrote:
> A NAS is often two things: a web server (using Apache to server web
> pages) and a file server (using Samba to serve shared files). So when
> you use the web browser you will focus via port 80 on the web server
> function; since there are no web pages built and placed on the NAS by
> you, you get the 404 response. So that’s to be expected.
The few devices I have seen have a management web page on port 80, not a
page put by the user.
:-?
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 04/01/2012 10:18 AM, Carlos E. R. wrote:
> On 2012-03-31 05:06, swerdna wrote:
>> A NAS is often two things: a web server (using Apache to server web
>> pages) and a file server (using Samba to serve shared files). So when
>> you use the web browser you will focus via port 80 on the web server
>> function; since there are no web pages built and placed on the NAS by
>> you, you get the 404 response. So that’s to be expected.
>
> The few devices I have seen have a management web page on port 80, not a
> page put by the user.
>
> :-?
>
Yes of course… I was daydreaming. And what I said about Samba still
stands. OP should ignore talk about web server because not relevant to
Samba.
–
Regards
swerdna
On 2012-04-01 06:29, swerdna wrote:
> On 04/01/2012 10:18 AM, Carlos E. R. wrote:
>> The few devices I have seen have a management web page on port 80, not a
>> page put by the user.
>>
>> :-?
>>
> Yes of course… I was daydreaming. And what I said about Samba still
> stands. OP should ignore talk about web server because not relevant to Samba.
Aha.
Then dghobbiest has some kind of connectivity problem, because he gets a
404 error when trying to connect via http - unless he is not using http://
on the web browser, but smb://?
Connecting via web should be easier, and it is usually the first step in
order to configure samba on the device. It should be password protected,
and the password is set via that control page - usually, that is.
If all fails, there is probably an all reset procedure.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
You are completely right. We need to know from dghobbiest whether successful contact with the NAS & configuration occurred on http:/ /IP_address_of_nas
Over to you dghobbiest
No success trying to connect a browser using http://IP. That is where the 404 error comes from. As for the password part of this. I never set one up. The NAS is being used for internal storage on my network only. I don’t have it setup for outside connectivity and the few files that I need security on I encrypt individually.
On 04/02/2012 09:16 AM, dghobbiest wrote:
>
> swerdna;2452823 Wrote:
>> You are completely right. We need to know from dghobbiest whether
>> successful contact with the NAS& configuration occurred on http:/
>> /IP_address_of_nas
>>
>> Over to you dghobbiest
>
> No success trying to connect a browser using http://IP. That is where
> the 404 error comes from. As for the password part of this. I never
> set one up. The NAS is being used for internal storage on my network
> only. I don’t have it setup for outside connectivity and the few files
> that I need security on I encrypt individually.
>
>
I don’t understand how you access the storage space in the NAS; i.e.
what do you mean by “The NAS is being used for internal storage on my
network only”. Is there any form of network transport used to get to the
storage space in the NAS or is there some other form of connection to
the storage space?
–
Regards
swerdna
I was just making sure everyone is on the same page. Some NAS devices operate with cloud type services or are able to be configured so you can connect to them via WAN and LAN. And while my device is capable of this I don’t use the function. It is strictly used for my LAN.
On 2012-04-02 01:16, dghobbiest wrote:
> No success trying to connect a browser using http://IP. That is where
> the 404 error comes from. As for the password part of this. I never
> set one up. The NAS is being used for internal storage on my network
> only. I don’t have it setup for outside connectivity and the few files
> that I need security on I encrypt individually.
And how did you put those files in there?
If you can not open the control page via http://IP, then there is nothing
that can be done. Its just a piece of metal junk. Read the manual for
ideas. It is possible that you accessed the control interface and removed
http as a valid protocol - it is possible, but then you shot yourself on
the foot. Maybe it has ssh or telnet instead.
Try to find a factory reset procedure.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
No the NAS was working perfectly prior to my Linux install. Under Windows everything function flawlessly. But I dumped Windows again I can’t access the drive.
On 04/01/2012 08:26 PM, dghobbiest wrote:
>
> No the NAS was working perfectly prior to my Linux install. Under
> Windows everything function flawlessly. But I dumped Windows again I
> can’t access the drive.
How was Windows accessing the drive? Was it mapped as a network drive?
Yes it was mapped as a network drive. Buffalo Tech provided software for the install however they don’t support Linux thus I’m on my own for this.
Yes it was mapped as a network drive. Buffalo Tech provided software for the install however they don’t support Linux thus I’m on my own for this.
On 04/01/2012 09:16 PM, dghobbiest wrote:
> Yes it was mapped as a network drive. Buffalo Tech provided software
> for the install however they don’t support Linux thus I’m on my own for
> this.
Was the software for the install for Windows, or for the NAS? If the former,
then they may be using a proprietary protocol; however everything I have read
on-line seems to indicate that they use SMB.
The other thing I found that was a group that supports the replacement of the
Buffalo software with Linux firmware. With that, you could use any protocol that
Linux handles. I think the LS-CHL varieties are supported.
The software was more for Windows. The biggest part of it were utilities for back-up. As far as I know no new protocols were part of the install and like you all the data I can find online points to SMB. Also if so odd protocol were in use wouldn’t I be finding an open port somewhere for it?
On 2012-04-02 05:56, dghobbiest wrote:
> The software was more for Windows. The biggest part of it were
> utilities for back-up. As far as I know no new protocols were part of
> the install and like you all the data I can find online points to SMB.
> Also if so odd protocol were in use wouldn’t I be finding an open port
> somewhere for it?
You would have to check if you can browse via http from Windows. Without
that you have no control of the machine, can’t check anything.
With nmap you can find out what ports are open.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Under Windows I could access the drive any number of ways including web browser. I have used nmap (zenmap to be precise, see my original post) and only found one open port (80/http protocol)