DSM-G600, DNS-3xx and NSA-220 Hack Forum

What interface are you trying to use?  ethernet or usb?

Last edited by mig (2007-03-30 04:43:09)

A direct Ethernet connection is possible.  You need to use a 'cross-over' cable http://en.wikipedia.org/wiki/Ethernet_crossover_cable (or crossover adapter) to connect the DNS-323 ethernet port to your computer's ethernet port.   You may also want to assign a static IP address to the DNS-323 that is on the same subnet as your computer, unless your computer is running a dhcp service.

Lance wrote:

thanks! I was hoping i won't need a cross over cable because i dont' have one with me haha... (here i thought they provide me with a straight through cable. it must work) lol

If your computer has a GigE interface, too, it should work with a standard cable.

By default the DNS-323 will have a self-assigned IP address of 192.168.0.32  if there is no DHCP server available.  You should be able to set your computer, temporarly, to 192.168.0.<any number other than 32> and then connect to the DNS-323 with your web browser http://192.168.0.32 and follow the setup steps in the manual.  You can then give the DNS-322 a static IP address in your default subnet, then change you computer back to it's original IP address.  I don't know why D-Link says you can't direct connect, the easy search utility might have a problem with direct connect, but the DNS-323 should not.

Last edited by mig (2007-04-01 03:11:08)

What is the ip address your computer is using?  Are you using any firewall software?  Can you further elaborate on what 'doesn't work' means.  Do you get any error messages?

Last edited by mig (2007-04-01 07:29:08)

Can you 'ping' the DNS-323...
At the command prompt do you get any response if you type c:\> ping <ip_address_of_DNS-323> ?
Can you post the output of the route command... c:\>route print

Lance,
The information you posted is a great help   I think I see how your network adapters need to be configured.

I believe you have two NICs on your PC:
1) Atheros AR5001X wireless nic  - connects to the internet
2) Realtek TRL8139/810x wired nic - connects to the DNS-323

In the first image (where partial success was reported) I see the IP address of the Realtek wired nic is set to 192.168.0.32.  I believe (correct me if I'm wrong) this is the ethernet port which you have the DNS-323 connected via a crossover cable.  You need to manually change the IP address on the Realtek wired nic to 192.168.0.33, because the DNS-323 defaults to using 192.168.0.32.  Each device on the network must have a unique number after the third dot [192.168.0.<this number must be unique>]

'ipconfig'  is a command to list the ip address information for each network port on your computer.  If you run C:> ipconfig /all  you will see how each network card is setup.

Reboot (or power cycle) the DNS-323 with no network cable attached (this will make sure the DNS configures itself to use the default IP of 192.168.0.32.  Then reboot your computer (as usual) so you can access the internet.  Finally, manually set the IP address for the Realtek wired nic to 192.168.0.33 (subnet mask 255.255.255.0, gateway 192.168.0.1) and attach the crossover cable between the DNS-323 and the Realtek wired nic.

You should be able to ping 192.168.0.32 (which is the ip address of your DNS-323).  Then start firefox and use http://192.168.0.32 to connect to your DNS-323.  Your PC  should be able to have access to the internet (via the wireless card) and the DNS-323 via the crossover cable.

If this doesn't work, post the results of the 'ipconfig /all' and 'route print' commands

Lance, I'm sorry this is not working for you.  I tried this setup tonight, so I know it works. 

I think you may be mis-understanding the static IP assignment [192.168.0.33], this IP address needs to be setup for the wired network card, to which, the DNS-323 is attached.  The crossover cable is a point-to-point, network, using the subnet 192.168.0.x and having two devices attached to this subnet, device 32 (the DNS-323), and device 33 (your PC's wired NIC).  Your PC also has a wireless NIC and that will be using a different subnet (and IP address) which is assigned by the DHCP server in the wireless access point your PC connects to (via wireless).  You keep the wireless NIC setup whatever way (most likely DHCP) you need to for internet access.  With this setup your PC is connected to two different networks at the same time, each with a different IP address and on a different subnet.  The wireless one, with internet access; and the wired one, with the DNS-323 attached.

I used a PC [WinXP Home] with a Belkin wireless card and a SiS 900 wired NIC on the motherboard.  I setup the wireless network card to use DHCP which connects (via wireless) to a Linksys WRT54g router [the router is connected to a cable modem for internet access].  The wireless network card is automatically assigned a IP address, DNS and gateway which, for my network, is 192.168.1.111. (this is device 111 on the 192.168.1.x subnet)  I setup the wired network card with a static IP address of 192.168.0.33 and a netmask of 255.255.255.0 (I left the default gateway and the DNS blank for the wired NIC).  This is the output of the ifconfig command

C:\>ipconfig
Windows IP Configuration

Ethernet adapter Wireless Network Connection 2:

        Connection-specific DNS Suffix  . : 
        IP Address. . . . . . . . . . . . : 192.168.1.111
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 192.168.0.33
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :

I then turned on the DNS-323 with no network cable attached and waited for the blue lights to stop blinking.  This will force the DNS-323 to assign itself the fail-over IP address of 192.168.0.32.  I then connected the DNS-323 to the wired interface of the PC.  I could ping the DNS-323 [at 192.168.0.32] and I could ping a computer (www.google.com) on the internet.  I used http://192.168.0.32 to access the DNS-323 web admin pages and could surf the web in another tab of the same firefox browser.

C:\>ping 192.168.0.32

Pinging 192.168.0.32 with 32 bytes of data:

Reply from 192.168.0.32: bytes=32 time<1ms TTL=64
Reply from 192.168.0.32: bytes=32 time<1ms TTL=64
Reply from 192.168.0.32: bytes=32 time<1ms TTL=64
Reply from 192.168.0.32: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.32:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ping www.google.com

Pinging www.l.google.com [72.14.253.99] with 32 bytes of data:

Reply from 72.14.253.99: bytes=32 time=18ms TTL=240
Reply from 72.14.253.99: bytes=32 time=16ms TTL=240
Reply from 72.14.253.99: bytes=32 time=15ms TTL=240
Reply from 72.14.253.99: bytes=32 time=17ms TTL=240

Ping statistics for 72.14.253.99:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 18ms, Average = 16ms

C:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 30 bd fa 14 4f ...... Belkin Wireless 54Mbps Desktop Adapter - Packet
Scheduler Miniport
0x3 ...00 0d 87 f1 a3 33 ...... SiS 900-Based PCI Fast Ethernet Adapter - Packet
 Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1   192.168.1.111       25
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.0.0    255.255.255.0     192.168.0.33    192.168.0.33       20
     192.168.0.33  255.255.255.255        127.0.0.1       127.0.0.1       20
    192.168.0.255  255.255.255.255     192.168.0.33    192.168.0.33       20
      192.168.1.0    255.255.255.0    192.168.1.111   192.168.1.111       25
    192.168.1.111  255.255.255.255        127.0.0.1       127.0.0.1       25
    192.168.1.255  255.255.255.255    192.168.1.111   192.168.1.111       25
        224.0.0.0        240.0.0.0     192.168.0.33    192.168.0.33       20
        224.0.0.0        240.0.0.0    192.168.1.111   192.168.1.111       25
  255.255.255.255  255.255.255.255     192.168.0.33    192.168.0.33       1
  255.255.255.255  255.255.255.255    192.168.1.111   192.168.1.111       1
Default Gateway:       192.168.1.1
===========================================================================
Persistent Routes:
  None

Last edited by mig (2007-04-05 12:13:58)

Doh! I completely missed the wireless NIC is getting a 192.168.0.x subnet address from the DHCP server.