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

Ripperjack wrote:

- Is this because the product is just a piece of junk, as a lot of people on the Internet claim?

Throw it away (in my arms please!) or just like it. It is definitely not a piece of junk

Have you set the name of the "Workgroup" to your workgroup? Your DNS doesn't seem to resolve the name correctly, so this may be the error?

having the sam problem as the first poster:

can access the dns via its ip, can also mount the share via its ip, but SOMETIMES i can NOT access it via its name, meaning \\ip\ or http://ip will work fine, but NOT \\name\ or http://name.

the "fix" for me is not using the name

will post here when i find the solution.

cheers

EDIT: this error occurs only sometimes
________________________
ch3snas, fw 1.02 beta, static ip

Last edited by w00 (2007-09-16 21:37:42)

kymlp wrote:

Like Fordem, I have no problem accessing via its name... I also have my home "workgroup name" defined everywhere: in the router, in the DNS323 and in all PC's. (I didn't bother with the share utility either!).

Same here - accessing via its name is not a problem for me.

Well from the responses, it does seam that it is an DNS error. However I am not sure how to result it, since I have done pretty much what all of your are eluding to in that:

- My D-Link 504 ADSL modem is running the DNS server as it were. The primary DNS setting of all my computers is pointing to the modem ( 192.168.0.1 )
- My modem and all computers are in the same workgroup, as is the DNS-323 unit.
- The DNS-323 is set to static IP in the admin page.

Could it be that since the DNS-323 is set to a static IP, it is not being listed in the modems DNS server as it is not getting an IP from the modems DHCP function?

I remember when I very first hooked the unit up to my network, before setting the IP to static in the admin pages, it did appear in the "My Network Places". Now, that is set to a static IP, it is no longer showing and that I have to use the IP number in the folder address bar to connect.

if you don't have a proper DNS then you could just add the desired name to you host file.

I have also experienced similar issue also.

I got an ASUS wl500g router with custom firmware http://oleg.wl500g.info/ and mac address assigned IP address (192.168.1.10) of the DNS-323.

Try to have a look here http://www.thekelleys.org.uk/dnsmasq/docs/FAQ and see for “Q: Names on the internet are working fine, but looking up local names from /etc/hosts or DHCP doesn't seem to work“. I had left the domain field blank in the router!

In the DNS-323 WEB configuration SETUP | DEVICE , I have set the Name and Description fields to same value, to make name consistent. Ping –a 192.168.1.10 resolved the device name as the Description field value!?

And as already mentioned, use same workgroup name.

Edit: (FW 1.3 and fonz fun_plug 0.3)

Last edited by FIB (2007-09-17 21:05:28)

Ripperjack wrote:

fordem wrote:

One way to find out would be to re-configure the DNS-323 to use DHCP and you could also use a DHCP reservation to keep the DNS-323 at a specific ip address.

Indeed. That was the first thing I was going to try. Set the DNS-323 back to DHCP and see if it appears in the "Microsoft Windows Network" listing.

The only thing to do then, if that does fix that symtom, is to work out if the D-Link 504 modem can do a DHCP reservation, since the DHCP setting options are pretty simplistic.

Update ( 6 hours later ) :-

Well trying to set the unit into DHCP mode didn't solve anything. As before I can access via IP number, but not by the units name. I double checked all my workgroup/domain settings and everything looks OK, but still no DNS resolution.

I guess the problem is that the D-link DSL-504 modem doesn't have a fill DNS server, as has been suggested. It just relays the DNS information from the ISP to my network and back again, so I would have to get the ISP to host my DNS-323 name, which an't going to happen any time soon.

So at this stage the easiest thing to do, without setting up an windows 2000/2003 server on my network, is to live with the IP access only. Since my network at this stage consists of the modem, the 8 port gigabit switch, the DNS-323 and 3 windows XP professional boxes. I currently do NOT run any servers, so everything is pretty much peer-to-peer.

I don't suppose there are any other ADSL routers out there that do have a fully blown DNS server built in?

I think a previous poster suggested editing the hosts file.

All tcp/ip implementations have a "hosts" file - with Windows XP it's in C:\Windows\System32\Drivers\etc - it's a text file which can be used to force name resolution - open the file with a text editor and you will see examples of what can be done with it.

FIB wrote:

In the DNS-323 WEB configuration SETUP | DEVICE , I have set the Name and Description fields to same value, to make name consistent. Ping –a 192.168.1.10 resolved the device name as the Description field value!?

...

In the DNS-323 WEB configuration SETUP | DEVICE , I have set the Name and Description fields to same value, to make name consistent. Ping –a 192.168.1.10 resolved the device name as the Description field value!?

Sorry, the ping issue is not fixed. I named my box nas, but see here:

C:\>ping -a 192.168.1.10

Pinger DNS-323.localnet [192.168.1.10] med 32 byte data:

Svar fra 192.168.1.10: byte=32 tid=1ms TTL=64

C:\>ping nas

Pinger nas [192.168.1.10] med 32 byte data:

Svar fra 192.168.1.10: byte=32 tid=3ms TTL=64

C:\>ping dns-323

Pinger dns-323.localnet [192.168.1.10] med 32 byte data:

Svar fra 192.168.1.10: byte=32 tid=1ms TTL=64

Not sure were the dns-323 name is comming from!?

I had to debug this a bit further on my Windows PC, so I had to explore the commands "nslookup" and "nbtstat".

I found that the old device named of my DNS box "dns-323" was cached and not renewed by my router. The router needed to rebooted before my box was consistent named "nas".

So I guess that my conclusion "set the Name and Description fields to same value, to make name consistent", was based on a glitch.

Sorry for any confusion.

Last edited by FIB (2007-10-01 22:07:23)

If you just add the name of the DNS to your hosts and LMhosts file, your computer will always know where it is.  Those files are checked first before looking for the dns server.