Unable to execute Logon Script after change IP address

  • Thread starter Thread starter Andy
  • Start date Start date
A

Andy

Hi, we have changed our client workstations (Windows 2000
Professional) from private IP address 172.16.x.x to
128.235.x.x (follow corporate standard). Afterwards, some
of clients are unable to map the network drives by running
the logon scripts.
 
One important thing you didn't mention is that how you map the drives using
login scripts. Since you changed your clients, possibly you changed your
servers' too.

One thing now I can point out is to make sure your DNS servers are
configured correctly and your clients are pointing to your DNS servers only.

BR,
Denis
 
Hi Denis,

Thanks. All clients' DNS settings are correct. Since the
128.235.x.x is public registered IP address spool, we have
blocked the route to this IP address at Internet gateway
router and added a reverse-lookup at our DNS servers. It
seems some of clients are unable to execute the logon
scripts or even authenticated by DC. But they can ping DC
by NetBIOS name.
 
Pinging by name doesn't necessarily mean that DNS is working. Ensure that
the DCs are pointing to internal DNS servers, that that DNS server is set to
listen on all network adapters, or if this isn't possible, ensure that it's
still not listening on the old address if configured otherwise, and restart
the netlogon service (DHCP client must be running and the zone must accept
automatic updates).

Ensure that all clients are pointing to the appropriate DNS servers too.

The fact that it was working and now isn't indicates the IP change has
broken things - thus, 999 times out of 1000 this'll be a DNS problem.

Check, and check again.


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net


Hi Denis,

Thanks. All clients' DNS settings are correct. Since the
128.235.x.x is public registered IP address spool, we have
blocked the route to this IP address at Internet gateway
router and added a reverse-lookup at our DNS servers. It
seems some of clients are unable to execute the logon
scripts or even authenticated by DC. But they can ping DC
by NetBIOS name.
 
Back
Top