dsn will not resolve address when sing cell modem

Hi Anyone,
Heres the some history.
I have two connections to the internet. One being the normal LAN the other
being a DUN Cell modem.
Before joining or disjoining the domain both connections work and use the
correct DNS for the connection type. LAN uses LAN, Cell uses Cell.
Tested using ping and nslookup both answer correctly
I join the domain and the LAN continues to work the Cell stops working
unless it is also connected to the LAN.
Test results: With LAN disconnected and Cell modem connected nslookup is
still tring to use the LAN DNS servers to resolve DNS requests even though
the cell modem as the correct DNS entrys for the modems usage. The system
will still connect using the IP address of a site. It just will not resove
addresses.
Any Help
Jeff

Hello Jeff,

If you work in a domain, all computers have to use the domain internal DNS
server and no other ones, to avoid problems domain internal. To access internet
in this way you have to use the LAN default gateway. Additional you have
to setup a Forwarder to your ISP's DNS server on the server properties in
the DNS management console form the domain controller. Then also the domain
members will resolve names correctly. Also you can not specify 2 default
gateways for clients, that will result in a conflict.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hi Anyone,
> Heres the some history.
> I have two connections to the internet. One being the normal LAN the
> other
> being a DUN Cell modem.
> Before joining or disjoining the domain both connections work and use
> the
> correct DNS for the connection type. LAN uses LAN, Cell uses Cell.
> Tested using ping and nslookup both answer correctly
> I join the domain and the LAN continues to work the Cell stops working
> unless it is also connected to the LAN.
> Test results: With LAN disconnected and Cell modem connected nslookup
> is
> still tring to use the LAN DNS servers to resolve DNS requests even
> though
> the cell modem as the correct DNS entrys for the modems usage. The
> system
> will still connect using the IP address of a site. It just will not
> resove
> addresses.
> Any Help
> Jeff

"Jeff" <(E-Mail Removed)> wrote in message
news:F7C68B8A-6BB9-4AE0-B9D4-(E-Mail Removed)...
> Hi Anyone,
> Heres the some history.
> I have two connections to the internet. One being the normal LAN the other
> being a DUN Cell modem.
> Before joining or disjoining the domain both connections work and use the
> correct DNS for the connection type.

No they don't. You just got "lucky".

