Vista clients became unresponsive after network move
Deniz
I have been having this weird issue that I cannot isolate and I was
hoping someone can guess what's going on.
We recently moved our offices to a new location. Half of the computers
(Vista & XP clients) moved on day one, and worked without the domain
controller (2003) for a day. On the next day, the rest of the clients
and the domain controller have been moved to the new location. The
computers detected a new network, so not everything worked out of the
box after the move: some firewall and sharing settings were reset
since they have a new network connection. There were no hardware or
software changes on the computers (auto-updates were turned off) The
only difference between the old office network and the new one are the
cabling in the walls, and the Ethernet switch (old one: Siemens +
Netgear, new one: Cisco SR224)
Since the move, Vista clients seems to be acting strange in the
mornings when they were left on overnight:
- User cannot open any new programs or task manager. Currently open
programs run OK
- CTRL+ALT+DEL brings a black screen, and then shows this error:
"Logon Process has failed to create the security options dialog. "
with a dialog box "Failure - Security Options"
- Command prompt can be opened. Some commands work (ipconfig,
shutdown) some don't (ipconfig /all)
- I can ping the unresponsive Vista client on the LAN, and I can
remotely shutdown/restart it although it waits at that black screen
for few minutes before it starts to shutdown
- Event logs do not show any specific error before the clients become
unresponsive
Since I did not change any software/hardware on the machines, I have
reason to believe that this is a network issue. I searched online for
the error message I wrote above, but none of them helped so far (and
only few of them were related to network).
Has anybody had similar issues, or can anybody guess what the issue
could be?
Our current network:
----T1-router-----Linksys-with-DD-WRT------Cisco-SR224-switch-------DC-
and-clients--
Thank you,
Deniz
![Meinolf Weber [MVP-DS]'s profile photo](https://lh3.googleusercontent.com/a/default-user=s40-c)
Meinolf Weber [MVP-DS]
Hello Deniz,
Have you also changed the ip addressing? Did you make sure all machines use
the correct addresses and subnet masks? Can you post an unedited ipconfig
/all from the DC/DNS and a problem machine?
Are all machines correct registered in the DNS zones?
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
Deniz
wrote:
> Hello Deniz,
>
> Have you also changed the ip addressing? Did you make sure all machines use
> the correct addresses and subnet masks? Can you post an unedited ipconfig
> /all from the DC/DNS and a problem machine?
>
> Are all machines correct registered in the DNS zones?
>
> 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
Hi Meinolf,
Only our public IP (WAN IP on the router) has changed. All other IPs
are static assigned IPs in 192.168.x.x range.
One DNS issue that was pointed out in another discussion was about the
security settings on the host records. For example, host record for
COMPUTER-A did not have full control permissions for the user COMPUTER-
A$. Granting full control to the record owner did not solve this
problem, however.
Here is the technical data you requested, I hope it's helpful:
DC> ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : global
Primary Dns Suffix . . . . . . . : Global.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Global.local
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
Adapter(LNE100TX v4)
Physical Address. . . . . . . . . : 00-12-17-51-56-44
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.100
Vista Business 1> ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : MOSCOW
Primary Dns Suffix . . . . . . . : Global.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Global.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network
Connection
Physical Address. . . . . . . . . : 00-22-68-04-48-EB
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6806:4594:ed33:a0c6%11
(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.124(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.100
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR5007EG Wireless
Network Adapter
Physical Address. . . . . . . . . : 00-23-4D-97-FA-28
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{69493646-
EEA0-47F4-8D03-6FB084D382D0}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 7:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{0ED3926F-DCC3-4875-
B522-0F8FA7753E0B}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
I can see the Host (A) record in DNS for the computer MOSCOW, and it
points to 192.168.1.124 as also described in the IPconfig above.
Meinolf Weber [MVP-DS]
The ipconfig output look fine on both machines. What you can try on the Vista
machine is to uncheck IPv6 on the NIC, to see if this helps.
Any errors in the event viewer? Strange that it comes only over night, after
a reboot then everything is ok again?
Best regards
>>> DC - and-clients--
>>>
>>> Thank you,
>>>
>>> Deniz
>>>
> Hi Meinolf,
>
> Only our public IP (WAN IP on the router) has changed. All other IPs
> are static assigned IPs in 192.168.x.x range.
>
> One DNS issue that was pointed out in another discussion was about the
> security settings on the host records. For example, host record for
> COMPUTER-A did not have full control permissions for the user
> COMPUTER- A$. Granting full control to the record owner did not solve
> this problem, however.
>
> Here is the technical data you requested, I hope it's helpful:
>
DC>> ipconfig /all
DC>>
Deniz
wrote:
> Hello Deniz,
>
> The ipconfig output look fine on both machines. What you can try on the Vista
> machine is to uncheck IPv6 on the NIC, to see if this helps.
>
> Any errors in the event viewer? Strange that it comes only over night, after
> a reboot then everything is ok again?
>
> 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
In the event viewer first I saw errors like "GroupPolicy" or "DNSApi"
which suggested network connection problems. After fiddling around a
little bit those errors are not showing anymore. But the problem
remains. Another event that is always logged is Tcpip warning 4227,
which seems to happen little more often since we moved.
Computers appear to be running fine, until I do the Task Manager test,
or ipconfig /all test, none of which respond if the computer is having
the problem I described. If so, I immediately restart from the command
line. Then it runs fine throughout the day. Some computers even run
couple of days before they hit by this issue.
I will disable the IPv6 today to see if that helps. I will post an
update tomorrow.
Meinolf Weber [MVP-DS]
If DNSApi was event id 11166, this can belong to a DNS record update problem.
Check the security permisssions on the forward/reverse lookup zone entry
of the machine, if an unknown SID is used add the computername to the list
and give it the same permissions as the unknown account, then remove the
unknown one.
Group policy is to global , the complete error would be better to see what's
going on.
Best regards
>>>>> -- DC - and-clients--
Deniz
wrote:
> Hello Deniz,
>
> If DNSApi was event id 11166, this can belong to a DNS record update problem.
> Check the security permisssions on the forward/reverse lookup zone entry
> of the machine, if an unknown SID is used add the computername to the list
> and give it the same permissions as the unknown account, then remove the
> unknown one.
>
> Group policy is to global , the complete error would be better to see what's
> going on.
>
> 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
My Reverse Lookup Zones section is empty. Am I supposed to put any
records here?
In Forward Lookup Zones, I have (A) records for each station under
Global.local. User COMPUTER$ has enough permissions for the record
COMPUTER. There is nothing recent in the DNS events.
I checked the events for the computer in question this morning.
Starting from yesterday afternoon, it recorded GroupPolicy event 1058
every hour. I don't know what caused it, there are no errors before
it, and the only logged warning was TCPIP 4227 hours before the GP
error. I also remember entering GPUPDATE command on that computer
yesterday and getting the same error as the event log:
The processing of Group Policy failed. Windows attempted to read the
file \\Global.local\sysvol\Global.local\Policies
\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain
controller and was not successful. Group Policy settings may not be
applied until this event is resolved. This issue may be transient and
could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain
controller.
b) File Replication Service Latency (a file created on another domain
controller has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.
After a restart this morning, computer seems to be working fine.
GPUPDATE runs OK as well.
Meinolf Weber [MVP-DS]
If the configured reverse lookup zone is empty you have to check the "create
associated pointer" record in the record properties in the forward lookup
one.
For 1058 are many options available, google for 'event id 1058 Windows attempted
to read'. Also make sure the server is installed with latest SP and patches.
Do you have only one DC or more?
Meinolf Weber [MVP-DS]
Check this for event id 1058 also:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;887303
Deniz
wrote:
> Hello Deniz,
>
> If the configured reverse lookup zone is empty you have to check the "create
> associated pointer" record in the record properties in the forward lookup
> one.
>
> For 1058 are many options available, google for 'event id 1058 Windows attempted
> to read'. Also make sure the server is installed with latest SP and patches.
>
> Do you have only one DC or more?
>
> 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
>
> read more »
There is and there has been only one DC. No substitution/upgrade of DC
ever occurred.
I went into one of the Host (A) records, and checked the box "Update
associated pointer (PTR) record". It gave me an error saying that
there are no reverse lookup zones defined. I went ahead and defined
one.
One thing I haven't tried yet is to rejoin to the domain.
Ace Fekay [MCT]
> On Nov 13, 8:36ï¿œam, Meinolf Weber [MVP-DS] <meiweb@(nospam)gmx.de>
>>>>>>> Node Type . . . . . . . . . . . . : Unknown
>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>> Ethernet adapter Local Area Connection 2:
>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
>>>>>>> Adapter(LNE100TX v4)
>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>> Vista Business 1> ipconfig /all
>>>>>>> Windows IP Configuration
>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>> Ethernet adapter Local Area Connection:
>>>>>>> Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network
>>>>>>> Connection
>>>>>>> Physical Address. . . . . . . . . : 00-22-68-04-48-EB
>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>> Link-local IPv6 Address . . . . . : fe80::6806:4594:ed33:a0c6%11
>>>>>>> (Preferred)
>>>>>>> IPv4 Address. . . . . . . . . . . : 192.168.1.124(Preferred)
>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
>>>>>>> Wireless LAN adapter Wireless Network Connection:
>>>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>>>> Description . . . . . . . . . . . : Atheros AR5007EG Wireless
>>>>>>> Network Adapter
>>>>>>> Physical Address. . . . . . . . . : 00-23-4D-97-FA-28
>>>>>>> DHCP Enabled. . . . . . . . . . . : Yes
>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>> Tunnel adapter Local Area Connection* 6:
>>>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>>>> Description . . . . . . . . . . . : isatap.{69493646-
>>>>>>> EEA0-47F4-8D03-6FB084D382D0}
>>>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>> Tunnel adapter Local Area Connection* 7:
>>>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>>>> Description . . . . . . . . . . . : isatap.{0ED3926F-DCC3-4875-
>>>>>>> B522-0F8FA7753E0B}
>>>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>> I can see the Host (A) record in DNS for the computer MOSCOW, and
>>>>>>> it
>>>>>>> points to 192.168.1.124 as also described in the IPconfig above.
>>>>> In the event viewer first I saw errors like "GroupPolicy" or
>>>>> "DNSApi" which suggested network connection problems. After fiddling
>>>>> around a little bit those errors are not showing anymore. But the
>>>>> problem remains. Another event that is always logged is Tcpip
>>>>> warning 4227, which seems to happen little more often since we
>>>>> moved.
>>
>>>>> Computers appear to be running fine, until I do the Task Manager
>>>>> test, or ipconfig /all test, none of which respond if the computer
>>>>> is having the problem I described. If so, I immediately restart from
>>>>> the command line. Then it runs fine throughout the day. Some
>>>>> computers even run couple of days before they hit by this issue.
>>>>> I will disable the IPv6 today to see if that helps. I will post an
>>>>> update tomorrow.
>>
>>> My Reverse Lookup Zones section is empty. Am I supposed to put any
>>
>> ...
>>
>
> There is and there has been only one DC. No substitution/upgrade of DC
> ever occurred.
>
> I went into one of the Host (A) records, and checked the box "Update
> associated pointer (PTR) record". It gave me an error saying that
> there are no reverse lookup zones defined. I went ahead and defined
> one.
>
> One thing I haven't tried yet is to rejoin to the domain.
If you look at your zone global.local, what do you see in regards of
the "(same as parent)" record? There should only be one record,
pointing to the DC, 192.168.1.100. Same with the 'moscow' A record in
the zone.
Also, look in the _gc_msdcs.global.local zone. Do you see a reference
to the DC? That's your Global Catalog entry.
In the reverse zone, which I believe you just created, make sure
Updates are allowed on the zone.
Also curious, do you have any services disabled on the DC, such as the
DHCP Client Service? Despite its name, that's actually a required
service on all machines, since it is the DNS registration and client
side resolver service.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.
Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Deniz
wrote:
> > On Nov 13, 8:36 am, Meinolf Weber [MVP-DS] <meiweb@(nospam)gmx.de>
> >>>>>>> Node Type . . . . . . . . . . . . : Unknown
> >>>>>>> IP Routing Enabled. . . . . . . . : No
> >>>>>>> WINS Proxy Enabled. . . . . . . . : No
> >>>>>>> DNS Suffix Search List. . . . . . : Global.local
> >>>>>>> Ethernet adapter Local Area Connection 2:
> >>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
> >>>>>>> Adapter(LNE100TX v4)
> >>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
> >>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
> >>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
> >>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
> >>>>>>> Vista Business 1> ipconfig /all
> >>>>>>> Windows IP Configuration
> >>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
> >>>>>>> Node Type . . . . . . . . . . . . : Hybrid
> >>>>>>> IP Routing Enabled. . . . . . . . : No
> >>>>>>> WINS Proxy Enabled. . . . . . . . : No
> >>>>>>> DNS Suffix Search List. . . . . . : Global.local
> >>>>>>> Ethernet adapter Local Area Connection:
> >>>>>>> Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network
> >>>>>>> Connection
> >>>>>>> Physical Address. . . . . . . . . : 00-22-68-04-48-EB
> >>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >>>>>>> Autoconfiguration Enabled . . . . : Yes
> >>>>>>> Link-local IPv6 Address . . . . . : fe80::6806:4594:ed33:a0c6%11
> >>>>>>> (Preferred)
> >>>>>>> IPv4 Address. . . . . . . . . . . : 192.168.1.124(Preferred)
> >>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
> >>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
> >>>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
> >>>>>>> Wireless LAN adapter Wireless Network Connection:
> >>>>>>> Media State . . . . . . . . . . . : Media disconnected
> >>>>>>> Description . . . . . . . . . . . : Atheros AR5007EG Wireless
> >>>>>>> Network Adapter
> >>>>>>> Physical Address. . . . . . . . . : 00-23-4D-97-FA-28
> >>>>>>> DHCP Enabled. . . . . . . . . . . : Yes
> >>>>>>> Autoconfiguration Enabled . . . . : Yes
> >>>>>>> Tunnel adapter Local Area Connection* 6:
> >>>>>>> Media State . . . . . . . . . . . : Media disconnected
> >>>>>>> Description . . . . . . . . . . . : isatap.{69493646-
> >>>>>>> EEA0-47F4-8D03-6FB084D382D0}
> >>>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> >>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >>>>>>> Autoconfiguration Enabled . . . . : Yes
> >>>>>>> Tunnel adapter Local Area Connection* 7:
> >>>>>>> Media State . . . . . . . . . . . : Media disconnected
> >>>>>>> Description . . . . . . . . . . . : isatap.{0ED3926F-DCC3-4875-
> >>>>>>> B522-0F8FA7753E0B}
> >>>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> >>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >>>>>>> Autoconfiguration Enabled . . . . : Yes
> >>>>>>> I can see the Host (A) record in DNS for the computer MOSCOW, and
> >>>>>>> it
> >>>>>>> points to 192.168.1.124 as also described in the IPconfig above.
> >>>>> In the event viewer first I saw errors like "GroupPolicy" or
> >>>>> "DNSApi" which suggested network connection problems. After fiddling
> >>>>> around a little bit those errors are not showing anymore. But the
> >>>>> problem remains. Another event that is always logged is Tcpip
> >>>>> warning 4227, which seems to happen little more often since we
> >>>>> moved.
>
> >>>>> Computers appear to be running fine, until I do the Task Manager
> >>>>> test, or ipconfig /all test, none of which respond if the computer
> >>>>> is having the problem I described. If so, I immediately restart from
> >>>>> the command line. Then it runs fine throughout the day. Some
> >>>>> computers even run couple of days before they hit by this issue.
> >>>>> I will disable the IPv6 today to see if that helps. I will post an
> >>>>> update tomorrow.
>
> >>> My Reverse Lookup Zones section is empty. Am I supposed to put any
>
> >> ...
>
There are 3 "Same as Parent" records: one of each A, NS, SOA. I found
a second NS record which had the IP of 127.0.0.1 but I got rid of that
one. There is one "Same as Parent" A record, AND another A record
named after DC (GLOBAL) both of which are pointing to 192.168.1.100
Moscow A record in the zone has only one IP and that is the IPv4
address of that particular Vista station.
Under _msdcs.Global.local there are NS, SOA, and CNAME records. There
is also gc in there which contains Host (A) Same as Parent pointing to
192.168.1.100
DHCP seems to be working, even though clients do not use it. I see one
scope 192.168.0.0 with one scope option "006 DNS Servers" with the
value 192.168.0.1. I do not use 192.168.0.x addresses anywhere. Should
I change this value?
Thanks,
Deniz
Ace Fekay [MCT]
> wrote:
>>> On Nov 13, 8:36ï¿œam, Meinolf Weber [MVP-DS] <meiweb@(nospam)gmx.de>
>>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>>> Ethernet adapter Local Area Connection 2:
>>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
>>>>>>>>> Adapter(LNE100TX v4)
>>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>>>> Vista Business 1> ipconfig /all
>>>>>>>>> Windows IP Configuration
>>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>>> Ethernet adapter Local Area Connection:
>>>>>>>>> Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network
>>>>>>>>> Connection
>>>>>>>>> Physical Address. . . . . . . . . : 00-22-68-04-48-EB
>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>>>> Link-local IPv6 Address . . . . . : fe80::6806:4594:ed33:a0c6%11
>>>>>>>>> (Preferred)
>>>>>>>>> IPv4 Address. . . . . . . . . . . : 192.168.1.124(Preferred)
>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
>>>>>>>>> Wireless LAN adapter Wireless Network Connection:
>>>>>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>>>>>> Description . . . . . . . . . . . : Atheros AR5007EG Wireless
>>>>>>>>> Network Adapter
>>>>>>>>> Physical Address. . . . . . . . . : 00-23-4D-97-FA-28
>>>>>>>>> DHCP Enabled. . . . . . . . . . . : Yes
>>>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>>>> Tunnel adapter Local Area Connection* 6:
>>>>>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>>>>>> Description . . . . . . . . . . . : isatap.{69493646-
>>>>>>>>> EEA0-47F4-8D03-6FB084D382D0}
>>>>>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>>>> Tunnel adapter Local Area Connection* 7:
>>>>>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>>>>>> Description . . . . . . . . . . . : isatap.{0ED3926F-DCC3-4875-
>>>>>>>>> B522-0F8FA7753E0B}
>>>>>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>>>> I can see the Host (A) record in DNS for the computer MOSCOW, and
>>>>>>>>> it
>>>>>>>>> points to 192.168.1.124 as also described in the IPconfig above.
>>>>>>> In the event viewer first I saw errors like "GroupPolicy" or
>>>>>>> "DNSApi" which suggested network connection problems. After fiddling
>>>>>>> around a little bit those errors are not showing anymore. But the
>>>>>>> problem remains. Another event that is always logged is Tcpip
>>>>>>> warning 4227, which seems to happen little more often since we
>>>>>>> moved.
>>
>>>>>>> Computers appear to be running fine, until I do the Task Manager
>>>>>>> test, or ipconfig /all test, none of which respond if the computer
>>>>>>> is having the problem I described. If so, I immediately restart from
>>>>>>> the command line. Then it runs fine throughout the day. Some
>>>>>>> computers even run couple of days before they hit by this issue.
>>>>>>> I will disable the IPv6 today to see if that helps. I will post an
>>>>>>> update tomorrow.
>>
>>>>> My Reverse Lookup Zones section is empty. Am I supposed to put any
>>>> ...
>>
Hi Deniz,
Yes, you must change the DHCP scope to match your new subnet. You may
have to delete the scope and recreate it.
You will want Scope Options:
003 192.168.1.1 (router or gateway)
006 192.168.1.100 (DNS)
015 global.local (DNS Specific suffix)
If you use WINS, you will want the following options:
044 0x8 (for hybrid)
046 192.168.1.100
I hope that helps.
Ace
Meinolf Weber [MVP-DS]
Really interesting, because of this i never thought/read that he changes
the ip range as i asked before:
"Have you also changed the ip addressing? Did you make sure all machines
use the correct addresses and subnet masks?
Only our public IP (WAN IP on the router) has changed. All other IPs are
static assigned IPs in 192.168.x.x range"
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
>> On Nov 13, 9:38 am, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
>> wrote:
>>
>>>> On Nov 13, 8:36 am, Meinolf Weber [MVP-DS] <meiweb@(nospam)gmx.de>
>>>>>>>>>>>> shutdown) some don't (ipconfig /all)
>>>>>>>>>> Primary Dns Suffix . . . . . . . : Global.local
>>>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>>>> Ethernet adapter Local Area Connection 2:
>>>>>>>>>> Connection-specific DNS Suffix . :
>>>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast
>>>>>>>>>> Ethernet
>>>>>>>>>> Adapter(LNE100TX v4)
>>>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>> Vista Business 1> ipconfig /all
>>>>>>>>>> Windows IP Configuration
>>>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
>>>>>>>>>> Primary Dns Suffix . . . . . . . : Global.local
>>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>>>> Ethernet adapter Local Area Connection:
>>>>>>>>>> Connection-specific DNS Suffix . :
>>>>>>>>>> Description . . . . . . . . . . . : Intel(R) PRO/1000 PL
>>>>>>>>>> Network
>>>>>>>>>> Connection
>>>>>>>>>> Physical Address. . . . . . . . . : 00-22-68-04-48-EB
>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>>>>> Link-local IPv6 Address . . . . . :
>>>>>>>>>> fe80::6806:4594:ed33:a0c6%11
>>>>>>>>>> (Preferred)
>>>>>>>>>> IPv4 Address. . . . . . . . . . . : 192.168.1.124(Preferred)
>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
>>>>>>>>>> Wireless LAN adapter Wireless Network Connection:
>>>>>>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>>>>>>> Connection-specific DNS Suffix . :
>>>>>>>>>> Description . . . . . . . . . . . : Atheros AR5007EG Wireless
>>>>>>>>>> Network Adapter
>>>>>>>>>> Physical Address. . . . . . . . . : 00-23-4D-97-FA-28
>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : Yes
>>>>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>>>>> Tunnel adapter Local Area Connection* 6:
>>>>>>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>>>>>>> Connection-specific DNS Suffix . :
>>>>>>>>>> Description . . . . . . . . . . . : isatap.{69493646-
>>>>>>>>>> EEA0-47F4-8D03-6FB084D382D0}
>>>>>>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>>>>> Tunnel adapter Local Area Connection* 7:
>>>>>>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>>>>>>> Connection-specific DNS Suffix . :
>>>>> read more �
Bill Kearney
Why not? That's the likely source of your troubles. When you use DHCP you
can make changes centrally and then do nothing more than just reboot the
client machines. When you use static configurations you have to manually
visit each machine to make changes, not a good plan.
-Bill Kearney
Ace Fekay [MCT]
news:6cb2911d99778...@msnews.microsoft.com...
Hi Meinolf,
From the poster's response, I am assuming the scope was never changed. Then
was mentioned that DHCP wasn't used, which Bill responded to. So it's
somewhat confusing of exactly what the whole setup is. If DHCP is not being
used, and all clients are static and incorrectly configured, I can
understand the problems. As Bill responded, DHCP properly configured will
take care of all the problems, especially if all of this started with an
IP/network change and not everything was taken into account or planned prior
to the move.
Ace
Deniz
wrote:
> > On Nov 13, 9:38 am, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
> > wrote:
> >>> On Nov 13, 8:36 am, Meinolf Weber [MVP-DS] <meiweb@(nospam)gmx.de>
> >>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
> >>>>>>>>> IP Routing Enabled. . . . . . . . : No
> >>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
> >>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
> >>>>>>>>> Ethernet adapter Local Area Connection 2:
> >>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
> >>>>>>>>> Adapter(LNE100TX v4)
> >>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
> >>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
> >>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
> >>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
> >>>>>>>>> Vista Business 1> ipconfig /all
> >>>>>>>>> Windows IP Configuration
> >>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
> >>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
> >>>>>>>>> IP Routing Enabled. . . . . . . . : No
> >>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
> >>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
> >>>>>>>>> Ethernet adapter Local Area Connection:
> >>>>>>>>> Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network
> >>>>>>>>> Connection
> >>>>>>>>> Physical Address. . . . . . . . . : 00-22-68-04-48-EB
> >>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >>>>>>>>> Autoconfiguration Enabled . . . . : Yes
> >>>>>>>>> Link-local IPv6 Address . . . . . : fe80::6806:4594:ed33:a0c6%11
> >>>>>>>>> (Preferred)
> >>>>>>>>> IPv4 Address. . . . . . . . . . . : 192.168.1.124(Preferred)
> >>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
> >>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
> >>>>>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
> >>>>>>>>> Wireless LAN adapter Wireless Network Connection:
> >>>>>>>>> Media State . . . . . . . . . . . : Media disconnected
> >>>>>>>>> Description . . . . . . . . . . . : Atheros AR5007EG Wireless
> >>>>>>>>> Network Adapter
> >>>>>>>>> Physical Address. . . . . . . . . : 00-23-4D-97-FA-28
> >>>>>>>>> DHCP Enabled. . . . . . . . . . . : Yes
> >>>>>>>>> Autoconfiguration Enabled . . . . : Yes
> >>>>>>>>> Tunnel adapter Local Area Connection* 6:
> >>>>>>>>> Media State . . . . . . . . . . . : Media disconnected
> >>>>>>>>> Description . . . . . . . . . . . : isatap.{69493646-
> >>>>>>>>> EEA0-47F4-8D03-6FB084D382D0}
> >>>>>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> >>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >>>>>>>>> Autoconfiguration Enabled . . . . : Yes
> >>>>>>>>> Tunnel adapter Local Area Connection* 7:
> >>>>>>>>> Media State . . . . . . . . . . . : Media disconnected
> >>>>>>>>> Description . . . . . . . . . . . : isatap.{0ED3926F-DCC3-4875-
> >>>>>>>>> B522-0F8FA7753E0B}
> >>>>>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> >>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >>>>>>>>> Autoconfiguration Enabled . . . . : Yes
> >>>>>>>>> I can see the Host (A) record in DNS for the computer MOSCOW, and
> >>>>>>>>> it
> >>>>>>>>> points to 192.168.1.124 as also described in the IPconfig above.
> >>>>>>> In the event viewer first I saw errors like "GroupPolicy" or
> >>>>>>> "DNSApi" which suggested network connection problems. After fiddling
> >>>>>>> around a little bit those errors are not showing anymore. But the
> >>>>>>> problem remains. Another event that is always logged is Tcpip
> >>>>>>> warning 4227, which seems to happen little more often since we
> >>>>>>> moved.
>
> >>>>>>> Computers appear to be running fine, until I do the Task Manager
> >>>>>>> test, or ipconfig /all test, none of which respond if the computer
> >>>>>>> is having the problem I described. If so, I immediately restart from
> >>>>>>> the command line. Then it runs fine throughout the day. Some
> >>>>>>> computers even run couple of days before they hit by this issue.
> >>>>>>> I will disable the IPv6 today to see if that helps. I will post an
> >>>>>>> update tomorrow.
>
> >>>>> My Reverse Lookup Zones section is empty. Am I supposed to put any
> >>>> ...
>
Hi Ace,
As you can tell I am not an expert on administrating a network. I
learn as I face this kind of problems. You can't imagine how valuable
this discussion is. Thank you for bearing with me so far.
There were 2 reasons for why I did not bother setting DHCP on the DC:
1) The router has DHCP, and I thought 2 DHCPs cannot coexist
peacefully 2)I assigned static IPs to these computers way before the
DC, and I wasn't aware of that the DHCP on DC can assign those IPs.
I guess in order to utilize the DHCP on DC, I should: 1)Assign IPs to
the computers on DHCP 2)make computers get an IP from DHCP 3)
Deactivate the DHCP on the router.
Is that correct?
Deniz
wrote:
> "Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in messagenews:6cb2911d99778...@msnews.microsoft.com...
>
> Hi Meinolf,
>
> From the poster's response, I am assuming the scope was never changed. Then
> was mentioned that DHCP wasn't used, which Bill responded to. So it's
> somewhat confusing of exactly what the whole setup is. If DHCP is not being
> used, and all clients are static and incorrectly configured, I can
> understand the problems. As Bill responded, DHCP properly configured will
> take care of all the problems, especially if all of this started with an
> IP/network change and not everything was taken into account or planned prior
> to the move.
>
> Ace
>
> > Hello Ace Fekay [MCT],
>
> > Really interesting, because of this i never thought/read that he changes
> > the ip range as i asked before:
>
> > "Have you also changed the ip addressing? Did you make sure all machines
> > use the correct addresses and subnet masks?
>
> > Only our public IP (WAN IP on the router) has changed. All other IPs are
> > static assigned IPs in 192.168.x.x range"
>
> > 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
>
> read more »
The clients have static IPs, ranging from 192.168.1.110 to
192.168.1.254
DC has static IP of 192.168.1.100
The IP range 192.168.1.101 - 109 is reserved for dynamic allocation by
the DHCP on the router for wireless devices.
As Bill suggested, it is probably not a good solution to assign IPs to
clients one by one, however I have never visited a client to change
its IP (so far).
What I don't understand is why should moving affect any of this? My DC
configuration was never changed. Our ISP is the same, they only gave
us different public IPs. To me, the only thing that needed to be
changed was the WAN IP setting on the router, and everything should
have worked as it had been working before. Clients still have the same
gateway, same DC, same DNS, same everything - why should they even be
aware of a physical move?
BTW, I really appreciate your time here as I am learning along the
way.
Deniz
Hi Bill,
I meant to answer you but quoted Ace instead about the DHCP issue.
Feel free to interrupt! :)
Ace Fekay [MCT]
> wrote:
>>> On Nov 13, 9:38ï¿œam, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
>>> wrote:
>>>>> On Nov 13, 8:36ï¿œam, Meinolf Weber [MVP-DS] <meiweb@(nospam)gmx.de>
>>>>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>>>>> Ethernet adapter Local Area Connection 2:
>>>>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
>>>>>>>>>>> Adapter(LNE100TX v4)
>>>>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>> Vista Business 1> ipconfig /all
>>>>>>>>>>> Windows IP Configuration
>>>>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
>>>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>>>>> Ethernet adapter Local Area Connection:
>>>>>>>>>>> Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network
>>>>>>>>>>> Connection
>>>>>>>>>>> Physical Address. . . . . . . . . : 00-22-68-04-48-EB
>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>>>>>> Link-local IPv6 Address . . . . . : fe80::6806:4594:ed33:a0c6%11
>>>>>>>>>>> (Preferred)
>>>>>>>>>>> IPv4 Address. . . . . . . . . . . : 192.168.1.124(Preferred)
>>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
>>>>>>>>>>> Wireless LAN adapter Wireless Network Connection:
>>>>>>>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>>>>>>>> Description . . . . . . . . . . . : Atheros AR5007EG Wireless
>>>>>>>>>>> Network Adapter
>>>>>>>>>>> Physical Address. . . . . . . . . : 00-23-4D-97-FA-28
>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : Yes
>>>>>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>>>>>> Tunnel adapter Local Area Connection* 6:
>>>>>>>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>>>>>>>> Description . . . . . . . . . . . : isatap.{69493646-
>>>>>>>>>>> EEA0-47F4-8D03-6FB084D382D0}
>>>>>>>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>>>>>> Tunnel adapter Local Area Connection* 7:
>>>>>>>>>>> Media State . . . . . . . . . . . : Media disconnected
>>>>>>>>>>> Description . . . . . . . . . . . : isatap.{0ED3926F-DCC3-4875-
>>>>>>>>>>> B522-0F8FA7753E0B}
>>>>>>>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>>>>>> I can see the Host (A) record in DNS for the computer MOSCOW, and
>>>>>>>>>>> it
>>>>>>>>>>> points to 192.168.1.124 as also described in the IPconfig above.
>>>>>>>>> In the event viewer first I saw errors like "GroupPolicy" or
>>>>>>>>> "DNSApi" which suggested network connection problems. After fiddling
>>>>>>>>> around a little bit those errors are not showing anymore. But the
>>>>>>>>> problem remains. Another event that is always logged is Tcpip
>>>>>>>>> warning 4227, which seems to happen little more often since we
>>>>>>>>> moved.
>>
>>>>>>>>> Computers appear to be running fine, until I do the Task Manager
>>>>>>>>> test, or ipconfig /all test, none of which respond if the computer
>>>>>>>>> is having the problem I described. If so, I immediately restart from
>>>>>>>>> the command line. Then it runs fine throughout the day. Some
>>>>>>>>> computers even run couple of days before they hit by this issue.
>>>>>>>>> I will disable the IPv6 today to see if that helps. I will post an
>>>>>>>>> update tomorrow.
>>
>>>>>>> My Reverse Lookup Zones section is empty. Am I supposed to put any
>>>>>> ...
>>
Yes, but not in that order. You are correct, two DHCP servers with
identical or overlapping scopes will conflict. In your case, I would
simply disable DHCP on the router, then enable it on the DC. The
advantages are the DC's DHCP (Windows DHCP) interoperates with Dynamic
DNS, as well as uses AD Kerberos security, which the router does not
(nor can it) support. If the router does support Dynamic DNS, it's
optinos are limited with controlling how to register clients into DNS
for the foward lookup zone, and reverse lookup zone.
It's much easier. :-)
Ace
Ace Fekay [MCT]
>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>>>>>>> Ethernet adapter Local Area Connection 2:
>>>>>>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast
>>>>>>>>>>>>> Ethernet
>>>>>>>>>>>>> Adapter(LNE100TX v4)
>>>>>>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
>>>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>>>> Vista Business 1> ipconfig /all
>>>>>>>>>>>>> Windows IP Configuration
>>>>>>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>
>> ...
>>
>
> The clients have static IPs, ranging from 192.168.1.110 to
> 192.168.1.254
> DC has static IP of 192.168.1.100
> The IP range 192.168.1.101 - 109 is reserved for dynamic allocation by
> the DHCP on the router for wireless devices.
> As Bill suggested, it is probably not a good solution to assign IPs to
> clients one by one, however I have never visited a client to change
> its IP (so far).
>
> What I don't understand is why should moving affect any of this? My DC
> configuration was never changed. Our ISP is the same, they only gave
> us different public IPs. To me, the only thing that needed to be
> changed was the WAN IP setting on the router, and everything should
> have worked as it had been working before. Clients still have the same
> gateway, same DC, same DNS, same everything - why should they even be
> aware of a physical move?
>
> BTW, I really appreciate your time here as I am learning along the
> way.
No problem about the time. :-)
So you are saying that internally the IP subnet never changed. From
earlier posts, I assumed the internal range was changed.
Getting back to the TCPIP warning 4227, which I didn't realize was an
EventID# that you are receiving, and thought you were receiving it
elsewhere, it appears to indicate something else is going on with the
client side. Read the following, which doesn't provide specifics, but I
just want to confirm this is the error in the log you are getting.
http://www.eventid.net/display.asp?eventid=4227&eventno=9936&source=tcpip&phase=1
Are you still receiving other errors on the client side or the DC?
Looking back in this thread, you indicated a DNSAPI 11166 error? You
didn't post the EventID#, which I believe Meinolf assumed it was 11166,
which we see off an on. That usually can be alleviated by creating a
reverse zone.
If you see any other errors that are still occuring, *please* post the
_EventID#_ and the Source name in the event message to better help so
we can look them up specifically by their numbers and messages.
Ace
Deniz
wrote:
> > On Nov 14, 9:49 am, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
> >>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
> >>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
> >>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
> >>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
> >>>>>>>>>>>>> Ethernet adapter Local Area Connection 2:
> >>>>>>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast
> >>>>>>>>>>>>> Ethernet
> >>>>>>>>>>>>> Adapter(LNE100TX v4)
> >>>>>>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
> >>>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >>>>>>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
> >>>>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>>>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
> >>>>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
> >>>>>>>>>>>>> Vista Business 1> ipconfig /all
> >>>>>>>>>>>>> Windows IP Configuration
> >>>>>>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
> >>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
> >>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
> >>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
> >>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>
> >> ...
>
>
> > The clients have static IPs, ranging from 192.168.1.110 to
> > 192.168.1.254
> > DC has static IP of 192.168.1.100
> > The IP range 192.168.1.101 - 109 is reserved for dynamic allocation by
> > the DHCP on the router for wireless devices.
> > As Bill suggested, it is probably not a good solution to assign IPs to
> > clients one by one, however I have never visited a client to change
> > its IP (so far).
>
> > What I don't understand is why should moving affect any of this? My DC
> > configuration was never changed. Our ISP is the same, they only gave
> > us different public IPs. To me, the only thing that needed to be
> > changed was the WAN IP setting on the router, and everything should
> > have worked as it had been working before. Clients still have the same
> > gateway, same DC, same DNS, same everything - why should they even be
> > aware of a physical move?
>
> > BTW, I really appreciate your time here as I am learning along the
> > way.
>
> No problem about the time. :-)
>
> So you are saying that internally the IP subnet never changed. From
> earlier posts, I assumed the internal range was changed.
>
> Getting back to the TCPIP warning 4227, which I didn't realize was an
> EventID# that you are receiving, and thought you were receiving it
> elsewhere, it appears to indicate something else is going on with the
> client side. Read the following, which doesn't provide specifics, but I
>
> Are you still receiving other errors on the client side or the DC?
> Looking back in this thread, you indicated a DNSAPI 11166 error? You
> didn't post the EventID#, which I believe Meinolf assumed it was 11166,
> which we see off an on. That usually can be alleviated by creating a
> reverse zone.
>
> If you see any other errors that are still occuring, *please* post the
> _EventID#_ and the Source name in the event message to better help so
> we can look them up specifically by their numbers and messages.
>
> Ace
The DNS API error was 11166, but I haven't seen that since 11/9. I
think the updates I made after your suggestions fixed that problem.
I checked the event log of the station named MOSCOW which I have to
restart this morning. I can see that it downloaded updates from
Microsoft and installed them at around 3AM this morning. It restarted
at around 3:25AM. There are no events logged until 7AM, which shows 2
events until my restart at 8AM: 7003 MS Office 12 Session Terminated,
and 4227 TCP/IP warning. I checked the link you provided but I could
not find an answer: The clients don't have torrent or other port-
consuming applications. Every TCP port is set to expire withing 600
seconds on the router, and I don't have more than 500 open ports at
any given time on the network, let alone having too much open ports
off peak hours.
DNS server events since the move:
10/17 - DNS server has started
11/5 - Error 4015 "The DNS server has encountered a critical error
from the Active Directory. Check that the Active Directory is
functioning properly. "
11/5 - Error 4004 "The DNS server was unable to complete directory
service enumeration of zone .."
11/5 - Error 4004 "The DNS server was unable to complete directory
service enumeration of zone _msdcs.Global.local."
11/5 - Error 4004 "The DNS server was unable to complete directory
service enumeration of zone Global.local. "
11/5 - DNS server has started (3 minutes after the errors)
11/6 - DNS server has started
11/13 - Warning 4521 "The DNS server encountered error 32 attempting
to load zone 1.168.192.in-addr.arpa from Active Directory. " (This
happened right after adding reverse lookup zone)"
11/14 - DNS Server has started (I restarted the DNS server to see if
any of the errors above are logged. No events logged since then)
Directory Server Events:
Until the move, events are consistent (700,701,102,103,1000,1394,1869)
10/17 - Information 1404 NTDS KCC "The local domain controller is now
the intersite topology generator and has assumed responsibility for
generating and maintaining intersite replication topologies for this
site." (on the day of the move)
After the move, events are consistent (700,701,102,103,1000,1394,1869)
Ace Fekay [MCT]
> wrote:
>>> On Nov 14, 9:49ï¿œam, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
>>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
>>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>>>>>>>>> Ethernet adapter Local Area Connection 2:
>>>>>>>>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast
>>>>>>>>>>>>>>> Ethernet
>>>>>>>>>>>>>>> Adapter(LNE100TX v4)
>>>>>>>>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
>>>>>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>>>>>> Vista Business 1> ipconfig /all
>>>>>>>>>>>>>>> Windows IP Configuration
>>>>>>>>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
>>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>> ...
>>
I think this started before the move. Apparently there are some AD
issue, hence why the errors about the reverse zone popped up after
creating the zone. Also, why would it even give you a 1404 if it is the
only DC/GC you have?
Run the following, please:
dcdiag /v /fix > c:\dcdiag.txt
netdiag /v /fix > c:\netdiag.txt
Please post error or failures you see in the log.
Ace
Deniz
wrote:
> > On Nov 17, 10:06 am, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
> > wrote:
> >>> On Nov 14, 9:49 am, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
> >>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
> >>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
> >>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
> >>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
> >>>>>>>>>>>>>>> Ethernet adapter Local Area Connection 2:
> >>>>>>>>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast
> >>>>>>>>>>>>>>> Ethernet
> >>>>>>>>>>>>>>> Adapter(LNE100TX v4)
> >>>>>>>>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
> >>>>>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >>>>>>>>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
> >>>>>>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>>>>>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
> >>>>>>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
> >>>>>>>>>>>>>>> Vista Business 1> ipconfig /all
> >>>>>>>>>>>>>>> Windows IP Configuration
> >>>>>>>>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
> >>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
> >>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
> >>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
> >>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
> >>>> ...
>
I do not know why 1404 is logged. I don't even know what the intersite
topology generator is. That's the only entry for that event, and it
happened once the DC is booted up in the new office location.
I ran the dcdiag and netdiag. All the tests passed OK, some skipped
but no errors or failures.
Ace Fekay [MCT]
> wrote:
>>> On Nov 17, 10:06ï¿œam, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
>>> wrote:
>>>>> On Nov 14, 9:49ï¿œam, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
>>>>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
>>>>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>>>>>>>>>>> Ethernet adapter Local Area Connection 2:
>>>>>>>>>>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast
>>>>>>>>>>>>>>>>> Ethernet
>>>>>>>>>>>>>>>>> Adapter(LNE100TX v4)
>>>>>>>>>>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
>>>>>>>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>>>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>>>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>>>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>>>>>>>> Vista Business 1> ipconfig /all
>>>>>>>>>>>>>>>>> Windows IP Configuration
>>>>>>>>>>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
>>>>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>> ...
>>
Do you have AD Sites setup?
You said you only have one DC, correct?
Did you run those diagnostics I suggested?
Ace
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.
Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
PaulChavez
Verify there's not a speed or duplex mismatch between switch and hosts.
Since you changed the switch, this could be a possible issue.
Check and/or disable the autotuning settings, I have had similar issues with
both Vista and Server 2008 that were resolved by this.
This command will disable autotuning:
netsh interface tcp set global autotuninglevel=disabled
Good luck.
Paul
"Deniz" wrote:
> .
>
Deniz
wrote:
> > On Nov 17, 12:36 pm, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
> > wrote:
> >>> On Nov 17, 10:06 am, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
> >>> wrote:
> >>>>> On Nov 14, 9:49 am, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
> >>>>> wrote:
> >>>>>> "Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in
> >>>>>> messagenews:6cb2911d99778...@msnews.microsoft.com...
> >>>>>> Hi Meinolf,
>
> >>>>>> From the poster's response, I am assuming the scope was never changed.
> >>>>>> Then was mentioned that DHCP wasn't used, which Bill responded to. So
> >>>>>> it's somewhat confusing of exactly what the whole setup is. If DHCP is
> >>>>>> can understand the problems. As Bill responded, DHCP properly configured
> >>>>>> will take care of all the problems, especially if all of this started
> >>>>>>>>>>>>>>>> if this helps.
>
> >>>>>>>>>>>>>>>> Any errors in the event viewer? Strange that it comes only
> >>>>>>>>>>>>>>>> over
> >>>>>>>>>>>>>>>>>>> without the domain controller (2003) for a day. On the next
> >>>>>>>>>>>>>>>>>>> day,
> >>>>>>>>>>>>>>>>>>> moved to the new location. The computers detected a new
> >>>>>>>>>>>>>>>>>>>network,
> >>>>>>>>>>>>>>>>>>> so not everything worked out of the boxafterthemove:
> >>>>>>>>>>>>>>>>>>> some
> >>>>>>>>>>>>>>>>>>> firewall and sharing settings were reset since they have a
> >>>>>>>>>>>>>>>>>>> new
> >>>>>>>>>>>>>>>>>>> changes
> >>>>>>>>>>>>>>>>>>> on the computers (auto-updates were turned off) The only
> >>>>>>>>>>>>>>>>>>> are
> >>>>>>>>>>>>>>>>>>> the cabling in the walls, and the Ethernet switch (old one:
> >>>>>>>>>>>>>>>>>>> Siemens + Netgear, new one: Cisco SR224)
> >>>>>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>> mornings when they were left on overnight:
> >>>>>>>>>>>>>>>>>>> - User cannot open any new programs or task manager.
> >>>>>>>>>>>>>>>>>>> Currently
> >>>>>>>>>>>>>>>>>>> open
> >>>>>>>>>>>>>>>>>>> programs run OK
> >>>>>>>>>>>>>>>>>>> - CTRL+ALT+DEL brings a black screen, and then shows this
> >>>>>>>>>>>>>>>>>>> error:
> >>>>>>>>>>>>>>>>>>> "Logon Process has failed to create the security options
> >>>>>>>>>>>>>>>>>>> dialog.
> >>>>>>>>>>>>>>>>>>> "
> >>>>>>>>>>>>>>>>>>> with a dialog box "Failure - Security Options"
> >>>>>>>>>>>>>>>>>>> - Command prompt can be opened. Some commands work
> >>>>>>>>>>>>>>>>>>> (ipconfig,
> >>>>>>>>>>>>>>>>>>> - I can ping theunresponsiveVistaclient on the LAN, and
> >>>>>>>>>>>>>>>>>>> I can
> >>>>>>>>>>>>>>>>>>> remotely shutdown/restart it although it waits at that
> >>>>>>>>>>>>>>>>>>> black
> >>>>>>>>>>>>>>>>>>> screen
> >>>>>>>>>>>>>>>>>>> for few minutes before it starts to shutdown
> >>>>>>>>>>>>>>>>>>> - Event logs do not show any specific error before the
> >>>>>>>>>>>>>>>>>>>clients
> >>>>>>>>>>>>>>>>>>> become
> >>>>>>>>>>>>>>>>>>>unresponsive
> >>>>>>>>>>>>>>>>>>> Since I did not change any software/hardware on the
> >>>>>>>>>>>>>>>>>>> machines, I
> >>>>>>>>>>>>>>>>>>> have
> >>>>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
> >>>>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
> >>>>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
> >>>>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
> >>>>>>>>>>>>>>>>> Ethernet adapter Local Area Connection 2:
> >>>>>>>>>>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast
> >>>>>>>>>>>>>>>>> Ethernet
> >>>>>>>>>>>>>>>>> Adapter(LNE100TX v4)
> >>>>>>>>>>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
> >>>>>>>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >>>>>>>>>>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
> >>>>>>>>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>>>>>>>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
> >>>>>>>>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
> >>>>>>>>>>>>>>>>> Windows IP Configuration
> >>>>>>>>>>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
> >>>>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
> >>>>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
> >>>>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
> >>>>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
> >>>>>> ...
>
>
> >>>>> Theclientshave static IPs, ranging from 192.168.1.110 to
> >>>>> 192.168.1.254
> >>>>> DC has static IP of 192.168.1.100
> >>>>> The IP range 192.168.1.101 - 109 is reserved for dynamic allocation by
> >>>>> the DHCP on the router for wireless devices.
> >>>>> As Bill suggested, it is probably not a good solution to assign IPs to
> >>>>> its IP (so far).
>
> >>>>> What I don't understand is why should moving affect any of this? My DC
> >>>>> configuration was never changed. Our ISP is the same, they only gave
> >>>>> us different public IPs. To me, the only thing that needed to be
> >>>>> changed was the WAN IP setting on the router, and everything should
> >>>>> gateway, same DC, same DNS, same everything - why should they even be
> >>>>> aware of a physicalmove?
>
> >>>>> BTW, I really appreciate your time here as I am learning along the
> >>>>> way.
>
> >>>> No problem about the time. :-)
>
> >>>> So you are saying that internally the IP subnet never changed. From
> >>>> earlier posts, I assumed the internal range was changed.
> >>>> Getting back to the TCPIP warning 4227, which I didn't realize was an
> >>>> EventID# that you are receiving, and thought you were receiving it
> >>>> elsewhere, it appears to indicate something else is going on with the
> >>>> client side. Read the following, which doesn't provide specifics, but I
> >>>> just want to confirm this is the error in the log you are
> >>>> getting.http://www.eventid.net/display.asp?eventid=4227&eventno=9936&source=t...
> >>>> Are you still receiving other errors on the client side or the DC?
> >>>> Looking back in this thread, you indicated a DNSAPI 11166 error? You
> >>>> didn't post the EventID#, which I believe Meinolf assumed it was 11166,
> >>>> which we see off an on. That usually can be alleviated by creating a
> >>>> reverse zone.
>
> >>>> If you see any other errors that are still occuring, *please* post the
> >>>> _EventID#_ and the Source name in the event message to better help so
> >>>> we can look them up specifically by their numbers and messages.
> >>>> Ace
>
> >>> The DNS API error was 11166, but I haven't seen that since 11/9. I
> >>> I checked the event log of the station named MOSCOW which I have to
> >>> restart this morning. I can see that it downloaded updates from
> >>> Microsoft and installed them at around 3AM this morning. It restarted
> >>> at around 3:25AM. There are no events logged until 7AM, which shows 2
> >>> events until my restart at 8AM: 7003 MS Office 12 Session Terminated,
> >>> and 4227 TCP/IP warning. I checked the link you provided but I could
> >>> consuming applications. Every TCP port is set to expire withing 600
> >>> seconds on the router, and I don't have more than 500 open ports at
> >>> off peak hours.
>
> >>> DNS server events since themove:
> >>> 10/17 - DNS server has started
> >>> 11/5 - Error 4015 "The DNS server has encountered a critical error
> >>> from the Active Directory. Check that the Active Directory is
> >>> functioning properly. "
> >>> 11/5 - Error 4004 "The DNS server was unable to complete directory
> >>> service enumeration of zone .."
> >>> 11/5 - Error 4004 "The DNS server was unable to complete directory
> >>> service enumeration of zone _msdcs.Global.local."
> >>> 11/5 - Error 4004 "The DNS server was unable to complete directory
> >>> service enumeration of zone Global.local. "
> >>> 11/6 - DNS server has started
> >>> 11/13 - Warning 4521 "The DNS server encountered error 32 attempting
> >>> to load zone 1.168.192.in-addr.arpa from Active Directory. " (This
> >>> 11/14 - DNS Server has started (I restarted the DNS server to see if
> >>> any of the errors above are logged. No events logged since then)
> >>> Directory Server Events:
> >>> 10/17 - Information 1404 NTDS KCC "The local domain controller is now
> >>> the intersite topology generator and has assumed responsibility for
> >>> generating and maintaining intersite replication topologies for this
> >>> site." (on the day of themove)
>
> >> I think this started before themove. Apparently there are some AD
I ran the dcdiag and netdiag as you suggested. All the tests passed
OK, some skipped but no errors or failures. And yes, only one DC.
For now I suggested users to shut their computer down before leaving
for the day since this happens only a handful of computers. Maybe we
will hire a network admin to look into this. My knowledge is limited,
and I have spent more time than anticipated. I thank you all.
Deniz
Deniz
wrote:
> After reading the whole thread, here are a couple other ideas to check out.
>
> Verify there's not a speed or duplex mismatch between switch and hosts.
> Since you changed the switch, this could be a possible issue.
>
> Check and/or disable the autotuning settings, I have had similar issues with
> both Vista and Server 2008 that were resolved by this.
>
> This command will disable autotuning:
> netsh interface tcp set global autotuninglevel=disabled
>
> Good luck.
>
> Paul
>
Hi Paul,
I will give it a try before I give up on this whole issue.
Thanks!
Deniz
Ace Fekay [MCT]
> On Nov 17, 4:07ï¿œpm, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
> wrote:
>>> On Nov 17, 12:36ï¿œpm, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
>>> wrote:
>>>>> On Nov 17, 10:06ï¿œam, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
>>>>> wrote:
>>>>>>> On Nov 14, 9:49ï¿œam, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
>>>>>>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
>>>>>>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>>>>>>>>>>>>> Ethernet adapter Local Area Connection 2:
>>>>>>>>>>>>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast
>>>>>>>>>>>>>>>>>>> Ethernet
>>>>>>>>>>>>>>>>>>> Adapter(LNE100TX v4)
>>>>>>>>>>>>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
>>>>>>>>>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>>>>>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>>>>>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>>>>>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>>>>>>>>>> VistaBusiness 1> ipconfig /all
>>>>>>>>>>>>>>>>>>> Windows IP Configuration
>>>>>>>>>>>>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
>>>>>>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>> ...
>>
Hi Deniz,
That may be a better course of action. A qualified individual should be
able to spot or figure out the problem hands on. If you need any more
assistance that we can help with through the Microsoft newsgroups,
please do post back.
Ace
Deniz
wrote:
> > On Nov 17, 4:07 pm, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
> > wrote:
> >>> On Nov 17, 12:36 pm, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
> >>> wrote:
> >>>>> On Nov 17, 10:06 am, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
> >>>>> wrote:
> >>>>>>> On Nov 14, 9:49 am, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
> >>>>>>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
> >>>>>>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
> >>>>>>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
> >>>>>>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
> >>>>>>>>>>>>>>>>>>> Ethernet adapter Local Area Connection 2:
> >>>>>>>>>>>>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast
> >>>>>>>>>>>>>>>>>>> Ethernet
> >>>>>>>>>>>>>>>>>>> Adapter(LNE100TX v4)
> >>>>>>>>>>>>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
> >>>>>>>>>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >>>>>>>>>>>>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
> >>>>>>>>>>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>>>>>>>>>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
> >>>>>>>>>>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
> >>>>>>>>>>>>>>>>>>> VistaBusiness 1> ipconfig /all
> >>>>>>>>>>>>>>>>>>> Windows IP Configuration
> >>>>>>>>>>>>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
> >>>>>>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
> >>>>>>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
> >>>>>>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
> >>>>>>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
> >>>>>>>> ...
>
>
> > I ran the dcdiag and netdiag as you suggested. All the tests passed
> > OK, some skipped but no errors or failures. And yes, only one DC.
>
> > For now I suggested users to shut their computer down before leaving
> > for the day since this happens only a handful of computers. Maybe we
> > will hire a network admin to look into this. My knowledge is limited,
> > and I have spent more time than anticipated. I thank you all.
>
> > Deniz
>
> Hi Deniz,
>
> That may be a better course of action. A qualified individual should be
> able to spot or figure out the problem hands on. If you need any more
> assistance that we can help with through the Microsoft newsgroups,
> please do post back.
>
> Ace
Per Paul's suggestion, I disabled autotuning on TCP for two clients
last night, and they were OK this morning. So far so good. I assume
this was the cause, and I will post back if disabling autotuning was
not the solution.
I am also glad to fix the small glitches on the server along the way
with the help from you guys :)
Thank you all,
Deniz
Bill Kearney
> identical or overlapping scopes will conflict. In your case, I would
> simply disable DHCP on the router, then enable it on the DC. The
> advantages are the DC's DHCP (Windows DHCP) interoperates with Dynamic
> DNS, as well as uses AD Kerberos security, which the router does not (nor
> can it) support. If the router does support Dynamic DNS, it's optinos are
> limited with controlling how to register clients into DNS for the foward
> lookup zone, and reverse lookup zone.
>
> It's much easier. :-)
Ace is exactly right. DHCP running on a windows server (it can be any
member server, it need not be the DC) can integrate itself with DNS
automagically. It really is a superior solution to router or other OS-based
DHCP (and DNS) services.
It really does make desktop IP addressing a lot easier to administer.
If you have hosts that need to stay on the same addresses you can do that by
setting up a DHCP reservation. That way they always get the same IP
address. This is very handy for dumb devices like printers. Plug their
network MAC address into a reservation and never worry about having to
configure the front panel again.
My only complaint about the DHCP service is there's not an easy way to
convert an existing lease to a reservation. Just makes for some added work
through retyping.
-Bill
Bill Kearney
> Feel free to interrupt! :)
No worries. Be sure to follow up with the group when you get things working
better.
Ace Fekay [MCT]
> wrote:
>>> On Nov 17, 4:07ï¿œpm, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
>>> wrote:
>>>>> On Nov 17, 12:36ï¿œpm, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
>>>>> wrote:
>>>>>>> On Nov 17, 10:06ï¿œam, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
>>>>>>> wrote:
>>>>>>>>> On Nov 14, 9:49ï¿œam, "Ace Fekay [MCT]"
>>>>>>>>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Unknown
>>>>>>>>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>>>>>>>>>>>>>>> Ethernet adapter Local Area Connection 2:
>>>>>>>>>>>>>>>>>>>>> Description . . . . . . . . . . . : Linksys LNE100TX Fast
>>>>>>>>>>>>>>>>>>>>> Ethernet
>>>>>>>>>>>>>>>>>>>>> Adapter(LNE100TX v4)
>>>>>>>>>>>>>>>>>>>>> Physical Address. . . . . . . . . : 00-12-17-51-56-44
>>>>>>>>>>>>>>>>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>>>>>>>>>>>>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>>>>>>>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>>>>>>>>>>>>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>>>>>>>>>>>>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.100
>>>>>>>>>>>>>>>>>>>>> VistaBusiness 1> ipconfig /all
>>>>>>>>>>>>>>>>>>>>> Windows IP Configuration
>>>>>>>>>>>>>>>>>>>>> Host Name . . . . . . . . . . . . : MOSCOW
>>>>>>>>>>>>>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>>>>>>>>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>>>>>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>>>>>>>>>>>>> DNS Suffix Search List. . . . . . : Global.local
>>>>>>>>>> ...
>>
Glad to hear Paul's suggestion worked. :-)
Ace
Ace Fekay [MCT]
Good point. One of the very few nuances compared to all the goodies
Windows DHCP provides!!
:-)
Ace
Deniz
wrote:
> >> Yes, but not in that order. You are correct, two DHCP servers with
> >> identical or overlapping scopes will conflict. In your case, I would simply
> >> disable DHCP on the router, then enable it on the DC. The advantages are
> >> the DC's DHCP (Windows DHCP) interoperates with Dynamic DNS, as well as
> >> uses AD Kerberos security, which the router does not (nor can it) support.
> >> If the router does support Dynamic DNS, it's optinos are limited with
> >> and reverse lookup zone.
>
> >> It's much easier. :-)
>
> > Ace is exactly right. DHCP running on a windows server (it can be any member
> > server, it need not be the DC) can integrate itself with DNS automagically.
> > It really is a superior solution to router or other OS-based DHCP (and DNS)
> > services.
>
> > It really does make desktop IP addressing a lot easier to administer.
>
> > If you have hosts that need to stay on the same addresses you can do that by
> > setting up a DHCP reservation. That way they always get the same IP address.
> > This is very handy for dumb devices like printers. Plug their network MAC
> > address into a reservation and never worry about having to configure the
> > front panel again.
>
> > My only complaint about the DHCP service is there's not an easy way to
> > convert an existing lease to a reservation. Just makes for some added work
> > through retyping.
>
> > -Bill
>
> Good point. One of the very few nuances compared to all the goodies
> Windows DHCP provides!!
>
> :-)
>
> Ace
Disabling Autotuning did not solve my issue.
I will play around with DHCP more. I already entered reservations in
DHCP, and put the DHCP on the router in "Forwarder" mode. I will start
setting the clients one by one so that they can obtain IP from the
DHCP. This works on wired clients, but now all the wireless clients
are gone e.g. they cannot even locate the SSID when the DHCP on the
router is either disabled or in Forwarder mode.
Ace Fekay [MCT]
> wrote:
>>>> Yes, but not in that order. You are correct, two DHCP servers with
>>>> identical or overlapping scopes will conflict. In your case, I would
>>>> simply disable DHCP on the router, then enable it on the DC. The
>>>> advantages are the DC's DHCP (Windows DHCP) interoperates with Dynamic
>>>> DNS, as well as uses AD Kerberos security, which the router does not (nor
>>>> can it) support. If the router does support Dynamic DNS, it's optinos are
>>>> limited with controlling how to registerclientsinto DNS for the foward
>>>> lookup zone, and reverse lookup zone.
>>
>>>> It's much easier. :-)
>>
>>
>>> It really does make desktop IP addressing a lot easier to administer.
>>> If you have hosts that need to stay on the same addresses you can do that
>>> address. ï¿œThis is very handy for dumb devices like printers. ï¿œPlug their
>>> configure the front panel again.
>>
>>> My only complaint about the DHCP service is there's not an easy way to
>>> through retyping.
>>
>>> -Bill
>>
>> Good point. One of the very few nuances compared to all the goodies
>> Windows DHCP provides!!
>>
>> :-)
>>
>> Ace
>
> Disabling Autotuning did not solve my issue.
>
> I will play around with DHCP more. I already entered reservations in
> DHCP, and put the DHCP on the router in "Forwarder" mode. I will start
> setting the clients one by one so that they can obtain IP from the
> DHCP. This works on wired clients, but now all the wireless clients
> are gone e.g. they cannot even locate the SSID when the DHCP on the
> router is either disabled or in Forwarder mode.
Refresh my memory, please. What is DHCP Forwarding mode on the router?
From all of us suggesting help, we all said to eliminate the router for
DHCP. Unless I misunderstand what Forwarding mode does.
Is the router a wireles AP, too? If so, set it to 'corporate' mode (or
whatever it's called that will not make it NAT to wireless folks) so
the wireless folks are on the same subnet as the wired subnet.
What kind of router is it?
Ace
Deniz
wrote:
> > On Nov 20, 7:49 pm, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
> > wrote:
> >>>> Yes, but not in that order. You are correct, two DHCP servers with
> >>>> identical or overlapping scopes will conflict. In your case, I would
> >>>> simply disable DHCP on the router, then enable it on the DC. The
> >>>> advantages are the DC's DHCP (Windows DHCP) interoperates with Dynamic
> >>>> DNS, as well as uses AD Kerberos security, which the router does not (nor
> >>>> can it) support. If the router does support Dynamic DNS, it's optinos are
> >>>> limited with controlling how to registerclientsinto DNS for the foward
> >>>> lookup zone, and reverse lookup zone.
>
> >>>> It's much easier. :-)
>
> >>> member server, it need not be the DC) can integrate itself with DNS
> >>> OS-based DHCP (and DNS) services.
>
> >>> It really does make desktop IP addressing a lot easier to administer.
> >>> If you have hosts that need to stay on the same addresses you can do that
> >>> address. This is very handy for dumb devices like printers. Plug their
> >>> network MAC address into a reservation and never worry about having to
> >>> configure the front panel again.
>
> >>> My only complaint about the DHCP service is there's not an easy way to
> >>> through retyping.
>
> >>> -Bill
>
> >> Good point. One of the very few nuances compared to all the goodies
> >> Windows DHCP provides!!
>
> >> :-)
>
> >> Ace
>
> > Disabling Autotuning did not solve my issue.
>
> > I will play around with DHCP more. I already entered reservations in
> > DHCP, and put the DHCP on the router in "Forwarder" mode. I will start
> > DHCP. This works on wiredclients, but now all the wirelessclients
> > are gone e.g. they cannot even locate the SSID when the DHCP on the
> > router is either disabled or in Forwarder mode.
>
> Refresh my memory, please. What is DHCP Forwarding mode on the router?
>
> From all of us suggesting help, we all said to eliminate the router for
> DHCP. Unless I misunderstand what Forwarding mode does.
>
> Is the router a wireles AP, too? If so, set it to 'corporate' mode (or
> whatever it's called that will not make it NAT to wireless folks) so
> the wireless folks are on the same subnet as the wired subnet.
>
> What kind of router is it?
>
> Ace
It seems that the router was the problem. I haven't seen this
particular problem since I replaced the router. I guess that's what I
should have tried first. It was a Linksys router with DD-WRT firmware.
Apparently DHCP forwarding mode is when you want to use a DHCP server
outside of the network. If there is a DHCP on the network, it is
advised to turn the router's DHCP off completely.
Now I put a new wired router with DHCP off (DNS and DHCP is handled by
the DC), and I connected the old router to the new router to serve as
a wireless access point (WAN/DHCP off). Both wired and wireless
clients can now get IPs from the server. Just the way I wanted it! IP
reservations seem to be working fine too.
Another annoyance I found during this process was that once a client
is told to use the DHCP instead of static IP, it will use an
unauthenticated network connection (Global.Local 2) until it's
restarted (or else its network-related capabilities will be limited).
Once it's restarted it detects the domain network Global.Local fine.
Thanks for all the help.
Deniz
Ace Fekay [MCT]
> wrote:
>>> On Nov 20, 7:49ï¿œpm, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
>>> wrote:
>>>>>> Yes, but not in that order. You are correct, two DHCP servers with
>>>>>> identical or overlapping scopes will conflict. In your case, I would
>>>>>> simply disable DHCP on the router, then enable it on the DC. The
>>>>>> advantages are the DC's DHCP (Windows DHCP) interoperates with Dynamic
>>>>>> DNS, as well as uses AD Kerberos security, which the router does not
>>>>>> (nor can it) support. If the router does support Dynamic DNS, it's
>>>>>> optinos are limited with controlling how to registerclientsinto DNS for
>>>>>> the foward lookup zone, and reverse lookup zone.
>>>>>> It's much easier. :-)
>>
>>>>> member server, it need not be the DC) can integrate itself with DNS
>>>>> OS-based DHCP (and DNS) services.
>>
>>>>> It really does make desktop IP addressing a lot easier to administer.
>>>>> If you have hosts that need to stay on the same addresses you can do that
>>>>> address. ï¿œThis is very handy for dumb devices like printers. ï¿œPlug their
>>>>> network MAC address into a reservation and never worry about having to
>>>>> configure the front panel again.
>>
>>>>> My only complaint about the DHCP service is there's not an easy way to
So DHCP forwarding is like an IP helper (on Cisco) or a DHCP Relay
Agent (under Windows).
Disabling DHCP on the router is what we've been saying, correct?
Where is global.local2 coming from? Is there another DHCP on the
network? Sorry, but I'm not sure what you mean by an unauthenticated
network connection.
Ace
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.
Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
Deniz
wrote:
> > On Nov 24, 9:18 am, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
> > wrote:
> >>> On Nov 20, 7:49 pm, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
> >>> wrote:
> >>>>>> Yes, but not in that order. You are correct, two DHCP servers with
> >>>>>> identical or overlapping scopes will conflict. In your case, I would
> >>>>>> simply disable DHCP on the router, then enable it on the DC. The
> >>>>>> advantages are the DC's DHCP (Windows DHCP) interoperates with Dynamic
> >>>>>> DNS, as well as uses AD Kerberos security, which the router does not
> >>>>>> (nor can it) support. If the router does support Dynamic DNS, it's
> >>>>>> optinos are limited with controlling how to registerclientsinto DNS for
> >>>>>> the foward lookup zone, and reverse lookup zone.
> >>>>>> It's much easier. :-)
>
> >>>>> member server, it need not be the DC) can integrate itself with DNS
> >>>>> OS-based DHCP (and DNS) services.
>
> >>>>> It really does make desktop IP addressing a lot easier to administer.
> >>>>> If you have hosts that need to stay on the same addresses you can do that
> >>>>> address. This is very handy for dumb devices like printers. Plug their
> >>>>> network MAC address into a reservation and never worry about having to
> >>>>> configure the front panel again.
>
> >>>>> My only complaint about the DHCP service is there's not an easy way to
Yes, you told me to disable the DHCP. In current setup it works like a
charm.
As for the "domain.local 2" problem, I don't know the cause but I
don't care much since it goes away after one restart. You can find
similar discussions all over the internet (one is at
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/Windows_Vista/Q_23212198.html)
Current setup is working fine so thank you very much again for all the
help.
Ace Fekay [MCT]
> wrote:
>>> On Nov 24, 9:18ï¿œam, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
>>> wrote:
>>>>> On Nov 20, 7:49ï¿œpm, Ace Fekay [MCT] <ace...@mvps.RemoveThisPart.org>
>>>>> wrote:
>>>>>>>> Yes, but not in that order. You are correct, two DHCP servers with
>>>>>>>> identical or overlapping scopes will conflict. In your case, I would
>>>>>>>> simply disable DHCP on the router, then enable it on the DC. The
>>>>>>>> advantages are the DC's DHCP (Windows DHCP) interoperates with Dynamic
>>>>>>>> DNS, as well as uses AD Kerberos security, which the router does not
>>>>>>>> (nor can it) support. If the router does support Dynamic DNS, it's
>>>>>>>> optinos are limited with controlling how to registerclientsinto DNS
>>>>>>>> for the foward lookup zone, and reverse lookup zone.
>>>>>>>> It's much easier. :-)
>>
>>>>>>> member server, it need not be the DC) can integrate itself with DNS
>>>>>>> OS-based DHCP (and DNS) services.
>>>>>>> It really does make desktop IP addressing a lot easier to administer.
>>>>>>> If you have hosts that need to stay on the same addresses you can do
>>>>>>> same IP address. ï¿œThis is very handy for dumb devices like printers.
>>>>>>> ï¿œPlug their network MAC address into a reservation and never worry
>>>>>>> My only complaint about the DHCP service is there's not an easy way to
I haven't personally seen the "2" problem, but if it's disappearing and
not causing a concern, you can ignore it. I'll look around and if I
find anything else, I'll post back.
Also, as an FYI regarding posting Experts-Exchange links, you can't see
the 'answers' or responses when you scroll down unless you have an
account. To get around that, copy and paste the experts Exchange link
into a Google search, and click on the first result, now you can see
the responses when you scroll down. For some reason, search referrals
allow you to get into it.
Ace
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.
Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check