Domain name screwup

[chrisk96x]

Good Day,

I have a client who, before I came on board, configured their Windows 2000 local domain name the same as their web page. mydomain.org and mydomain.org as the example.

Things weren't working so well (slow logons, couldn't get to their mail.mydomain.org server, etc.) so I created a work around by putting the domain controller IP address (also the local domain DNS server) in as the primary DNS on the workstations (that fixed the slow logons) and added some host file entries (that fixed the web page and e-mail issues) and everything worked fine for quite awhile.

Then they had a web designer come in and he whacked all the host files and reconfigured TCP/IP on the network computers. He took out my primary DNS entries and replaced them with the DNS entries for the ISP.

Sooo, now we're back to slow logons and some other more insideous stuff going on. "Windows cannot determine the user or computer name", login problems, things like that. I believe those problems are related to the DNS entry that was changed.

Web pages come up fine.

Workstations are XP and W2K configured with static IP addresses.

I'm thinking there is a way to globally fix this without going back and reconfiguring all the workstations individually.

I've looked at lookup zones and forwarders but being the lazy bloke I am I thought I might find a brighter bulb here.

Thanks for reading.

CK

 

[Claudek]

Your logon issues will go away as you have already noted before by changing the DNS ip address of all workstations to the internal Ip address - this is because the srv records are queried as to which server to go, to authenticate.
The web issues can be fixed as well (provided your website has a static ip address)

Have a look at

http://www.tek-tips.com/viewthread.cfm?SQID=624853&SPID=96&newpid=96&page=1

note that in the above, an A record called

http://www should

work as well as a Cname record.





Claudius (What certifications??)

http://www.iteq.com.au

 

[ricpinto]

use netsh in a batch file, include also the changes in the hosts file and run it on their login script.

You can also consider using DHCP, it's a nightmare administering static ips.

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/netsh.mspx

http://www.is-it-true.org/nt/nt2000/utips/utips46.shtml