Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We are running a small LAN in our Company using a Cisco Router. Attached to this Router is QNAP NAS providing Access to Data via Windows Shares (we all use Windows 7 Computers). As the Router does not provide WiFi Access, we attached an old D-Link Router (that works fine) and use it as an Access Point. Everything is working fine (including Printing on the Network Printers, Internet Access, even Accessing other Windows PC in the Network) when accessing the network via WiFi. However it is not possible to access the windows shares on the QNAP any more. We allays get the error that the Network Path can not be found/is unavailable. We can see any reason why this is not working. Any ideas what the problem is and how to solve it?

Thanks a lot in Advance.

share|improve this question

1 Answer 1

up vote 0 down vote accepted

Any chance you have the D-Link attached via its WAN port? If so, you may consider taking a closer look to see if the D-Link has a "wireless access point" mode, which will probably be more appropriate for your configuration.

share|improve this answer
    
Thanks for the fast answer. Unfortunately the DIR-635 does not have a AP Mode. However I configured it to work as an AP according to the manual provided by D-Link. Besides the Windows Shares Issue the AP works very well. I could imagine that this is some DNS or WINS problem here but I do not really have any idea how to troubleshoot the problem any further. –  Thomas Jul 6 '11 at 14:10
    
How is the D-Link connected to the rest of your network? –  user48838 Jul 6 '11 at 14:25
    
Sorry did forget to specify this. It is connected using a LAN Port on the D-Link using an RJ45 wire directly to a LAN port on the Cisco Router. –  Thomas Jul 6 '11 at 15:20
    
Can the wireless clients successfully ping the QNAP - by name vs. IP address? –  user48838 Jul 6 '11 at 18:23
    
IP Works fine but Name does not. Looking at the protocol by wireshark, it seems the query for the share name goes out to the wrong address (from my pc 192.168.1.20 to 192.168.1.255 and there is no server that has this 255 address). Thanks again I really appreciate your help here! –  Thomas Jul 7 '11 at 7:30

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.