Re: Vista clients became unresponsive after network move
- From: Deniz <deniz.turkmen@xxxxxxxxx>
- Date: Tue, 17 Nov 2009 08:42:46 -0800 (PST)
On Nov 14, 9:49 am, "Ace Fekay [MCT]" <ace...@xxxxxxxxxxxxxxxxxxxxxxx>
wrote:
"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in messagenews:6cb2911d99778cc333f70e1a076@xxxxxxxxxxxxxxxxxxxxxxx
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
** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
On Nov 13, 9:38 am, Ace Fekay [MCT] <ace...@xxxxxxxxxxxxxxxxxxxxxxx>
wrote:
On Nov 13, 8:36 am, Meinolf Weber [MVP-DS] <meiweb@(nospam)gmx.de>
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
** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
On Nov 13, 2:42 am, Meinolf Weber [MVP-DS]
<meiweb@(nospam)gmx.de> 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
** HELP us help
YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
On Nov 12, 2:06 pm, Meinolf Weber [MVP-DS]
<meiweb@(nospam)gmx.de> 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
** HELP us help
YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
On Nov 12, 11:31 am, Meinolf Weber [MVP-DS]
<meiweb@(nospam)gmx.de> 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
** HELP us help
YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
Hi,
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-swit
ch---
--
-- DC - and-clients--
Thank you,
Deniz
Hi Meinolf,
Only our public IP (WAN IP on the router) has changed. AllDC>> ipconfig /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>>
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
...
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.
.
- Follow-Ups:
- Re: Vista clients became unresponsive after network move
- From: Ace Fekay [MCT]
- Re: Vista clients became unresponsive after network move
- References:
- Re: Vista clients became unresponsive after network move
- From: Ace Fekay [MCT]
- Re: Vista clients became unresponsive after network move
- From: Meinolf Weber [MVP-DS]
- Re: Vista clients became unresponsive after network move
- From: Ace Fekay [MCT]
- Re: Vista clients became unresponsive after network move
- Prev by Date: Re: Vista clients became unresponsive after network move
- Next by Date: Re: Vista clients became unresponsive after network move
- Previous by thread: Re: Vista clients became unresponsive after network move
- Next by thread: Re: Vista clients became unresponsive after network move
- Index(es):
Relevant Pages
|