DNS settings are *global* for the whole machine regaurdless of the Nic's
TCP/IP Specs they are set in. A machine should have DNS entries on only one
Nic with the rest left blank (can't do that with cell dialup because of
forced DHCP). A machine should never have more than one DNS server listed
unless those DNS servers are "redundant" to each other like a pair of DCs
(again, can't do that with cell dialup because of forced DHCP)

The Cell Nic is a "dialup technology". When a dialup connection is made it
"takes over" everything. A machine is not intended to use any other Nic or
any other "TCP/IP Specs" while the dialup is active. The intent of a dialup
connection is to:
1. Dial up/connect
2. Use for the specific task at hand
3. Immediately disconnect
4. Do not stay connected
5. All other communication on other nics/connections is [loosely] suspended
while the dialup is active.

Any activity that works with other nics/connection while the dialup is
active is just "lucky".
What I mean by "loosely suspended" is this,..The TCP/IP stack will still
work for the other connections. Routing pathes that are specific to the
other nics/connections will still route (like static routes). But default
routing (default gateways) becomes confused because you now have two Default
Gateways,..the one you first had, and now the one on the Dialup connection
forced on you by the DHCP on the opposite end of the connection,..and the
dialup connection usually (is supposed to) over-ride the other. Sometimes a
dialup will even over ride static routes although I haven't experimented
with that a lot,..but using Split-Tunneling (disabling "use gateway on
remote network" on the dialup) might relieve that. DNS?,..well DNS just
becomes a "crap-shoot". Usually the machine will just take the first DNS
entriy it sees on the Nic that is the highest in the binding order priority.
It will never attempt to use any other DNS unless the first DNS it attempted
just flat out does not respond at all.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

I think I might not have been clear on the situation.
Before joining the domain (Computer Assigned to workgroup = Temp) The
Computer can use either the Wireless, Cell , or Network (Hardwired)
connections. The computer will use the DNS server that is supplied by any of
the connection.
Nslookup uses the dns supplied by the connection for it settings.

Upon Joining the Domain the computer will only use the settings from the
domain. Even if the computer is not connected to the network. Nslookup will
use the domains dns ip address to try to resolve all requests. Thus Failing
when you are not connected to the Domain. This is the case even if you look
at Ipconfig/all and see that the cell or wireless has correct dns settings
for that connection. Also if you type the ip address into ping or to the
address you can get to the site. But nslookup will fail.

If you change back to a workgroup from the domain. The system will go back
to operating as normal.
"Meinolf Weber" wrote:

> Hello Jeff,
>
> If you work in a domain, all computers have to use the domain internal DNS
> server and no other ones, to avoid problems domain internal. To access internet
> in this way you have to use the LAN default gateway. Additional you have
> to setup a Forwarder to your ISP's DNS server on the server properties in
> the DNS management console form the domain controller. Then also the domain
> members will resolve names correctly. Also you can not specify 2 default
> gateways for clients, that will result in a conflict.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > Hi Anyone,
> > Heres the some history.
> > I have two connections to the internet. One being the normal LAN the
> > other
> > being a DUN Cell modem.
> > Before joining or disjoining the domain both connections work and use
> > the
> > correct DNS for the connection type. LAN uses LAN, Cell uses Cell.
> > Tested using ping and nslookup both answer correctly
> > I join the domain and the LAN continues to work the Cell stops working
> > unless it is also connected to the LAN.
> > Test results: With LAN disconnected and Cell modem connected nslookup
> > is
> > still tring to use the LAN DNS servers to resolve DNS requests even
> > though
> > the cell modem as the correct DNS entrys for the modems usage. The
> > system
> > will still connect using the IP address of a site. It just will not
> > resove
> > addresses.
> > Any Help
> > Jeff
>
>
>

I think I might not have been clear on the situation.
Before joining the domain (Computer Assigned to workgroup = Temp) The
Computer can use either the Wireless, Cell , or Network (Hardwired)
connections. The computer will use the DNS server that is supplied by any of
the connection.
Nslookup uses the dns supplied by the connection for it settings.

Upon Joining the Domain the computer will only use the settings from the
domain. Even if the computer is not connected to the network. Nslookup will
use the domains dns ip address to try to resolve all requests. Thus Failing
when you are not connected to the Domain. This is the case even if you look
at Ipconfig/all and see that the cell or wireless has correct dns settings
for that connection. Also if you type the ip address into ping or to the
address you can get to the site. But nslookup will fail.

If you change back to a workgroup from the domain. The system will go back
to operating as normal.
"Phillip Windell" wrote:

> "Jeff" <(E-Mail Removed)> wrote in message
> news:F7C68B8A-6BB9-4AE0-B9D4-(E-Mail Removed)...
> > Hi Anyone,
> > Heres the some history.
> > I have two connections to the internet. One being the normal LAN the other
> > being a DUN Cell modem.
> > Before joining or disjoining the domain both connections work and use the
> > correct DNS for the connection type.
>
> No they don't. You just got "lucky".
>
> DNS settings are *global* for the whole machine regaurdless of the Nic's
> TCP/IP Specs they are set in. A machine should have DNS entries on only one
> Nic with the rest left blank (can't do that with cell dialup because of
> forced DHCP). A machine should never have more than one DNS server listed
> unless those DNS servers are "redundant" to each other like a pair of DCs
> (again, can't do that with cell dialup because of forced DHCP)
>
> The Cell Nic is a "dialup technology". When a dialup connection is made it
> "takes over" everything. A machine is not intended to use any other Nic or
> any other "TCP/IP Specs" while the dialup is active. The intent of a dialup
> connection is to:
> 1. Dial up/connect
> 2. Use for the specific task at hand
> 3. Immediately disconnect
> 4. Do not stay connected
> 5. All other communication on other nics/connections is [loosely] suspended
> while the dialup is active.
>
> Any activity that works with other nics/connection while the dialup is
> active is just "lucky".
> What I mean by "loosely suspended" is this,..The TCP/IP stack will still
> work for the other connections. Routing pathes that are specific to the
> other nics/connections will still route (like static routes). But default
> routing (default gateways) becomes confused because you now have two Default
> Gateways,..the one you first had, and now the one on the Dialup connection
> forced on you by the DHCP on the opposite end of the connection,..and the
> dialup connection usually (is supposed to) over-ride the other. Sometimes a
> dialup will even over ride static routes although I haven't experimented
> with that a lot,..but using Split-Tunneling (disabling "use gateway on
> remote network" on the dialup) might relieve that. DNS?,..well DNS just
> becomes a "crap-shoot". Usually the machine will just take the first DNS
> entriy it sees on the Nic that is the highest in the binding order priority.
> It will never attempt to use any other DNS unless the first DNS it attempted
> just flat out does not respond at all.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>

"Jeff" <(E-Mail Removed)> wrote in message
news:FF828A12-E15B-458A-9A36-(E-Mail Removed)...
>
> I think I might not have been clear on the situation.
> Before joining the domain (Computer Assigned to workgroup = Temp) The
> Computer can use either the Wireless, Cell , or Network (Hardwired)
> connections.

It doesn't matter. Workgroups don't depend on DNS to function so you just
do "see" the problem the same way,...that doesn't mean the problem isn't
there. Domains and Workgroups are "administration entities",..but I am
talking about network infrastructure,...two entirely different things.

> The computer will use the DNS server that is supplied by any of
> the connection.
> Nslookup uses the dns supplied by the connection for it settings.
............
> when you are not connected to the Domain. This is the case even if you
> look
> at Ipconfig/all and see that the cell or wireless has correct dns settings
> for that connection. Also if you type the ip address into ping or to the

IPConfig is mostly irrelevant here. IPConfig only shows you the config of
the Nics,...it does not show you nor signify *how* the OS makes use of those
settings nor how it makes its logical choices when things conflict (like two
conflicting DNS settings on two nics). When a machine has two nics you have
two choices for DNS,...1. Make the DNS Setting the same on both,...or 2.
Leave the DNS blank on one of them. By the nature of what you have you
cannot do either of those two

The bottom line is that you cannot have a machine on a LAN with an Ethernet
nic (wired or wireless) and at the same time enable and run a DHCP enabled
Cell Dialup card (and leave it up) and expect things to dependably work the
way they are supposed to. It just ain't gonna happen. The Cell Dialup Nic
is for running *only* when the machine is not connected to anything
else,...or it can be used *breifly* while on the LAN as long as a possible
LAN disruption with that one machine during the short period isn't a problem
and can be lived with.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

That is just it...
Ok. you are a member of the domain and hardwired into the network
domain...you use the networks DNS to resolve addresses.
nslookup www.google.com
server:xxx.xxx.xxx
Address: 192.168.10.111

Non-authoritative answer:
name: www.l.google.com
Addresses: 74.125.47.147 .......
Aliases: www.google.com

Now. you unplug from the wired network. and connect using either the cable
modem (Wireless) or cell modem to the raw internet.

All info about the wired network should be gone???...so

nslookup www.google.com
dns request timed out
timeout was 2 seconds
*** can't find server name for address 192.168.10.111: timed out
dns request timed out
timeout was 2 seconds
*** can't find server name for address 192.168.10.112: timed out
*** default servers are not available
Server: unknown
Address : 192.168.10.111

dns request timed out
timeout was 2 seconds

So it is like it is still trying to use the domains dns even though it is
not connected to the domain. This is where it should be using the dns from
the wireless connection or the cell modem but it is not.



"Phillip Windell" wrote:

> "Jeff" <(E-Mail Removed)> wrote in message
> news:FF828A12-E15B-458A-9A36-(E-Mail Removed)...
> >
> > I think I might not have been clear on the situation.
> > Before joining the domain (Computer Assigned to workgroup = Temp) The
> > Computer can use either the Wireless, Cell , or Network (Hardwired)
> > connections.
>
> It doesn't matter. Workgroups don't depend on DNS to function so you just
> do "see" the problem the same way,...that doesn't mean the problem isn't
> there. Domains and Workgroups are "administration entities",..but I am
> talking about network infrastructure,...two entirely different things.
>
> > The computer will use the DNS server that is supplied by any of
> > the connection.
> > Nslookup uses the dns supplied by the connection for it settings.
> ............
> > when you are not connected to the Domain. This is the case even if you
> > look
> > at Ipconfig/all and see that the cell or wireless has correct dns settings
> > for that connection. Also if you type the ip address into ping or to the
>
> IPConfig is mostly irrelevant here. IPConfig only shows you the config of
> the Nics,...it does not show you nor signify *how* the OS makes use of those
> settings nor how it makes its logical choices when things conflict (like two
> conflicting DNS settings on two nics). When a machine has two nics you have
> two choices for DNS,...1. Make the DNS Setting the same on both,...or 2.
> Leave the DNS blank on one of them. By the nature of what you have you
> cannot do either of those two
>
> The bottom line is that you cannot have a machine on a LAN with an Ethernet
> nic (wired or wireless) and at the same time enable and run a DHCP enabled
> Cell Dialup card (and leave it up) and expect things to dependably work the
> way they are supposed to. It just ain't gonna happen. The Cell Dialup Nic
> is for running *only* when the machine is not connected to anything
> else,...or it can be used *breifly* while on the LAN as long as a possible
> LAN disruption with that one machine during the short period isn't a problem
> and can be lived with.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>

"Jeff" <(E-Mail Removed)> wrote in message
news:054BF060-F603-4E06-8B3C-(E-Mail Removed)...
> Now. you unplug from the wired network. and connect using either the cable
> modem (Wireless) or cell modem to the raw internet.
>
> All info about the wired network should be gone???...so
<shortened to save space>
> So it is like it is still trying to use the domains dns even though it is
> not connected to the domain. This is where it should be using the dns from
> the wireless connection or the cell modem but it is not.

Ok, I didn't know it was having issues when running standalone, off the LAN,
with only the Cell Modem running. I thought you were having problems running
both at the same time.

Now,..with the Cell modem being the only thing it is using,...the LAN nic is
unpluged....

What does "IPConfig/All" show again? I mean all DNS anywhere in the
output,...I don't care what nic. Maybe you could paste the output into the
reply.

What does it do after you do "IPConfig /flushdns"?


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------