Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Windows 8.1 and RN102 - share problem
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
04:18 AM
2015-07-14
04:18 AM
Windows 8.1 and RN102 - share problem
Hi, I had a RN102, and I very satisfied.
I recently buy 2 windows 8.1 laptops.
I Can't see my shared folder, I just can see the NAS in the network.
On my old windows 7 laptops, I still can access to my NAS.
On my new windows 8.1 laptops, I can access to my another IOMEGA NAS.
I Can't see the problem.
Regards.
I recently buy 2 windows 8.1 laptops.
I Can't see my shared folder, I just can see the NAS in the network.
On my old windows 7 laptops, I still can access to my NAS.
On my new windows 8.1 laptops, I can access to my another IOMEGA NAS.
I Can't see the problem.
Regards.
Message 1 of 13
Labels:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
04:27 AM
2015-07-14
04:27 AM
Re: Windows 8.1 and RN102 - share problem
What protocol are you using to access the share(s) on your RN102? Is it SMB? Is it FTP?
Message 2 of 13
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
04:32 AM
2015-07-14
04:32 AM
Re: Windows 8.1 and RN102 - share problem
It might help if you set the workgroup on the NAS to match yours (note this is not the same as the homegroup).
Also, what happens if you enter \\nasname or \\nas.ip.address into the windows explorer address bar?
What firmware are you running?
Also, what happens if you enter \\nasname or \\nas.ip.address into the windows explorer address bar?
What firmware are you running?
Message 3 of 13
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
04:33 AM
2015-07-14
04:33 AM
Re: Windows 8.1 and RN102 - share problem
Yes RAIDar detects it.
When I click browse, it's empty.
When I click browse, it's empty.
Message 4 of 13
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
04:34 AM
2015-07-14
04:34 AM
Re: Windows 8.1 and RN102 - share problem
I use the 6.2.4 version of the firmware.
Message 5 of 13
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
04:35 AM
2015-07-14
04:35 AM
Re: Windows 8.1 and RN102 - share problem
If I enter \\nasname or \\nas.ip.address into the windows explorer address bar, it's empty.
Message 6 of 13
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
04:53 AM
2015-07-14
04:53 AM
Re: Windows 8.1 and RN102 - share problem
I use SMB, HTTP, HTTPS protocol.
Message 7 of 13
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
05:07 AM
2015-07-14
05:07 AM
Re: Windows 8.1 and RN102 - share problem
@goffy:
Are you accessing the shares wirelessly on your Windows 8.1 laptops?
Have you tried to access the shares via a wired connection?
Is there a software firewall or anti-virus installed on your Windows 8.1 laptops like Norton or Kaspersky? If yes, try to disable it.
Are you accessing the shares wirelessly on your Windows 8.1 laptops?
Have you tried to access the shares via a wired connection?
Is there a software firewall or anti-virus installed on your Windows 8.1 laptops like Norton or Kaspersky? If yes, try to disable it.
Message 8 of 13
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
07:44 AM
2015-07-14
07:44 AM
Re: Windows 8.1 and RN102 - share problem
I disable windows firewall and defender and ma antivirus. Still the same. All is wired.
Message 9 of 13
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
08:51 AM
2015-07-14
08:51 AM
Re: Windows 8.1 and RN102 - share problem
There is no failure indication?
goffy wrote: If I enter \\nasname or \\nas.ip.address into the windows explorer address bar, it's empty.
Message 10 of 13
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
09:12 AM
2015-07-14
09:12 AM
Re: Windows 8.1 and RN102 - share problem
No, everything fine, but it's empty.
Message 11 of 13
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
11:18 AM
2015-07-14
11:18 AM
Re: Windows 8.1 and RN102 - share problem
Maybe try opening a windows cmd box and enter
and enter the NAS admin password at the prompt (assuming you get one).
Use the real NAS IP address of course.
If you already are using T as a drive letter, just use a different letter.
net use * delete
net use T:\ \\NAS.IP.ADDR\data /user:admin
and enter the NAS admin password at the prompt (assuming you get one).
Use the real NAS IP address of course.
If you already are using T as a drive letter, just use a different letter.
Message 12 of 13
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-07-14
12:29 PM
2015-07-14
12:29 PM
Re: Windows 8.1 and RN102 - share problem
C:\Users\Aurele>net use T:\ \\192.168.1.10 /user:admin
L'erreur système 67 s'est produite.
Nom de réseau introuvable--> Network name not found
It's strange because :
C:\Users\Aurele>ping 192.168.1.10
Envoi d'une requête 'Ping' 192.168.1.10 avec 32 octets de données :
Réponse de 192.168.1.10 : octets=32 temps<1ms TTL=64
Réponse de 192.168.1.10 : octets=32 temps=1 ms TTL=64
Réponse de 192.168.1.10 : octets=32 temps=1 ms TTL=64
Réponse de 192.168.1.10 : octets=32 temps=6 ms TTL=64
Statistiques Ping pour 192.168.1.10:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 0ms, Maximum = 6ms, Moyenne = 2ms
L'erreur système 67 s'est produite.
Nom de réseau introuvable--> Network name not found
It's strange because :
C:\Users\Aurele>ping 192.168.1.10
Envoi d'une requête 'Ping' 192.168.1.10 avec 32 octets de données :
Réponse de 192.168.1.10 : octets=32 temps<1ms TTL=64
Réponse de 192.168.1.10 : octets=32 temps=1 ms TTL=64
Réponse de 192.168.1.10 : octets=32 temps=1 ms TTL=64
Réponse de 192.168.1.10 : octets=32 temps=6 ms TTL=64
Statistiques Ping pour 192.168.1.10:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 0ms, Maximum = 6ms, Moyenne = 2ms
Message 13 of 13