NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

readynasvirgin's avatar
May 06, 2011

Cannot access folders from Windows XP

Setup
Readynas Duo 2 TB connected via SKY wireless hub to PC running Windows XP SP3

Raidar works fine and I can see the folders e.g. 'media' with my itunes music library which I transferred from a macbook pro without any hitches.

Problem

Windows network shows an icon and identifies the nas drive name to me, however i cannot browse to the folders on the nas nor can I map a drive letter to the folders. This means that I cannot transfer my music library updates from itunes on the pc to the readynas. I can get to 'Shares' via http and also to the nas via http and frontview, it seems to be the CIFS side that does not communicate?

Any ideas gratefully accepted... thanks

readynasvirgin.

16 Replies

Replies have been turned off for this discussion
  • Hi All.

    I have the readynass working ok on my win 7 machine, but today I added a win xp machine.
    I ran Raidair and set the the folders for open access as suggested in a previous post, but when I click the "Browse" button in Raidair I get the following error:-

    \\192.168.0.220 is not accessible. You might not have permission to use this network resource.
    Contact Administrator of this server to find out if you have access permissions.
    Logon failure: account currently disabled.

    I can ping the nas from a command prompt.

    I must be missing something her and would appreciate any help.

    regards.
    Jim
  • ewok's avatar
    ewok
    NETGEAR Expert
    Make sure you're connecting using the credentials for a user account created on the ReadyNAS.
  • Hello,

    I am brand new to a Ready NAS Duo V1.
    Setup Ready NAS Duo v1 connected over wireless to an XP professional system.

    I am only able to access folder via HTTP.
    I have similar problems as mentioned in this thread.

    Raidair is telling me: \\192.168.1.106 network path not found.
    At the end of my post my attempts.
    Sadly no success.

    Thanx for your help.


    Ip config:

    C:\>ipconfig /all

    Windows-IP-Konfiguration
    Hostname. . . . . . . . . . . . . : Helios
    Primäres DNS-Suffix . . . . . . . :
    Knotentyp . . . . . . . . . . . . : Hybrid
    IP-Routing aktiviert. . . . . . . : Nein
    WINS-Proxy aktiviert. . . . . . . : Nein
    DNS-Suffixsuchliste . . . . . . . : http://www.google.de/search?q=

    Ethernetadapter LAN-Verbindung:
    Medienstatus. . . . . . . . . . . : Es besteht keine Verbindung
    Beschreibung. . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller
    Physikalische Adresse . . . . . . : 00-1C-23-B3-90-DD

    Ethernetadapter Drahtlose Netzwerkverbindung:

    Verbindungsspezifisches DNS-Suffix: http://www.google.de/search?q=
    Beschreibung. . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
    Physikalische Adresse . . . . . . : 00-1C-BF-49-FE-2E
    DHCP aktiviert. . . . . . . . . . : Ja
    Autokonfiguration aktiviert . . . : Ja
    IP-Adresse. . . . . . . . . . . . : 192.168.1.102
    Subnetzmaske. . . . . . . . . . . : 255.255.255.0
    Standardgateway . . . . . . . . . : 192.168.1.1
    DHCP-Server . . . . . . . . . . . : 192.168.1.1
    DNS-Server. . . . . . . . . . . . : 192.168.1.1
    83.169.184.161
    83.169.184.225
    Lease erhalten. . . . . . . . . . : Dienstag, 3. Januar 2012 22:50:29
    Lease läuft ab. . . . . . . . . . : Mittwoch, 4. Januar 2012 22:50:29

    PING

    C:\>ping 192.168.1.106

    Ping wird ausgeführt für 192.168.1.106 mit 32 Bytes Daten:

    Antwort von 192.168.1.106: Bytes=32 Zeit=1ms TTL=64
    Antwort von 192.168.1.106: Bytes=32 Zeit=1ms TTL=64
    Antwort von 192.168.1.106: Bytes=32 Zeit=1ms TTL=64
    Antwort von 192.168.1.106: Bytes=32 Zeit<1ms TTL=64

    Ping-Statistik für 192.168.1.106:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),

    Ca. Zeitangaben in Millisek.:
    Minimum = 0ms, Maximum = 1ms, Mittelwert = 0ms

    Der Netzwerkname wurde nicht gefunden.
    C:\>net use N: \\192.168.1.106\backup
    Geben Sie den Benutzernamen für "192.168.1.106" ein: admin
    Geben Sie das Kennwort für "192.168.1.106" ein:
    Systemfehler 53 aufgetreten.

    Der Netzwerkpfad wurde nicht gefunden.
  • Here are the settings for my NAS:
    IP static 192.186.1.106
    Subnetmask 255.255.255.0
    Gateway 192.168.1.1
    DNS Setting 192.168.1.1

    Thanx
  • The static IP for the NAS should not be within the DHCP range assigned by your router (normally 192.168.1.100 through .200).

    Try setting the NAS to 192.168.1.10 (or something less than .100).
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    Heliosmultimedia wrote:
    Here are the settings for my NAS:
    IP static 192.186.1.106
    Subnetmask 255.255.255.0
    Gateway 192.168.1.1
    DNS Setting 192.168.1.1

    Thanx
    Is the 186 a typo in the post? Needs to be 168.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More