Windows Server 2000/2003 Thread, Server not accessible error in Technical; Having a very similar problem as reported here but thought i'd post this in the correct forum
We're running Server ...
8th April 2009, 06:41 PM #1
Server not accessible error
Having a very similar problem as reported here but thought i'd post this in the correct forum
We're running Server 2003 R2, xp clients.
Some machines are fine, can do everything as normal, others have no internet, can't remote desktop to servers, and get the message "Naming information cannot be located for the following reason; the server is not operational." when connecting to active directory.
They can all ping the servers and can see shares on the network but can't run ad, or access internet.
Does anyone know why this is happening? I have restarted servers/clients multiple times and still having problems!
Run dcdiag and netdiag and there are no problems there. Event logs on both clients and servers are clean (no recent errors or warnings)
Have removed clients from the domain, then re-added them and still not working!
I'm supposed to be off for the next week but figure if someone knows what causes this then i might have to pop in and see if it fixes it.
Any help/advice would be very very gratefully received!
8th April 2009, 08:43 PM #2
Are the affected clients getting the correct DNS server addresses and the correct default gateway?
8th April 2009, 08:45 PM #3
Yeah, getting correct dns and gateway info. Can ping the proxy server and the dns server no problems.
8th April 2009, 09:14 PM #4
Try removing a workstation from the domain (set it to workgroup), reboot, then re-join the domain and reboot again. Does this help?
If it does, it would point to a possible computer object corruption within Active Directory.
8th April 2009, 09:16 PM #5
Sorry, forgot to mention i have tried this. We were renaming lots of machines today and one of the things i tried was re-syspreping it to see if that helped but no luck
Originally Posted by Michael
8th April 2009, 09:30 PM #6
On a problematic machine, if you open a command prompt and enter ipconfig /all are all the entries correct?
Especially DNS entries. Your primary DNS should be your primary domain controller, you may have a secondary DNS server and then you should have external DNS servers listed.
8th April 2009, 09:33 PM #7
Yup, all entries are correct....
Originally Posted by Michael
we only have one DNS server so that is first, then we have an external dns (bgfl dns server)
Thanks for your help so far.
8th April 2009, 09:49 PM #8
Ok, lets focus on more basic problems such as proxy settings. Seeing as you're a Birmingham/BGFL school, it makes sense to configure proxy settings on the Default Domain Policy.
Normally I wouldn't touch the Default Domain Policy, but for exceptions like this it makes sense. Once you've made this change (on the server), could you then verify where the computer objects are within your OU structure?
As a general recommendation, creating an OU called Curriculum and then sub OUs, such as 'Pupils', 'Classroom PCs' and 'ICT Suite' (for example). Make sure the computer objects are located under Classroom PCs or ICT Suite using my example.
On the workstation, from the Run menu perform: gpupdate /force then reboot (you should be prompted to).
One question I forgot to ask previously, is your workstations are running XP, but are they running SP2 or SP3?
8th April 2009, 10:03 PM #9
They're running SP3.
The machines have been working fine in the past (been set up for a year), this has just come out of the blue.
Ran gpupdate and they do pick up the policies and reboot.
8th April 2009, 10:30 PM #10
How do you access Active Directory on your workstations? Do you use either the MMC or the 2003 Server Administration Tools?
8th April 2009, 10:34 PM #11
8th April 2009, 10:39 PM #12
And if you try using MMC - Start > Run > MMC > File > Add/Remove Snap-in > Add > Group Policy Object Editor > Add > Browse
You should see all your domain GPOs listed here. Does this work OK?
9th April 2009, 11:33 AM #13
- Rep Power
Adding an external DNS does seem just a little strange. If your machines always pick the secondary, the external Resolver won't know anything about your internal arrangements, and the look-up will fail. Try removing the external DNS Resolver from your list, and just run with the internal one.
(Your internal DNS should resolve all external requesst for you - it's the only one that should reference external DNS)
Last edited by 7andY; 9th April 2009 at 11:36 AM.
9th April 2009, 11:43 AM #14
It's perfectly normal to set an external resolver. It all depends how your network is setup, but without it, internet connectivity would fail.
It means workstations connect directly to the DNS servers which handle external requests (in this case web pages), which would cut down on the number of requests your local DNS server has to handle, as well as all other roles such as Active Directory, DHCP, File Server, Print Server, IIS etc etc
9th April 2009, 11:57 AM #15
Stab in the dark...have you checked the DNS records to see if any are out of sync?
Had something simular a while back when DHCP had assigned a new IP address and DNS had not caught up.
By Strotzyl in forum Wireless Networks
Last Post: 14th March 2009, 03:46 PM
By SimpleSi in forum EduGeek.net Site Problems
Last Post: 11th June 2008, 04:24 PM
By CyberNerd in forum MIS Systems
Last Post: 15th February 2008, 10:22 AM
By ICT_GUY in forum General Chat
Last Post: 30th October 2007, 11:26 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)