Solved How to configure a name server

Toshiba / Satellite a100
March 11, 2015 at 03:31:36
Specs: Windows XP, x86 1995 MHz
I have a wifi bridge and I need to enter a name server for it manually in a receiver. The receiver has an ethernet connection socket but no wifi (Dreambox 7025+). When I connect the bridge and enable the DHCP, an IP address is assigned properly but network test on the receiver tells me that the name server is not configured correctly. When I use manual settings I enter Primary NS 213.42.20.20 and secondary 195.229.241.222 but this setting doesnt work. Is there another possibility for a name server?

See More: How to configure a name server

Report •


✔ Best Answer
March 12, 2015 at 11:14:15
Well, the whole situation is odd. With a proper DNS address, the device should communicate but it isn't. Honestly, I'm at a loss. We've tried everything I can think of. Without further investigation, I'd say this is indicative of a hardware problem

The only thing I can think of doing at this point would be to contact the device manufacturer and see if they can help. Perhaps there's something that isn't obvious that you have to enable.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***



#1
March 11, 2015 at 06:49:18
Is this in a home environment behind a SOHO Router?

If so, are you having issues with any other DHCP devices connected to the LAN?

If it is indeed in your home, rather than using the IP of name servers out on the internet, use the same one the rest of your DHCP clients are using. In a typical home environment your SOHO router will have something like the following TCP/IP settings:

LAN IP: 192.168.0.1
Subnet Mask: 255.255.255.0

All DHCP clients should show both the Default Gateway and the DNS IP's as being the LAN IP of the SOHO router (in this example: 192.168.0.1)

Then the router forwards DNS queries from clients to your ISP's DNS servers.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#2
March 11, 2015 at 07:21:02
Yes this is a home setup with a SOHO router. The TCP/IP you gave are correct. My other devices use the DNS that I gave above but they are not working in this receiver.

Report •

#3
March 11, 2015 at 11:08:42
Well, I'd suggest you try letting the router handle DNS requests in this case and see if it makes any difference. I honestly don't think it will, but it is worth checking and doing so rules out one possible issue.

Just FYI, for a device like this (or a printer, or access point, or server etc) I would statically assign TCP/IP settings. So if the above doesn't fix the issue. then I'd try changing the device over to static. Typically most SOHO router's have the following DHCP Scope: 192.168.0.100 to 192.168.0.199 So I would use an IP outside of the scope. Something like: 192.168.0.10 as the IP of the device.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***

message edited by Curt R


Report •

Related Solutions

#4
March 11, 2015 at 22:25:18
The out of scope IP didnt work. I am not sure how to let the router handle the DNS requests?

Report •

#5
March 12, 2015 at 05:33:00
As per my first response, you would set the router's LAN IP (which should also be the default gateway IP for all clients) as the DNS IP on the client in question.

For what it's worth, I'm not sure why you're using any DNS IP on your LAN other than the router's IP. Was this something you were told to do by your ISP? Were those DNS addresses assigned by the ISP? Or did it not work for DHCP clients with the default settings so you tried using your ISP's DNS addresses (assuming those are your ISP's DNS).

Normally when setting up a SOHO router in your home, once you connect the external (internet) port and get that working, the default is, DHCP is configured with the router's LAN IP as both DG and DNS. You would actually have to go in and manually change that DNS address. There's no real reason to, which is why I asked about that.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#6
March 12, 2015 at 10:00:19
Both primary and secondary NS that I mentioned in my original post are shown in the WLAN settings on the computer. They are also shown in another receiver with WLAN adapter. Only The "DHCP IP" is shown as the router IP exactly. I tried using the router IP as you suggested but still didnt work. Enabling DHCP on this receiver didnt work in providing a proper DNS automatically. That is what I find odd.

Report •

#7
March 12, 2015 at 11:14:15
✔ Best Answer
Well, the whole situation is odd. With a proper DNS address, the device should communicate but it isn't. Honestly, I'm at a loss. We've tried everything I can think of. Without further investigation, I'd say this is indicative of a hardware problem

The only thing I can think of doing at this point would be to contact the device manufacturer and see if they can help. Perhaps there's something that isn't obvious that you have to enable.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#8
March 12, 2015 at 12:06:52
You seem to be right. The device is discontinued and the maker isnt providing support. It is time to junk it. Thanks anyway.

Report •


Ask Question