D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: kwmama on June 28, 2010, 07:09:50 PM
-
Clearly I have no background in this area but need some help to reconnect to our dns 323 used wirelessly for back up of my laptop. I believe I may have deleted the driver at some point as it no longer shows up on "my computer" and I believe an error message indicated such at some point. A quick look by someone else indicated that this may no be the problem. Regardless, I am not able to connect to the dns 323. Any "for dummies" advice?
-
Reboot it.
Can you ping it?
Can you access the admin web page?
Can you access by ip address?
-
There is no driver needed to connect to your DNS-323 so you didn't delete it - it is possible however that you may have made changes to your wireless network that cause you to be no longer able to reach the DNS-323, and it is also possible that updates to Windows may be responsible.
Follow the steps suggested by dosborne as a start - and let us know the results
-
Finally getting back to this - very intimidating since I don't know about any of this. So I figured out how to ping the IP address and it said destination host unreachable but then 4 packets sent and received with 0 lost. What does this mean? ???
-
And I don't seem to be able to access by ip address (although I'm not 100% confident that I'm doing all of this correct)
-
And I don't know if this will help but I'm fairly certain that I deleted something (when I caused the original problem) as I really believe that there was another icon on "my computer" but I deleted it when I was having some trouble connecting with competing ip addressess the night before I had to give a big presentation (although I can't remember for sure what I was having trouble with). Currently DNS323 volume 1 with th ip address shows up on "my computer". But when I try to open it, it indicates that it is not accessible or able to communicate with it. (and that it network diagnostics pinged the ip address and it didn't respond) I don't have any trouble connecting to our wireless network.
-
If you don't know the ip address of the DNS323, try running the easy search utility to find it on your network.
-
I believe that I have the ip address correct. It seems more that my laptop is not able to communicate with DNS323
-
Open a command prompt - type ipconfig - post the results - ping the ip address of the DNS-323 - post the results.
If you can't ping the DNS-323, you're not communicating with it.
To have a destination host unreachable response when trying to ping a host on your local network is quite unusual.
-
okay here's the ipconfig. I deleted some of the numbers since i'm leery about posting everything and I don't know enough to decide what should be kept back.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ipconfig
Windows IP Configuration
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : starWLAN
Link-local IPv6 Address . . . . . : fe80::b10a:eca:3bae:
IPv4 Address. . . . . . . . . . . : 192.168.
Subnet Mask . . . . . . . . . . . : 255.255.
Default Gateway . . . . . . . . . : 192.168
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : uwaterloo.ca
Tunnel adapter Local Area Connection* 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Local Area Connection* 12:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:c34
Link-local IPv6 Address . . . . . : fe80::c34:96c:3f
Default Gateway . . . . . . . . . : ::
Tunnel adapter Local Area Connection* 13:
Connection-specific DNS Suffix . : starWLAN
Link-local IPv6 Address . . . . . : fe80::5efe:192.
Default Gateway . . . . . . . . . :
C:\Windows\system32>
-
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping 192.168
Pinging 192.168.0.102 with 32 bytes of data:
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Ping statistics for 192.168
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Windows\system32>
-
Posting a 192.168 address is 100% safe as it does not open you to any attacks.
Knowing what your local ip address is will be critical in resolving your issue as it seems you may have a routing problem, possibly a bad gateway address, but in any case it should not matter if both systems are on the same subnet.
Posting your subnet mask is also important and does not reveal any sensitive info.
-
We need the 192 numbers and subnet mask as indicated by previously. It is possible that you are using the wrong subnet for the DNS and Laptop.
Regards,
Wiggs
-
okay...
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ipconfig
Windows IP Configuration
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : starWLAN
Link-local IPv6 Address . . . . . : fe80::b10a:eca:3bae:e426%11
IPv4 Address. . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : uwaterloo.ca
Tunnel adapter Local Area Connection* 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Local Area Connection* 12:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e74:88:103b:3f57:ff9a
Link-local IPv6 Address . . . . . : fe80::88:103b:3f57:ff9a%12
Default Gateway . . . . . . . . . : ::
Tunnel adapter Local Area Connection* 13:
Connection-specific DNS Suffix . : starWLAN
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.0.101%15
Default Gateway . . . . . . . . . :
C:\Windows\system32>
-
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Ping statistics for 192.168.0.102
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Windows\system32>
-
Post the results of pinging it by name. It sure looks like its ip address is not *.102
-
There is a problem of some sort with the ip stack on 192.168.0.101 - the destination host unreachable message is erroneous.
Normally - a destination host unreachable message will be returned by a router in instances where it does not have a route to the destination network, in this case it is being returned by the ip stack in the PC itself, and from a host on the destination network.
If the DNS-323 were not at 192.168.0.102, what I would expect to see is four "request timed out" messages, followed by a summary indicating that four packets were sent, and none were received, 100% packet loss - what we are in fact seeing is four packets sent, four packets received, 0% packet loss.
Open a command prompt and do a "route print" and post the results.
-
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>route print
===========================================================================
Interface List
11 ...00 22 5f 30 96 e8 ...... Atheros AR5B91 Wireless Network Adapter
10 ...00 e0 b8 e9 9a f4 ...... Marvell Yukon 88E8040 PCI-E Fast Ethernet Contro
ller
1 ........................... Software Loopback Interface 1
13 ...00 00 00 00 00 00 00 e0 isatap.starWLAN
25 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
12 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
14 ...00 00 00 00 00 00 00 e0 6TO4 Adapter
16 ...00 00 00 00 00 00 00 e0 isatap.{303BC344-9B58-4EB4-97AD-724DA608135B}
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.101 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.0.0 255.255.255.0 On-link 192.168.0.101 281
192.168.0.101 255.255.255.255 On-link 192.168.0.101 281
192.168.0.255 255.255.255.255 On-link 192.168.0.101 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.0.101 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.0.101 281
===========================================================================
Persistent Routes:
None
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
12 18 ::/0 On-link
1 306 ::1/128 On-link
12 18 2001::/32 On-link
12 266 2001:0:4137:9e76:2c4d:1d9e:3f57:ff9a/128
On-link
11 281 fe80::/64 On-link
12 266 fe80::/64 On-link
25 286 fe80::5efe:192.168.0.101/128
On-link
12 266 fe80::2c4d:1d9e:3f57:ff9a/128
On-link
11 281 fe80::b10a:eca:3bae:e426/128
On-link
1 306 ff00::/8 On-link
12 266 ff00::/8 On-link
11 281 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
C:\Windows\system32>
-
Does this help?
-
???
Any thoughts? My big worry is that I haven't backed up the laptop for months
-
Can any one help me reconnect to the DNS-323 with this info?