August 04, 2008, 11:04:54 am
News:
  Pages: [1]
Author Topic: Network login issues  (Read 208 times)
Decay
Newbie

Posts: 2


« on: July 11, 2008, 08:30:48 pm »

I just connected my OSD to a Network Attached Storage (NAS) device to store my media files. The NAS unit has  a "Public" folder that's shared which doesn't require a user name or password to access. I can connect to the NAS, see the Public folder, and view it's contents from several computers on my network without having to authenticate with the NAS.

From my OSD, I can see the NAS device on the network, and when I select it, I can see the "Public" folder, but when I try to open the Public folder and view the contents, the OSD asks me to authenticate with a username and password. Again, the NAS is NOT configured to require a username and password. I tried using blanks for username and password, but the OSD throws an error and tells me the username and password are incorrect.

I have a similar issue with shared drives on a PC on my network. I have a PC that has four shared drives. I created a user account for the Neuros on that PC (Windows XP) and gave that account the same level of access (full access) to all four drives. When I connect to that PC from the Neuros, I can access two of the drives without being challenged to authenticate, but the OSD ask me to authenticate when trying to access two other drives on the same PC. If I use the username and password I created for the Neuros account, the OSD tells me the username and password are incorrect. The networking capabilities of the OSD seem completely random.

I'm running firmware 3.33-1.75-02.849

These network issues are making the OS unusable. Since it only supports USB HDs formatted as FAT (with a 32GB limit) I need to use a network share, and these network issues are driving me mad. Anyone have a solution?

Thanks,
Decay
Logged
greyback
Moderator
Hero Member

Posts: 925


« Reply #1 on: July 13, 2008, 12:22:25 pm »

A couple of possibilities spring to mind.

First, have you considered the new Arizona firmware branch? (3.33-2.xx) It has improved networking features which should solve this problem for you. It does require the use of a permanently inserted CF card however, but you are entitled to one from Neuros. Check out this age:
http://open.neurostechnology.com/content/osd-arizona-firmware-release-333-209-00871

Or if you wish to remain with 3.33-1.75, you could try telnetting in to your OSD and trying to create the network share manually. This isn't the easiest option, but this guide is a place to start.
-G
Logged
Decay
Newbie

Posts: 2


« Reply #2 on: July 14, 2008, 09:42:22 am »

Thanks, greyback.

I upgraded to Arizona (3.33-2.09-00.871 and still have the same problem.

The OSD seems to require a username and password for all network resources. Do you know if this is the case?  The Iomega NAS doesn't suport usernames, just passwords, so I can't setup a username/password account for the OSD.  I even created a new share and assigned a password but the OSD still won't login (using a blank username and the simple password I assigned to that share.)

At least the upgrade to Arizona fixed the problem logging into shares on an XP box. I can now see files on one of my PCs.
Logged
greyback
Moderator
Hero Member

Posts: 925


« Reply #3 on: July 14, 2008, 02:35:31 pm »

Hey,
usually the OSD tries some obvious login info like no username or password, and 'guest' with a blank password. If these all fail, it then it presents the user with the username/password prompt.

Your NAS is confusing it. Usually with samba shares, one needs a username with a password. Could you try "guest" as the username, with your supplied password perhaps? Or delve into the internets and see how other people on linux manage to interface with your model NAS. There must be a username/password pairing that can work for you!

I'm sorry I can't be more helpful, this process is either simple or tricky as hell, and dependent on the model of NAS you own.
-G
Logged
  Pages: [1]
Jump to: