DHCP and DNS trouble
Pierre Jelenc
I have a hard-wired DSL connection that has given me no trouble (after a
rocky installation) except for one thing: After a reboot (eCS 1.2) many
sites are inaccessible, most notably anything within google.com. Most
other sites are perfectly well behaved, however.
This problem appears to last for an hour, coinciding with the lease
renewal as shown by the DHCP monitor. The DNS shown is 192.168.1.1 i.e.
the router, which is always on and is not rebooted during that time.
After an hour, the problem disappears until the next reboot, when it
*always* comes back.
Is this an OS/2 problem? Something not being done properly during the
first DHCP request, perhaps?
Thanks,
Pierre
--
Pierre Jelenc
The Gigometer www.gigometer.com
The NYC Beer Guide www.nycbeer.org
Peter
I will give this one a go, however it would help to have some more
info first.
> I have a hard-wired DSL connection that has given me no trouble (after a
> rocky installation) except for one thing: After a reboot (eCS 1.2) many
> sites are inaccessible, most notably anything within google.com. Most
> other sites are perfectly well behaved, however.
>
> This problem appears to last for an hour, coinciding with the lease
> renewal as shown by the DHCP monitor. The DNS shown is 192.168.1.1 i.e.
> the router, which is always on and is not rebooted during that time.
Ok, so you are using DHCP on your local LAN....
>
> After an hour, the problem disappears until the next reboot, when it
> *always* comes back.
Lets start with some more info on the H/W you use.
1. What TYPE (IE Make and Model if known) of Router are you using?
2. As its a DSL link, do you know if it is operating in PPPoA or
PPPoE mode?
3. Did YOU configure (or have online access to) the Router or did
your ISP provide it? If you have access to the Router then its
configuration would help as well...
4. Now list the CONTENTS of the text file x:\MPTN\ETC\RESOLVE2. I am
most interested in the lines that start -
domain <something else here>
and
nameserver <an ip address here> There could be multiple lines of
these.
List any other TYPE of records present (there probably aren't; any)...
Start of your Testing...
And now for the status of a few things WHEN ITS WORKING.
The NETSTAT command only DISPLAY info, it changes nothing , but
IFCONFIG WILL try to change things if you add extra parameters, so
take care you only provide ONE word after IFCONFIG... Run IFCONFIG -?
for help to see what can be done) -
From your eCS machine run the following from a command line prompt and
report ALL input AND output -
netstat -a This displays your machines TCP/IP interfaces and the IP
addresses they are using.
netstat -r This displays the ROUTING table your machine is using (IE
routes both configured and learnt).
From the FIRST output, take the INTERFACE number as X and enter
ifconfig lanX
EG netstat -a on my machine currently displays -
addr 192.168.206.249 Interface 0 mask 0xffffff00 broadcast
192.168.206.255
Multicast addrs:
224.0.0.1
addr 127.0.0.1 Interface 9 mask 0xff000000 broadcast 127.0.0.1
Multicast addrs:
224.0.0.1
From this I can see that I have 1 real interface configured (interface
0 which becomes lan0 for the next command) plus a virtual LOOPBACK
interface (interface 9 or lan9, also known as interface "lo")
So I then do -
ifconfig lan0
And you should get something like this -
lan0: flags=8843<UP,BROADCAST,RUNNING,MULTICAST,LOOPBRD>
inet 192.168.206.249 netmask 0xffffff00 broadcast
192.168.206.255
Essentially these should display most of the same info (just formatted
different).
Now run NSLOOKUP to see what your DNS info is saying and enter
"www.google.com" as input). Use EXIT to exit . My one shows my own
local DNS so it will be VERY different to yours, BUT it shows that I
have a LOCAL Caching DNS in use. -
nslookup
Default Server: <local hostname hidden>
Address: 192.168.206.241
> www.google.com
Server: <local hostname hidden>
Address: 192.168.206.241
Non-authoritative answer:
Name: www.l.google.com
Addresses: 66.102.7.99, 66.102.7.104
Aliases: www.google.com
Now REPEAT these tests when things are NOT working. We need to see
what DIFFERENCES appear.
Lastly, how many DEVICES do you have on this LAN and IF more than 1
PC, are ALL devices experiencing the same problem?
> Is this an OS/2 problem?
I doubt it, its likely to be something your ISP is doing, but once we
know more about what is happening we may be able to suggest something.
Are you 100% sure the "sticky" DNS issue only appears with
www.google.com and no other site (such as www.ibm.com)?
Lets start with that and see what we get.
Good luck............pk.
--
Peter from Auckland.
Pierre Jelenc
>
> Lets start with some more info on the H/W you use.
> 1. What TYPE (IE Make and Model if known) of Router are you using?
It's Netopia. No obvious model name anywhere, but there's a sticker at the
bottom that says "2247NWG-T Type: 0X21" as well as long serial numbers.
It has 4 Ethernet ports, plus wireless (that I am not using)
> 2. As its a DSL link, do you know if it is operating in PPPoA or
> PPPoE mode?
PPPoE
> 3. Did YOU configure (or have online access to) the Router or did
> your ISP provide it? If you have access to the Router then its
> configuration would help as well...
I can access it. System status says:
System Name:
Netopia 2247-02
F/W Version:
7.7.4r3
DSL F/W Version:
DSP 7.2.3.0, HAL 7.2.1.0
Standard:
DMT
WAN Information:
IP Address:
166.84.167.2
Mask:
255.255.255.255
Primary DNS:
198.7.0.5
Secondary DNS:
166.84.67.2
Default Gateway:
166.84.64.2
VPI/VCI:
0/35
NAT:
On
LAN Information:
MAC Address:
00:1f:c4:81:6c:a0
IP Address:
192.168.1.1
IP Mask:
255.255.255.0
IP Range:
192.168.1.1-192.168.1.254
DHCP:
Server
DHCP Start IP:
192.168.1.101
DHCP Pool Size:
154
DHCP Range:
192.168.1.101-192.168.1.254
> 4. Now list the CONTENTS of the text file x:\MPTN\ETC\RESOLVE2. I am
> most interested in the lines that start -
> domain <something else here>
> and
> nameserver <an ip address here> There could be multiple lines of
> these.
domain
nameserver 192.168.1.1
Nothing else. This appears to be generated automatically, as it is
re-created if it is erased.
> Start of your Testing...
> And now for the status of a few things WHEN ITS WORKING.
>
> The NETSTAT command only DISPLAY info, it changes nothing , but
> IFCONFIG WILL try to change things if you add extra parameters, so
> take care you only provide ONE word after IFCONFIG... Run IFCONFIG -?
> for help to see what can be done) -
> From your eCS machine run the following from a command line prompt and
> report ALL input AND output -
> netstat -a This displays your machines TCP/IP interfaces and the IP
> addresses they are using.
[c:\]netstat -a
addr 127.0.0.1 Interface 9 mask 0xff000000 broadcast 127.0.0.1
Multicast addrs:
224.0.0.1
addr 192.168.1.102 Interface 0 mask 0xffffff00 broadcast 255.255.255.255
Multicast addrs:
224.0.0.1
> netstat -r This displays the ROUTING table your machine is using (IE
> routes both configured and learnt).
[c:\]netstat -r
destination router netmask metric flags intrf
default 192.168.1.1 0.0.0.0 0 UGP lan0
127.0.0.1 127.0.0.1 255.255.255.255 0 UH lo
166.84.1.3 192.168.1.1 255.255.255.255 0 UGHW lan0
192.168.1 192.168.1.102 255.255.255.0 0 UC lan0
> From the FIRST output, take the INTERFACE number as X and enter
> ifconfig lanX
[c:\]ifconfig lan9
ioctl (SIOCGIFFLAGS): No such device or address
[c:\]ifconfig lan0
lan0: flags=8843<UP,BROADCAST,RUNNING,MULTICAST,LOOPBRD>
inet 192.168.1.102 netmask 0xffffff00 broadcast 255.255.255.255
> Now run NSLOOKUP to see what your DNS info is saying and enter
> "www.google.com" as input). Use EXIT to exit . My one shows my own
> local DNS so it will be VERY different to yours, BUT it shows that I
> have a LOCAL Caching DNS in use. -
I don't get a prompt: the cursor goes to the start of the next line and
just sits there, and nothing I type does anything until I stop with ^C.
> Lastly, how many DEVICES do you have on this LAN and IF more than 1
> PC, are ALL devices experiencing the same problem?
Just this machine (Dell desktop).
> Are you 100% sure the "sticky" DNS issue only appears with
> www.google.com and no other site (such as www.ibm.com)?
It's not just Google, but that's the one I stumble upon every time because
of Gmail, Google News, and Google Reader. I know on the other hand that
cdbaby.com and any musicians' sites hosted on hostbaby.com are fine right
after reboot, and so is the BBC news site.
Peter
On Sat, 6 Jun 2009 02:23:45 UTC, rc...@panix.com (Pierre Jelenc) wrote:
> > 1. What TYPE (IE Make and Model if known) of Router are you using?
>
> It's Netopia.
I don't know that one, however the info you provided has told me most
of what is useful thanks.
... snip ...
> WAN Information:
> IP Address:
> 166.84.167.2
> Mask:
> 255.255.255.255
> Primary DNS:
> 198.7.0.5
> Secondary DNS:
> 166.84.67.2
> Default Gateway:
> 166.84.64.2
All useful stuff and it looks fairly normal to me.
> LAN Information:
> MAC Address:
> 00:1f:c4:81:6c:a0
> IP Address:
> 192.168.1.1
> IP Mask:
> 255.255.255.0
> IP Range:
> 192.168.1.1-192.168.1.254
> DHCP:
> Server
> DHCP Start IP:
> 192.168.1.101
> DHCP Pool Size:
> 154
> DHCP Range:
> 192.168.1.101-192.168.1.254
Ok, all the DHCP stuff looks normal as well.
> > 4. Now list the CONTENTS of the text file x:\MPTN\ETC\RESOLVE2. I am
> > most interested in the lines that start -
> > domain <something else here>
> > and
> > nameserver <an ip address here> There could be multiple lines of
> > these.
>
> domain
> nameserver 192.168.1.1
>
> Nothing else. This appears to be generated automatically, as it is
> re-created if it is erased.
Again all that looks normal to me. The refresh of the file means your
Router is providing all these values via DHCP, which it is normal and
working ok.
> > And now for the status of a few things WHEN ITS WORKING.
Did you repeat these tests when it was NOT working? Without that there
is nothing I can compare it with...
> [c:\]netstat -a
> addr 127.0.0.1 Interface 9 mask 0xff000000 broadcast 127.0.0.1
> Multicast addrs:
> 224.0.0.1
>
> addr 192.168.1.102 Interface 0 mask 0xffffff00 broadcast 255.255.255.255
> Multicast addrs:
> 224.0.0.1
Ok, your interfaces are generated in a different order to mine (mine
is 0 first, then 9), but otherwise they look fine to me, EXCEPT that
your broadcast address is a little unusual (255.255.255.255) for the
192.268.1 Network segment,, but I don't THINK this will be causing
your problem... unless the Router is doing something odd with it.
This info is coming FROM your Router DHCP server.
The 192.168.1.x network is a Class C network so its BROADCAST address
is usually 192.168.1.255. Normally its only the LAST Octet in a Class
C address that is set to 255 for BROADCAST (the LAST high order value
for the IP address). As you do not have any other networks locally, IE
no other ROUTES, then this is _probably_ not a problem. One thing we
could try here is to disables DHCP on your eCS machine and set the IP
values manually, AND bypass your Router DHCP data, ,just to check if
it is causing the issue, but it depends on how confident you are at
trying manual TCP/IP Config entries... If you want to give it a go,
make sure you can restore the values to normal and try the following,
otherwise skip it... If you make ANY changes, they will only be STORED
if you SAVE the changes at the end of the configuration.
1. Open the TCP/IP Configuration Notebook and on the NETWORK TAB,
confirm that the LAN 0 interface is ENABLED.
2. It probably has "Automatically, using DHCP" checked. Change this
to "Manually using " and set -
IP address to "192.168.1.105" (this uses a spare address that should
not clash with anything you currently use),
Subnet Mask to "255.255.255.0" (this will be the same as you
currently use)
3. Select the ROUTING TAB. Set up a DEFAULT Route that matches your
DHCP Route (IE pointing at 192.168.1.1).
4. Select the HOST NAMES TAB. Set up your DNS entries to match your
DHCP DNS entries. You can use the Same ones set by your DHCP setting.
NOTE; Your Router appears to want to act as a DNS Forwarder, so it
lists itself for your DHCP setup. With the MANUAL configuration you
could use the entries in your Router that point at your ISP DNS
servers instead. This eliminates the Router as a potential cause of
problems (but I think this is unlikely however it would be nice to
confirm this).
> [c:\]netstat -r
> destination router netmask metric flags intrf
>
> default 192.168.1.1 0.0.0.0 0 UGP lan0
> 127.0.0.1 127.0.0.1 255.255.255.255 0 UH lo
> 166.84.1.3 192.168.1.1 255.255.255.255 0 UGHW lan0
> 192.168.1 192.168.1.102 255.255.255.0 0 UC lan0
These look normal to me. 127.0.0.1 is YOUR Loopback address, and
192.168.1 is a NETWORK Route (Mask = 255.255.255.0) for your LAN.
166.84.1.3 is a HOST route and points at your router which is also
your default Gateway and is correct.
> > From the FIRST output, take the INTERFACE number as X and enter
> > ifconfig lanX
>
> [c:\]ifconfig lan9
> ioctl (SIOCGIFFLAGS): No such device or address
Sorry, that actually needs to be "ifconfig lo", but don't worry, its
not a problem.
> [c:\]ifconfig lan0
> lan0: flags=8843<UP,BROADCAST,RUNNING,MULTICAST,LOOPBRD>
> inet 192.168.1.102 netmask 0xffffff00 broadcast 255.255.255.255
This all looks good to me.
> > Now run NSLOOKUP to see what your DNS info is saying and enter
> > "www.google.com" as input). Use EXIT to exit . My one shows my own
> > local DNS so it will be VERY different to yours, BUT it shows that I
> > have a LOCAL Caching DNS in use. -
>
> I don't get a prompt: the cursor goes to the start of the next line and
> just sits there, and nothing I type does anything until I stop with ^C.
This sounds wrong to me.
"nslookup hostname" starts nslookup using the DEFAULT DNS Server and
automatically looks up the hostname using your DEFAULT DNS entries,
and then exits like this -
nslookup xxx
Server: <name removed>
Address: 192.168.206.241
Name: xxx.<name removed>
Address: 192.168.206.241
and exits back to the prompt. for the above example I used the
hostname of my DNS server.
"Nslookup" (with NO hostname) starts nslookup in interactive mode,
tells you the CURRENT DNS server being used, and waits for the next
command with a > prompt. You need to type EXIT to leave nslookup -
nslookup
Default Server: <name removed>
Address: 192.168.206.241
> exit
in interactive mode you can enter many optional commands -
nslookup
Default Server: <name removed>
Address: 192.168.206.241
> ?
Commands: (identifiers are shown in uppercase, [] means
optional)
NAME - print info about the host/domain NAME using default server
NAME1 NAME2 - as above, but use NAME2 as server
help or ? - print info on common commands
set OPTION - set an option
all - print options, current server and host
[no]debug - print debugging information
[no]d2 - print exhaustive debugging information
[no]defname - append domain name to each query
[no]recurse - ask for recursive answer to query
[no]search - use the search list
[no]vc - always use a virtual circuit
domain=NAME - set default domain name to NAME
port=x - use TCP/IP port number x
srchlist=N1[/N2/.../N6] - set domain to N1 and search list to
N1,N2,etc.
root=NAME - set root server to NAME
retry=X - set number of retries to X
timeout=X - set initial time-out interval to X seconds
querytype=X or type=x - set query type, e.g.,
A,ANY,CNAME,NS,PTR, etc.
class=X - set query class to one of IN(Internet),CHAOS,HESIOD or
ANY
server NAME - set default server to NAME, using current default
server
lserver NAME - set default server to NAME, using initial server
(MORE....press enter to continue)
finger [USER] - finger the optional NAME at the current default host
root - set current default server to the root
ls [option] DOMAIN [>|>> FILE] - list addresses in DOMAIN (output to
FILE)
-a - list canonical names and aliases
-h - list HINFO (CPU type and operating system)
-s - list well-known services
-d - list all records
-t TYPE - list records of the given type (e.g., A,CNAME,MX,
etc.)
view FILE - sort an 'ls' output file and view it with more
exit - exit the program
> exit
If you do NOT get these, can you please capture the screen that you DO
get and list it here... Something is quite wrong then...
> > Lastly, how many DEVICES do you have on this LAN and IF more than 1
> > PC, are ALL devices experiencing the same problem?
>
> Just this machine (Dell desktop).
Noted thanks, its not an issue.
> > Are you 100% sure the "sticky" DNS issue only appears with
> > www.google.com and no other site (such as www.ibm.com)?
>
> It's not just Google, but that's the one I stumble upon every time because
> of Gmail, Google News, and Google Reader. I know on the other hand that
> cdbaby.com and any musicians' sites hosted on hostbaby.com are fine right
> after reboot, and so is the BBC news site.
Ok ,that's a bit odd. Maybe your ISP is caching the name "google" for
some reason...
So far the only odd thing I can see is the MASK used for the NETWORK
Route (255.255.255.255). That means its effectively a HOST route not
a Network route, but I can't see how this might be affecting a single
network route at an endpoint like this. Without a comparison of a
non-working setup its hard to say more...
Cheers...............pk.
--
Peter from Auckland.
Paul Ratcliffe
> WAN Information:
> Primary DNS:
> 198.7.0.5
> Secondary DNS:
> 166.84.67.2
>
>> 4. Now list the CONTENTS of the text file x:\MPTN\ETC\RESOLVE2.
>
> nameserver 192.168.1.1
The router is doing the DNS. An obvious first step if you are having DNS
issues is to bypass it and use the real DNS servers listed above.
> Nothing else. This appears to be generated automatically, as it is
> re-created if it is erased.
Can you change the DNS settings that LAN clients see in the router?
If not, then it sounds like you'll have to use static IP addresses
rather than DHCP.
I would do this anyway as you then don't have any of this lease
renewal crap and all the other grief of DHCP.
>> Now run NSLOOKUP to see what your DNS info is saying
>
> I don't get a prompt: the cursor goes to the start of the next line and
> just sits there, and nothing I type does anything until I stop with ^C.
Well that says it all. The DNS support in the router is very broken by
the sound of it.
But, what does it do after an hour, when it is all supposedly working?
Pierre Jelenc
>
> Can you change the DNS settings that LAN clients see in the router?
> If not, then it sounds like you'll have to use static IP addresses
> rather than DHCP.
> I would do this anyway as you then don't have any of this lease
> renewal crap and all the other grief of DHCP.
How do I do that? I was told to use DHCP when setting up. I have nothing
against fixed IPs in the 192... block, since there's only this one PC now,
and at most there may be a laptop in the (distant) future.
> Well that says it all. The DNS support in the router is very broken by
> the sound of it.
> But, what does it do after an hour, when it is all supposedly working?
That *is* when it is supposedly working!
I am going to reboot in an hour or so and finish the tests then.
Pierre Jelenc
=====================================
domain
nameserver 192.168.1.1
=====================================
System Name:
Netopia 2247-02
F/W Version:
7.7.4r3
DSL F/W Version:
DSP 7.2.3.0, HAL 7.2.1.0
Standard:
DMT
IP Address:
166.84.167.2
Mask:
255.255.255.255
Primary DNS:
198.7.0.5
Secondary DNS:
166.84.67.2
Default Gateway:
166.84.64.2
0/35
NAT:
On
LAN Information:
MAC Address:
00:1f:c4:81:6c:a0
IP Address:
192.168.1.1
IP Mask:
255.255.255.0
IP Range:
192.168.1.1-192.168.1.254
DHCP:
Server
DHCP Start IP:
192.168.1.101
DHCP Pool Size:
154
DHCP Range:
192.168.1.101-192.168.1.254
[c:\]netstat -a
addr 127.0.0.1 Interface 9 mask 0xff000000 broadcast 127.0.0.1
Multicast addrs:
224.0.0.1
addr 192.168.1.102 Interface 0 mask 0xffffff00 broadcast 255.255.255.255
Multicast addrs:
224.0.0.1
=====================================
[c:\]netstat -r
destination router netmask metric flags intrf
default 192.168.1.1 0.0.0.0 0 UGP lan0
64.233.161.104 192.168.1.1 255.255.255.255 0 UGHW lan0
74.125.115.18 192.168.1.1 255.255.255.255 0 UGHW lan0
127.0.0.1 127.0.0.1 255.255.255.255 0 UH lo
140.211.166.81 192.168.1.1 255.255.255.255 0 UGHW lan0
166.84.143.27 192.168.1.1 255.255.255.255 0 UGHW3 lan0
192.168.1 192.168.1.102 255.255.255.0 0 UC lan0
198.7.0.5 192.168.1.1 255.255.255.255 0 UGHW3 lan0
=====================================
[c:\]ifconfig lan0
lan0: flags=8843<UP,BROADCAST,RUNNING,MULTICAST,LOOPBRD>
inet 192.168.1.102 netmask 0xffffff00 broadcast 255.255.255.255
c:\]ifconfig lo
o: flags=809<UP,LOOPBACK,MULTICAST>
inet 127.0.0.1 netmask 0xff000000
=====================================
> "nslookup hostname" starts nslookup using the DEFAULT DNS Server and
> automatically looks up the hostname using your DEFAULT DNS entries,
This is what I see:
http://www.pierrejelenc.com/nslookup1.gif
then after a while (at least a minute, maybe more) I get an error (I
hadn't seen that before, I probably had not waited log enough):
http://www.pierrejelenc.com/nslookup2.gif
> One thing we
> could try here is to disables DHCP on your eCS machine and set the IP
> values manually, AND bypass your Router DHCP data,
I'll try that next and will report later.
Paul Ratcliffe
>> I would do this anyway as you then don't have any of this lease
>> renewal crap and all the other grief of DHCP.
>
> How do I do that? I was told to use DHCP when setting up.
By what? Or whom? DHCP just seems to cause loads of problems on OS/2.
You want something like this (ignoring the REM lines) in \MPTN\BIN\SETUP.CMD
route -fh
arp -f
ifconfig lo 127.0.0.1
ifconfig lan0 192.168.1.2 netmask 255.255.255.0 metric 0 mtu 1500
route add default 192.168.1.1
ipgate off
and then change your \MPTN\ETC\RESOLV2 file to read:
nameserver 198.7.0.5
nameserver 166.84.6.2
>> But, what does it do after an hour, when it is all supposedly working?
>
> That *is* when it is supposedly working!
Ah, then it really is broken.
Peter
> OK, here are the results right after a reboot, with Gmail inaccessible.
... snip ...
This all looks the same.
> > "nslookup hostname" starts nslookup using the DEFAULT DNS Server and
> > automatically looks up the hostname using your DEFAULT DNS entries,
>
> This is what I see:
>
> http://www.pierrejelenc.com/nslookup1.gif
TIP: When you open the Window, issue the "Mode co80,44" command to get
more LINES (44) displayed. I would like to see the output from
NSLOOKUP at this time (its missing in this output). You can also
select all the text in the Window and copy/paste it to the message...
> then after a while (at least a minute, maybe more) I get an error (I
> hadn't seen that before, I probably had not waited log enough):
>
> http://www.pierrejelenc.com/nslookup2.gif
BINGO... this looks like it is the problem. The DNS Forwarder in the
Router is not starting up correctly... if the Router is not
restarting, but the PC is, then you may be able to work around the
problem.This could be caused by either a ROUTER issue or an ISP issue.
It would be useful to see what NSLOOKUP gives us when it IS working,
to see what works, so we can replicate that. The Routers DNS Forwarder
is not operating correctly at the PC connection start up or there is
something wrong here... Effectively, the Router it saying it cannot
find itself (192.168.1.1), which is wierd.
NOTE, your ISP's DHCP configuration is telling your machine to use the
Router DNS forwarder, so THATS the bit you need to fix to set up your
OWN permanent workaround. Its possble to tell your PC what parameters
to accept from the DHCP Server, but that takes a bit more to set up.
You can then insert your own DNS value to get things working properly.
I can see 2 solutions (work arounds) here...
1. Get a replacement Router that fixes the problem, OR..
2. When its working correctly, take note of the IP address of the
DNS the Router Forwarder is using. THEN... configure your machine to
go DIRECTLY to there by -
1. Manually updating your RESOLVE2 file to point to the Target DNS
and therefore bypass this function in the Router.
2. Automaticaly, by modifying your DHCP control file AND your TCP/IP
notebook settings.
Cheers..............pk.
--
Peter from Auckland.
Pierre Jelenc
>
> 1. Manually updating your RESOLVE2 file to point to the Target DNS
> and therefore bypass this function in the Router.
> 2. Automaticaly, by modifying your DHCP control file AND your TCP/IP
> notebook settings.
I edited the setup using TCP/IP Configuration as you described in a prior
post, and that seems to do the trick: everything appears to be accessible
right after reboot, and nslookup returns sensible IP addresses, including
for the google.com domains.
Paul Ratcliffe
> NOTE, your ISP's DHCP configuration is telling your machine to use the
> Router DNS forwarder
No it isn't. The ISP has no control over what the router tells its DHCP
clients. Where do you get this stuff?
> I can see 2 solutions (work arounds) here...
> 1. Get a replacement Router that fixes the problem, OR..
> 2. When its working correctly, take note of the IP address of the
The third solution is the easiest and the best - use a static IP address.
> 1. Manually updating your RESOLVE2 file to point to the Target DNS
It's "RESOLV2" and DHCP will just overwrite it again, so that's hardly
a solution.
> 2. Automaticaly, by modifying your DHCP control file AND your TCP/IP
> notebook settings.
Bloody 'ell, just use static settings. It is a lot less work.
Peter
> > NOTE, your ISP's DHCP configuration is telling your machine to use the
> > Router DNS forwarder
>
> No it isn't. The ISP has no control over what the router tells its DHCP
> clients. Where do you get this stuff?
That was meant to be the eCS DHCP configuration is telling...etc..
> > I can see 2 solutions (work arounds) here...
> > 1. Get a replacement Router that fixes the problem, OR..
> > 2. When its working correctly, take note of the IP address of the
>
> The third solution is the easiest and the best - use a static IP address.
That is not always the case. When a laptop moves between different
LANS and both LANS have DHCP, available then DHCP is by far the
easiest solution.
> > 1. Manually updating your RESOLVE2 file to point to the Target DNS
>
> It's "RESOLV2" and DHCP will just overwrite it again, so that's hardly
> a solution.
Thats why it was a MANUAL solution. IE a once off event.
> > 2. Automaticaly, by modifying your DHCP control file AND your TCP/IP
> > notebook settings.
>
> Bloody 'ell, just use static settings. It is a lot less work.
Not always true (as outlined above)...
Cheers.........pk.
--
Peter from Auckland.
Njupalo
Hi Peter,
> Start of your Testing...
> And now for the status of a few things WHEN ITS WORKING.
> The NETSTAT command only DISPLAY info, it changes nothing , but
> IFCONFIG WILL try to change things if you add extra parameters, so
Maybe there is an easiest way to see that info . Use IpConfigPM.exe
which will give you most of info you need.
You can find it on Hobbes.
> Now run NSLOOKUP to see what your DNS info is saying and enter
Hmmm, maybe I should add that part to IpConfigPM too?
--
Best Regards, Dusan