Re: Non-domain connection problem
- From: "Gregg Hill" <bogus@xxxxxxxxxxx>
- Date: Fri, 17 Feb 2006 18:10:53 -0800
Liam,
The only weird thing is why anyone in his/her right mind would set up such a
GPO in the first place!
Gregg Hill
"Liam" <Liam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F486770C-5878-4371-AD99-D87C3FECDC2D@xxxxxxxxxxxxxxxx
Indeed, the HARD CODED DNS was over written by theh local policy whether
you
were connected to the domain or not. All it took was one connection as a
member to be persistent....weird...
Liam
"Gregg Hill" wrote:
Liam,
I thought you were talking about home users behind home routers, not SBS
at
home. Not that it matters, since it should still work no matter where the
system is located.
You said that you "hard coded the DNS server to a known DNS on the
internet:
24.207.7.6," but the ipconfig output you posted does not show that DNS
server. Why not?
Gregg Hill
"Liam" <Liam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A111355D-D341-486D-99CC-E6A287DD3BC7@xxxxxxxxxxxxxxxx
Hi Gregg,
This output is from the HOME LAN. I use SBS2003 Premium edition.
The subnet at work is 192.168.10.13 with a gateway of 192.168.10.15
All addressing typically comes form the dom,ain controller.
Yesterday I even hardcoded the DNS of a local ISP into the TCP/ip
properties
to confirm that the Nameserver is not changing from the work DNS.
So today I have re-installed XPPro onto a new machine.
I am going to do the following:
**Before becoming a Client in the domain:
Connect to Internet from external network
Connect to Internet from Internal Network
**After becoming a client on the Domain
Connect to Internet from external network
Connect to Internet from Internal Network
If I can still connect then I will install VPN sftware to see if that
is
the
culprit.
"Gregg Hill" wrote:
Liam,
This output looks as though it is from a system connected to the work
LAN.
Notice that the default gateway and DNS IP addresses are different, as
well
as the fact that there is a WINS server listed.
What is the ipconfig from the system when it is on a home router? A
typical
home system would have 192.168.0.1 or 192.168.1.1 as the default
gateway
and
the DNS server, with no WINS listed.
Gregg Hill
"Liam" <Liam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8D9456C0-7981-4894-9E90-0098C9A565AD@xxxxxxxxxxxxxxxx
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\lhawthorne>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : it-test-pc
Primary Dns Suffix . . . . . . . : megastream.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : megastream.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : hoth.local
Description . . . . . . . . . . . : via Rhine III Fast
ethernet
adapter
Physical Address. . . . . . . . . : o3-E0-18-F1-94-98
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.185
DNS Servers . . . . . . . . . . . : 192.168.2.185
Primary WINS Server . . . . . . . : 192.168.2.185
Lease Obtained. . . . . . . . . . : February 14, 2006
12:31:39
PM
Lease Expires . . . . . . . . . . : February 22, 2006
12:31:39
PM
I hard coded the DNS server to a known DNS on the internet:
24.207.7.6
Again this had no effect on the ability to connect to the internet.
Thnkas for your help,
Liam
"Gregg Hill" wrote:
Liam,
After you do the following off the domain and on home router
ipconfig /release SUCCESS!
ipconfig /flushdns SUCCESS!
ipconfig /renew SUCCESS!
please post the output from
ipconfig /all
Gregg Hill
"Liam" <Liam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FFB0421E-77AF-410B-91C9-3AE47E9A9306@xxxxxxxxxxxxxxxx
Hi Gregg,
Thanks for the help.
DHCP is "pure". At home it is from the routers at work ir is from
the
SBS
box.
There are few fixed IP's (3 servers, 2 routers).
IPconfig /release /renew /flush dbs seem to have no effect on the
connectivity.
NSLOOKUP always looks for the SBS as the default gateway.
The wonder of all of this is that it worked without error for 8
moths.
When
I put the server 2003 box on the network seems to have caused
these
problems.
I ran gpedit and all the gpo's are "not configured" which is as
it
should
be.
I currently have a laptop here that is off the domain.
ipconfig /release SUCCESS!
ipconfig /flushdns SUCCESS!
ipconfig /renew SUCCESS!
Connect to Internet...fail!
The client software is Symantec VPN (same as our router/gateway)
There
are
no settings for "allow remote gateway".
But , again...this worked fine for at least 8 months until the
Server
2003
was placed on the network.
?
"Gregg Hill" wrote:
Liam,
Are you using pure DHCP both at work and home (NO fixed address
anywhere)?
Make sure you have no fixed IP addresses for DNS servers. You
**should**
be
able to use a batch file with "ipconfig /release && ipconfig
/renew"
in
it
to make it easy for the end users to release/renew the address.
As long as no fixed settings are there, and as long as the
user's
home
router is configured properly, it should get the correct
addressing.
What is the result of taking the laptop off the network, then
running
"ipconfig /release" followed by an "ipconfig /all" command?
Please
post
your
results here.
Do you have any GPOs forcing IP settings?
Gregg Hill
"Liam" <Liam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:62108E7B-8810-4660-8D3A-22A0ABDCB622@xxxxxxxxxxxxxxxx
Crina Li,
Thank you so much for replying and attempting to help me solve
my
challenge.
I have done everything you have asked and still remote clients
cannot
find
a
dns server other than the Primary Domain Controller on the
domain.
I am sure that I need to find a way to "change the default
gateway
on
the
remote PC"
Since the default gateway is ALWAYS the domain controller of
the
SBS
domain!
From home this is a real problem.
""Crina Li"" wrote:
Hi Liam,
Thank you for posting in SBS newsgroup.
From the description, I understand the issue to be: you want
to
let
the
laptop can surf internet from home without going through SBS.
If
I
have
misunderstood your concerns, please do not hesitate to let me
know.
As I know, when a laptop which is set to obtain an IP address
automatically
connects to your network, it should contact the SBS server
for
an
IP
address (including DNS and other settings) and then it can
browse
the
internal network and Internet web sites. When the laptop
disconnects
from
the network cable, all IP configuration should be deleted by
the
system
automatically.
Currently, we can check the following configuration on
laptop:
1. IE setting:
1) Open IE and then Click Internet Options on Tools menu.
2) Click Connections and then click LAN settings.
3) Check if you have selected Automatically detect settings.
4) Please do not use Proxy server to see how thing goes.
2. IP address and DNS settings:
1) Right click My Network Places and select Properties.
2) Open the properties of the Network Connection you are
using
to
connect
to internet on home.
3) Select TCP/IP and then click Properties.
4) Have you specified the SBS as the DNS server?
5) Make sure you have selected Obtain an IP address
automatically
and
Obtain DNS server address automatically if you are obtaining
the
IP
and
DNS
from ISP automatically when you surf internet at home.
6) Click Advanced and then check if you have configured SBS
on
it.
If you do want release an IP address, you can use the
following
command:
ipconfig /release
ipconfig /renew
Hope it helps and I look forward to hearing from you.
Best regards,
Crina Li (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
.
- Follow-Ups:
- Re: Non-domain connection problem
- From: Liam
- Re: Non-domain connection problem
- References:
- Non-domain connection problem
- From: Liam
- RE: Non-domain connection problem
- From: "Crina Li"
- RE: Non-domain connection problem
- From: Liam
- Re: Non-domain connection problem
- From: Gregg Hill
- Re: Non-domain connection problem
- From: Liam
- Re: Non-domain connection problem
- From: Gregg Hill
- Re: Non-domain connection problem
- From: Liam
- Re: Non-domain connection problem
- From: Gregg Hill
- Re: Non-domain connection problem
- From: Liam
- Re: Non-domain connection problem
- From: Gregg Hill
- Re: Non-domain connection problem
- From: Liam
- Non-domain connection problem
- Prev by Date: FTP Server Problem
- Next by Date: Re: Non-domain connection problem
- Previous by thread: Re: Non-domain connection problem
- Next by thread: Re: Non-domain connection problem
- Index(es):
Relevant Pages
|