Archived from groups: microsoft.public.win2000.active_directory (
More info?)
Ace...
I see where having the domain name in AD just entered as briess would be a
problem...
When I specified internal.briess.com in dhcp to force clients to use that
dns suffix, I replaced briess so that should be ok now.
I have included ipconfig /all from 2 DCs on our network.... looks alright
from what I can tell... neither of them see just briess as a dns suffix.
IPconfig 1:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : solomon2k
Primary DNS Suffix . . . . . . . : internal.briess.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : internal.briess.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100+ Server Adapter
(PILA8470B)
Physical Address. . . . . . . . . : 00-30-48-22-AD-84
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.1
IPconfig 2:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : w-server2k
Primary DNS Suffix . . . . . . . : internal.briess.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : internal.briess.com
briess.com
Ethernet adapter Intel Pro 1000 MT Gigabit Ethernet Adapter - Onboard:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-0C-F1-D1-73-BF
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . . . . : 192.168.1.1
Ethernet adapter Intel Fast Ethernet LAN Controller - PCI Slot 4:
Media State . . . . . . . . . . . : Cable Disconnected
Description . . . . . . . . . . . : Intel(R) PRO/100 S Server Adapter
Physical Address. . . . . . . . . : 00-02-B3-EF-95-23
Also, all the clients are listed in the DNS zone internal.briess.com, some
web apps like www.briess.com and mail and things live in the zone
briess.com...
internal.briess.com zone list:
Name Type Data
wmcchart Host 192.168.0.51
web2k Host 192.168.1.3
w-server2k Host 192.168.0.200
W-MSILLMAN2K Host 192.168.0.197
w-gburmeisterxp Host 192.168.0.39
w-gburmeister Host 192.168.0.58
W-FPETRAN2K Host 192.168.0.14
W-CSTROBEL2K Host 192.168.0.150
W-CBEYER2K Host 192.168.1.64
w-beyerc2k Host 192.168.0.180
vstenklyftxp Host 192.168.1.52
VSTENKLYFT2K Host 192.168.1.124
vista1 Host 192.168.254.128
vendor2k Host 192.168.1.144
traffic2k Host 192.168.1.76
tmeyer2k Host 192.168.1.66
thickey2k Host 192.168.1.70
test2k Host 192.168.1.68
test Host 192.168.1.85
SQL2K Host 192.168.1.11
solomon60test Host 192.168.1.66
solomon2k Host 192.168.1.1
SMUELLENBACH2K Host 192.168.1.93
shipping01 Host 192.168.1.115
ryoung2k Host 192.168.1.128
rndmanager Host 192.168.1.74
RECEPTION2K Host 192.168.1.65
reception01 Host 192.168.1.66
qualityoffice Host 192.168.1.62
purchasing01 Host 192.168.1.94
project Host 192.168.1.108
president Host 192.168.1.99
PPICKART2K Host 192.168.1.67
portalserver Host 192.168.1.51
MPIEPENBURG2K Host 192.168.1.248
MMCINTIRE2K Host 192.168.1.148
mlauty2k Host 192.168.1.150
mgruber2k Host 192.168.1.114
MFORSTNER2K Host 192.168.1.116
Marketing02 Host 192.168.1.82
marketing01 Host 192.168.1.107
Maintenance02 Host 192.168.1.88
maintenance01 Host 192.168.1.81
LMANZ2K Host 192.168.1.101
LFRANZ2K Host 192.168.1.74
lboetchoer2k Host 192.168.1.153
laptop Host 192.168.2.102
labeler2k1 Host 192.168.1.117
labeler2k Host 192.168.1.122
lab3 Host 192.168.1.68
lab2 Host 192.168.1.121
lab1 Host 192.168.1.79
KVOGEL2K Host 192.168.1.105
kvhieewp Host 192.168.1.108
kschroeder2k2 Host 192.168.1.146
kschroeder2k04 Host 192.168.1.138
KSCHROEDER2K Host 192.168.1.131
kkunzxp Host 192.168.1.77
KKLASEN2K Host 192.168.1.113
kdedering2k Host 192.168.1.95
KBOLL2K Host 192.168.1.104
jmeuer2k Host 192.168.1.157
jkrueger2k Host 192.168.1.158
jgokingxp Host 192.168.1.84
it Host 192.168.1.5
invoicing01 Host 192.168.1.133
greuels2K03 Host 192.168.1.56
foodsales Host 192.168.1.89
finance Host 192.168.1.125
FILES2K Host 192.168.1.8
extractsuper02 Host 192.168.1.123
extractsuper01 Host 192.168.1.116
extractmanager Host 192.168.1.104
exchange2k Host 192.168.1.7
dschaulandxp Host 192.168.1.69
dkuske2k Host 192.168.1.118
DistCenter Host 192.168.1.102
dboettcher2k2 Host 192.168.1.119
DBOETTCHER2K Host 192.168.1.132
custservice3 Host 192.168.1.97
CustService2 Host 192.168.1.96
custservice1 Host 192.168.1.92
credit01 Host 192.168.1.64
CMCWarehouse Host 192.168.1.75
CMCLAB2K Host 192.168.0.22
cmc_maintenance Host 192.168.1.114
CKREBSBACH2K-03 Host 192.168.1.71
CKREBSBACH2K Host 192.168.1.53
CKLEINHANS2K Host 192.168.1.123
citrix2k Host 192.168.1.63
CFIELD2K Host 192.168.1.111
CELERON2K Host 192.168.1.61
CARTMAN Host 192.168.1.90
BWASDOVITCH2K Host 192.168.1.58
BTASCH2K Host 192.168.1.46
brushlaptop Host 192.168.1.94
BRUSH2K Host 192.168.1.62
briess-7916803x Host 192.168.1.244
BPARR2K3 Host 192.168.1.57
bhansen2k Host 192.168.1.85
BDOETTCHER2K Host 192.168.1.132
ashiplett2k Host 192.168.1.98
area151 Host 192.168.1.130
area151 Host 192.168.1.51
archive95 Host 192.168.1.107
ACASPER2K Host 192.168.1.109
_udp
_tcp
_sites
_msdcs
(same as parent folder) Start of Authority [2134],
solomon2k.internal.briess.com., admin.
(same as parent folder) Name Server solomon2k.internal.briess.com.
(same as parent folder) Host 192.168.1.10
(same as parent folder) Host 192.168.1.7
(same as parent folder) Host 192.168.1.3
(same as parent folder) Host 192.168.1.1
(same as parent folder) Host 192.168.0.200
(same as parent folder) Host 192.168.0.2
(same as parent folder) Host 169.254.148.31
I think it is beginning to make sense a little more now. I walked into this
environment and it was limping along well enough to leave it alone until
recently...
Thanks again for all your help...
Derek
"Ace Fekay [MVP]" wrote:
> In news:51DD5A67-32C0-4005-BDBE-44E57AAB1802@microsoft.com,
> Derek Schauland <DerekSchauland@discussions.microsoft.com> made this post,
> which I then commented about below:
> > Hello Ace,
> >
> > I do remember using a single name rather than the FQDN when adding
> > this box to the domain.
> >
> > the IP info is below, sorry for not providing it sooner...
> >
> > Windows IP Configuration
> > Host Name . . . . . . . . . . . . : invoicing01
> > Primary Dns Suffix . . . . . . . : internal.briess.com
> > Node Type . . . . . . . . . . . . : Hybrid
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : internal.briess.com
> > BRIESS
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . : BRIESS
> > Description . . . . . . . . . . . : Broadcom NetXtreme 57xx
> > Gigabit Controller
> >
> > Physical Address. . . . . . . . . : 00-12-3F-2E-4A-70
> > Dhcp Enabled. . . . . . . . . . . : Yes
> > Autoconfiguration Enabled . . . . : Yes
> > IP Address. . . . . . . . . . . . : 192.168.1.133
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.1.254
> > DHCP Server . . . . . . . . . . . : 192.168.1.1
> > DNS Servers . . . . . . . . . . . : 192.168.1.1
> > Primary WINS Server . . . . . . . : 192.168.1.1
> > Lease Obtained. . . . . . . . . . : Monday, September 12, 2005
> > 7:50:52 AM
> >
> > Lease Expires . . . . . . . . . . : Thursday, October 27, 2005
> > 7:50:52 AM
> >
> > I am guessing that removing the PC and adding it back to the domain
> > using internal.briess.com as the domain name would correct this?
> >
> > Derek
>
> What is AD's DNS domain name? Is it "Breiss" or "breiss.com"?
>
> The Search Suffix on this machine (assuming it's the client), is set to:
> > DNS Suffix Search List. . . . . . : internal.briess.com
> > BRIESS
>
> So when you attempt to connect to \\servername, the resolver service will
> first look for (in the order shown above), "servername.briess.com", and if
> not found under that zone, will then look for "servername.breiss". Then if
> neither is found, it wll attempt to ask WINS. So do you see how the Search
> Suffix dictates resolution? If either the record doesn't exist under either
> zone, or the zone doesn't exist, and it doesn't exist in WINS, then it
> returns "not found".
>
> When resolving for \\domain, it will treat it as a NetBIOS name. So when it
> tries to resolve \\domain\dfsrootname,it thinks \\domain is a host name and
> not a domain. \\domain.com is the proper format.
>
> I'm confused because the Primary DNS Suffix is:
> > Primary Dns Suffix . . . . . . . : internal.briess.com
>
> Yet the Search Suffix list is:
> > DNS Suffix Search List. . . . . . : internal.briess.com
> > BRIESS
>
> Normally with using a subdomain as the Primary DNS Suffis, the Search Suffix
> will be set to:
> > DNS Suffix Search List. . . . . . : internal.briess.com
> > breiss.com
>
> So, in light of this, can you tell me what zones exist in DNS? Can you also
> post an ipconfig /all of your DC please? Honestly, I hope your AD DNS domain
> name is not just "BREISS".
>
> Oh, one more thing, I forgot to respond to a point you made in your previous
> post:
> > Also when trying to browse the network in net
> > neighborhood, Active Directory doesnt appear
> > in Entire Network.. it just shows Windows
> > Network.
>
> The above is normal on XP since that functionality was removed for security
> reasons. Entire Network should only show Windows Network, unless you also
> have NW client installed, which then it would show you Netware Network too.
>
> Thanks
> Ace
>
>
>
>