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

Also a note by default when no DHCP server is found on the DNS-323 the ip address will be 192.168.0.32.

You can direct hookup to your PC but you must set your PC's ip range in 192.168.0.xxx and connect to the DNS-323 via 192.168.0.32. Or once you have set your PC in the same range you can just use the easy search from there.

-Aaron

Ok still on direct connect, because I can not find it through my router, and I would like to take it step by step.

I reconfigured my LAN connect (I hadonly set the wireless to 192.168.0.x now also the wired, but still no succes

I cannot get connected through either direct throught the browser or through the easy link program.

however I do see that the easy link sees the dns (only through direct connection and not wireless through the router...) but I cannot select the configure button, see attachment

What now?

Thanks
Patrick

Windows IP Configuration


Ethernet adapter Local Area Connection:

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

Ethernet adapter Local Area Connection 2:

        Media State . . . . . . . . . . . : Media disconnected

Ethernet adapter Wireless Network Connection:

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


Windows IP Configuration


Ethernet adapter Local Area Connection:

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

Ethernet adapter Local Area Connection 2:

        Media State . . . . . . . . . . . : Media disconnected

Ethernet adapter Wireless Network Connection:

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

I tried that as well, no success....

wongo wrote:

frodo wrote:

You need to disconnect your wireless adapter for this to work.
Windows will not know how to route your packets otherwise.
You use the same network on both adapters. That is one to many ;-)

Off topic: That shouldn't be a problem, you don't have to route anyways, they are all on the same network.
On topic: Maybe mac-address filtering is enabled on the router.

Wongo routing is involved when choosing which interface to send out the packets!

As he has two interfaces. The only way to know which interface is being used is to check the routing table and the metric for each interface.

So to make this as simple as possible. If you try to connect to the DNS through a crossover cable disconnect any other interface being used!

Be aware that we are talking about two different networks here. One offered via the wireless LAN and one manually setup on the LAN. They are NOT the same network even if they share the same config.

pwvandeursen pointed out that he disconnected the DNS from the router and connected it directly to the PC.

Last edited by frodo (2007-07-06 13:42:51)

Ok, to get a few things clear and out of the way:

My router gives addresses from 192.168.0.3 to 192.168.0.155
the power led, network led and the drive led, all are on, full and blue.
I have disconnected the wireless network, when connected directly through a crosslink cable to the PC
I have resetted the dns through the button on the back
left the dns without power for a while and reconnected again.
unfortunately, I cannot see which IP address is give to the dns through the router.

Result,
no contact either directly or through the router......

HELP...

It only seams to work without wireless on as mentioned by DNS-323 Talker. do more people have this issue?

pwvandeursen wrote:

It only seams to work without wireless on as mentioned by DNS-323 Talker. do more people have this issue?

If you still have the DNS-323 connected directly to the PC, I'm going to take guess and say the answer is NO - most of us don't use it that way, it's sort of pointless.

If you have the DNS-323 connected to the router, I'm going to say no again, but this time because I can access my DNS-323 from any computer in my home network whether wired or wireless.

The DNS-323 is connected to the router, and if the laptop is connected to the router by a cable you can "contact" the DNS-323, but if it's connected by wireless you can't.  Do I have it right?

What do you mean by contact?  Are you using the EasySearch tool?  Canyou get to the admin interface by putting the ip address in your browser?
What sort of wireless router do you have?

The reasoning behind this line of questioning is that I believe some routers maintain some sort of separation between the wired & wireless segments, so this problem may not be related to the DNS-323

Ok, my setup for a example

Cable Modem > dlink router on 192.168.0.x subnet

router is managing DHCP

Wireless in the router and cable connections in the router are on the same subset - I have not see a router yet that will let you specify diff subnets for wireless and wired

Now when running the easy search util - it comes up to whatever DHCP assigned it - i forced the DNS unit using easy search util to 192.168.0.254 so I know where it always is.

laptop sees it - and it connects via wireless, laptop can also see it when connecting via cable


Now my question is - is your wireless and wired of different subnets?  If yes - configure them onto the same subnet.... or are you using a wired router and a access point?

if AP, leave the AP at its default settings except for security and turn off its DHCP and let it get its ip address from the wired router, and anything connecting via the AP will get its ip from the router thru the AP, the AP will be transparent to everything in the network.

Your wireless will gateway to 192.168.0.1(in my example) because the router gave it that, and the AP will auto forward packets to 192.168.0.1 because it got that info from the router as well.

when I had wired router and AP, the dlink ap defaulted to 192.168.0.50, it just acted like a bridge to everything wireless, the wired router never knew the difference.

Last edited by mykroft (2007-07-07 10:39:35)

So when you try mapping a nework drive on your laptop it doesn't work?

Open a folder on your laptop, select Tools>Map Network Drive.  Choose a free drive letter to map to on the Drive drop-down list, and for the Folder enter \\192.168.0.10\Volume_1.  Select "Reconnect at logon.   (Assuming that your DNS-323 is still at 192.168.0.10 IP.) 

That's all I did, everything works fine...

Yeah...the only version I've ever used is 3.5.0.0...doesn't bother me if it works or not, as I mapped via Windows, and did initial config of the DNS-323 from a desktop on my home network connected wired to the router...

DNS-323 admin web interface works fine from the laptops on wireless.

Hey, Fordem...how hard is it to set up a VPN on a home network?