Re: Client Machine cannot see Active Directory
- From: Derek Schauland <DerekSchauland@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 14 Sep 2005 18:31:02 -0700
We have multiple subnets 192.168.1.0, 192.168.0.0, and 192.168.3.0
3.0 uses a netgear wireless router to allow wireless access for some devices
1.0 is the subnet for the majority of our users and servers
0.0 is the subnet for our remote location. This subnet is connected by a
hardware vpn between a Cisco Pix 515 and a Cisco Pix 501. The pix 515 has 3
interfaces the 501 has 2
I will make sure to disable the non-used NICs and remove the 169.254.148.31
entry.
I have some web applications being sent out to the internet using NAT on the
Pix 515 other than that just the VPN from the remote site is coming in
between subnets.
Derek
"Ace Fekay [MVP]" wrote:
> In news:B2F82E60-948F-4605-8089-6AE23B6B6422@xxxxxxxxxxxxx,
> Derek Schauland <DerekSchauland@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post,
> which I then commented about below:
>
> Derek, I see some interesting issues. Please read my comments inline
> below...
>
>
> > 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.
>
> Good.
>
> >
> > 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.
>
> Good.
>
> > =================================
> > 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
>
> This should also show briess.com as the second search suffix. Did you remove
> that? That is actually default and will suggest to keep it, especially if
> you have a briess.com zone with records in it.
>
> >
> > 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
>
>
> Derek, there is no WINS address configured for this machine in it's ipconfig
> /all above. If I suspect as such that you have multiple subnets, unless the
> IP configuration below is incorrect, then WINS will be required for cross
> subnet NetBIOS name resolution.
>
>
> > =================================
> >
> >
> > 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
>
>
> Derek, do you have multiple subnets in your organization or is that a typo
> in the ipconfig /all?
>
>
> >
> > Ethernet adapter Intel Fast Ethernet LAN Controller - PCI Slot 4:
> >
> > Media State . . . . . . . . . . . : Cable Disconnected
>
>
> Derek, disable the above NIC in the BIOS please, or disable it in Windows.
>
>
>
> > 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
>
> Go into DNS and remove the 169.254.148.31 entry. That is coming from the NIC
> that is not connected. You will need to either disable the NIC in the BIOS
> or in Windows, or physically remove it.
>
>
> >
> > 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
>
>
> See if that helps.
>
> Also, are you routing between the 192.168.0.0 network and the 192.168.1.0
> network on a NAT device? If so, that can be blocking domain communication
> (specifically LDAP, RPC and Kerberos), due to H.323 support. What type of
> device is your router that is connecting the two subnets? Is it a Windows
> machine or a 3rd party device? If either one, does it have 3 interfaces on
> it?
>
> Ace
>
>
>
.
- Follow-Ups:
- Re: Client Machine cannot see Active Directory
- From: Ace Fekay [MVP]
- Re: Client Machine cannot see Active Directory
- References:
- Client Machine cannot see Active Directory
- From: Derek Schauland
- Re: Client Machine cannot see Active Directory
- From: Ace Fekay [MVP]
- Re: Client Machine cannot see Active Directory
- From: Derek Schauland
- Re: Client Machine cannot see Active Directory
- From: Ace Fekay [MVP]
- Re: Client Machine cannot see Active Directory
- From: Derek Schauland
- Re: Client Machine cannot see Active Directory
- From: Ace Fekay [MVP]
- Re: Client Machine cannot see Active Directory
- From: Derek Schauland
- Re: Client Machine cannot see Active Directory
- From: Ace Fekay [MVP]
- Client Machine cannot see Active Directory
- Prev by Date: AdminSDHolder thread - How can I block??
- Next by Date: Re: AdminSDHolder thread - How can I block??
- Previous by thread: Re: Client Machine cannot see Active Directory
- Next by thread: Re: Client Machine cannot see Active Directory
- Index(es):
Relevant Pages
|