Windows Server 2000/2003 Thread, Computers not recognising domain in Technical; Originally Posted by TechSupp
Meant to put Laserblazer!!!!
Not to worry - just made me laugh is all...
11th November 2009, 04:47 PM #16
11th November 2009, 05:12 PM #17
I have a couple that do it as well. Putting the whole domain name in, eg: school.local rather than just SCHOOL does seem to stop it happening quite so often but I have never found a solution. Different machines, different locations, different switches.
Sometimes if I move a computer - making sure it is properly switched off first - the same thing happens.
I wish I could get to the bottom of it.
11th November 2009, 05:42 PM #18
because school.local as apposed to school stops it from happening as often if you do an nslookup on school.local versus just school are there any differences ?
Originally Posted by witch
Also wondering if there is a GPO setting somewhere thats been missed or could be configured ?
Not tried this as not got a server setup at home or ought like that but instead of trying to enter in the name of the server ( whether or not its the FQDN or not ) if you use the IP Address of the server instead ( not sure if thats a viable option or not ) ???
Last edited by mac_shinobi; 11th November 2009 at 05:54 PM.
11th November 2009, 06:11 PM #19
I thought it might be using the short domain name but it doesn't make any difference here. In fact when the domain welcome message pops up the domain name automatically changes to its long version ie. domain.local. Tomorrow, I'm going to try renaming the computer that keeps doing it and see what happens.
12th November 2009, 08:03 AM #20
I've renamed the most persistent offender but I noticed the last username had been entered incorrectly, so it wouldn't have logged on. There's isn't an obscure server 2003 function that locks out a computer after so many invalid logins?
12th November 2009, 08:11 AM #21
There is a utility which afaik is apart of the 2003 resource kit
Originally Posted by laserblazer
Lockoutstatus.exe: Account Lockout Status (documented in Readme.htm)
Think the above one is the one I am thinking of - this should be able to assist and let you know if its locked out or not.
Not sure what settings are required to do or set the amount of login attempts that are a maximum amount of login attempts that are allowed - would be good to find out / know though.
Am guessing it may be something to do with group policy in the security section ?? * SHRUGS *
12th November 2009, 08:14 AM #22
No, no differences between school and school.local - and it doesnt always stop it happening, or rather, some machines with the problem have school.local already.
Originally Posted by mac_shinobi
Got a new server over the summer running Server 2008 so the whole lot is new - but still got the problem! If anyone knows of a GPO setting, I would be grateful.
By CyberNerd in forum *nix
Last Post: 10th February 2010, 12:48 PM
By Ben-BSH in forum Windows Server 2000/2003
Last Post: 5th November 2009, 10:53 AM
By enjay in forum Hardware
Last Post: 16th November 2007, 03:26 PM
By Blind in forum Windows
Last Post: 2nd August 2007, 10:42 PM
By BKGarry in forum Wireless Networks
Last Post: 30th March 2006, 05:47 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)