Azhibberd

Well its nice to get them.... But windows generally seems to get upset allot..... We managed it for about a month.... then it got upset about something that simply wasn't what i consider a problem, So generally its not too much of a problem as long as everything is working and that its nothing critical thats giving you errors or replication errors....

Not Personally had this issue, Sure its not something weird with a firewall blocking the ping? Try turning off the firewall on the client and server see if you get the problem then?

can they see and access the area that all the short-cuts are pointing to? Tried clearing the users profile?

Just been playing for abit and one machine we had working fine, with the machine next to it (on the same switch and vlan) refusing to see anything not on the same vlan could ping machines on its vlan and nothing outside its vlan, then 5 minutes later the one that was fine has stopped being able to see anything not on its vlan, Hence i'm guessings its not dns related, looked at the logs on the switch there on doesn't seem to be any problems... And well its not just that switch its happening on, Anyone got any bright ideas i should be looking at? Think next step is wait till end of the day and restart the core switch.. ? **Looks like it was something really odd going on with the core switch, As a restart off that seems to have resolved the issues, Although we shall find out tomorrow**

Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\STUDENT-SERVER Starting test: Connectivity ......................... STUDENT-SERVER passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\STUDENT-SERVER Starting test: Replications ......................... STUDENT-SERVER passed test Replications Starting test: NCSecDesc ......................... STUDENT-SERVER passed test NCSecDesc Starting test: NetLogons ......................... STUDENT-SERVER passed test NetLogons Starting test: Advertising ......................... STUDENT-SERVER passed test Advertising Starting test: KnowsOfRoleHolders ......................... STUDENT-SERVER passed test KnowsOfRoleHolders Starting test: RidManager ......................... STUDENT-SERVER passed test RidManager Starting test: MachineAccount ......................... STUDENT-SERVER passed test MachineAccount Starting test: Services ......................... STUDENT-SERVER passed test Services Starting test: ObjectsReplicated ......................... STUDENT-SERVER passed test ObjectsReplicated Starting test: frssysvol ......................... STUDENT-SERVER passed test frssysvol Starting test: frsevent ......................... STUDENT-SERVER passed test frsevent Starting test: kccevent ......................... STUDENT-SERVER passed test kccevent Starting test: systemlog ......................... STUDENT-SERVER passed test systemlog Starting test: VerifyReferences ......................... STUDENT-SERVER passed test VerifyReferences Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : nsnet Starting test: CrossRefValidation ......................... nsnet passed test CrossRefValidation Starting test: CheckSDRefDom ......................... nsnet passed test CheckSDRefDom Running enterprise tests on : nsnet.net Starting test: Intersite ......................... nsnet.net passed test Intersite Starting test: FsmoCheck ......................... nsnet.net passed test FsmoCheck 2 DC's give that... One is giving an error about systemlog Just to add something i noticed odd... on one of the clients that isn't playing ball i ran nslookup and i get Default Server: Unknown Address: 172.16.0.10 > student-server Server: Unknown Address 172.16.0.10 Name: Student-server.nsnet.net Address: 172.16.0.10

Hey guys, Sorry i'm getting a sore head from this one.... So here goes... Server that does DHCP decided to crash out monday night, So came in tuesday restarted it, wasn't giving out ip addresses, Turned off the old wds that was on it, then bound the ip address so it could then give out ip addresses, then everywhere is getting IP addresses again... but now some machines are getting a usable dns and some arn't, We have 2 dns servers both seem to be happy(Can use nslookup on both of them and seems to resolve fine) Some of the machines (Doesn't seem to be a pattern what so ever) and when i say some we have 3 IT rooms that have 30 machines each that are doing as they should, where as some of them only get 3 working out of the 30(Whose that arn't working are receiving "there are currently no logon servers available to service the logon request") Now doing dcdiag /test:DNS does give me: C:\Program Files\Support Tools>dcdiag /test:dns Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\STAFF-SERVER Starting test: Connectivity ......................... STAFF-SERVER passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\STAFF-SERVER DNS Tests are running and not hung. Please wait a few minutes... Running partition tests on : DomainDnsZones Running partition tests on : ForestDnsZones Running partition tests on : Schema Running partition tests on : Configuration Running partition tests on : nsnet Running enterprise tests on : nsnet.net Starting test: DNS Test results for domain controllers: DC: Staff-Server.nsnet.net Domain: nsnet.net TEST: Forwarders/Root hints (Forw) Error: Root hints list has invalid root hint server: a.root-se rvers.net. (198.41.0.4) Error: Root hints list has invalid root hint server: b.root-se rvers.net. (192.228.79.201) Error: Root hints list has invalid root hint server: c.root-se rvers.net. (192.33.4.12) Error: Root hints list has invalid root hint server: d.root-se rvers.net. (128.8.10.90) Error: Root hints list has invalid root hint server: e.root-se rvers.net. (192.203.230.10) Error: Root hints list has invalid root hint server: f.root-se rvers.net. (192.5.5.241) Error: Root hints list has invalid root hint server: g.root-se rvers.net. (192.112.36.4) Error: Root hints list has invalid root hint server: h.root-se rvers.net. (128.63.2.53) Error: Root hints list has invalid root hint server: i.root-se rvers.net. (192.36.148.17) Error: Root hints list has invalid root hint server: j.root-se rvers.net. (192.58.128.30) Error: Root hints list has invalid root hint server: k.root-se rvers.net. (193.0.14.129) Error: Root hints list has invalid root hint server: l.root-se rvers.net. (199.7.83.42) Error: Root hints list has invalid root hint server: m.root-se rvers.net. (202.12.27.33) TEST: Dynamic update (Dyn) Warning: Dynamic update is enabled on the zone but not secure nsnet.net. Summary of test results for DNS servers used by the above domain contro llers: DNS server: 128.63.2.53 (h.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 128.63.2.53 DNS server: 128.8.10.90 (d.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 128.8.10.90 DNS server: 192.112.36.4 (g.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 192.112.36.4 DNS server: 192.203.230.10 (e.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 192.203.230.10 DNS server: 192.228.79.201 (b.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 192.228.79.201 DNS server: 192.33.4.12 (c.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 192.33.4.12 DNS server: 192.36.148.17 (i.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 192.36.148.17 DNS server: 192.5.5.241 (f.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 192.5.5.241 DNS server: 192.58.128.30 (j.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 192.58.128.30 DNS server: 193.0.14.129 (k.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 193.0.14.129 DNS server: 198.41.0.4 (a.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 198.41.0.4 DNS server: 199.7.83.42 (l.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 199.7.83.42 DNS server: 202.12.27.33 (m.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.12 7.in-addr.arpa. failed on the DNS server 202.12.27.33 Summary of DNS test results: Auth Basc Forw Del Dyn RReg Ext ________________________________________________________________ Domain: nsnet.net Staff-Server PASS PASS FAIL PASS WARN PASS n/a ......................... nsnet.net failed test DNS Now i'm not exactly sure where to go from here.... Any help would be much appreciated!

Any chance its a firewall installed somewhere that you haven't noticed? Or something like a norton trial firewall installed that ran out of trial(half removed?) and still haunts this machine (I've had that before where it wasn't in add/remove etc, not in programs and not in processes, had to get hold of the advanced norton uninstalled? Maybe try a live cd just to check hardware is all happy etc... then you know your deffo looking at a software problem?

I've done the simple, Please insert cheese... added with a shortcut to facebook.com on the students desktop which actually goes to http://www.oldheatonian.co.uk/testwp/wp-content/uploads/2009/05/facebook1.jpg As facebook is blocked here i'm interested to know how many hits it will get

Never bumped into it before... Although i'm not sure if i'm being stupid when i ask... Whats wrong with just using MSI's to publish applications ?

Another vote for the software restriction policy... GPO > User > windows > Security > Software restriction policies - We by default have it set to disallowed, Then have additional rules added for what we want to run... That way only allowed applications are allowed.. And you can simply choose not to add those to your list... Although just remember if you have multiple dc's the netlogon area will have to be allowed for each dc for logon scripts

HAve to say first time i've realised with started you can't change your desktop... Thats a really odd one to me :S But hey ho..... I think its a case of most people will live without it... if not they would find the 'ways around it'... When any businesses etc will be using pro anyway to be able to join a domain

Well you said you used the same domain name as the 2003 server... So they would have been the same domain... Although i'm presuming you promoted the 2008R2 to a DC.... Which is normal.... although you should have adprep /forestprep and adprep /domainprep to atleast upgrade the schema

Have you tried installing the software for it... least see if it works i mean mine i bought a year ago has it... so its not exactly new

If Adobe reader 4 was installed with a msi... you could use a script to do msiexec /uninstall

How about the good old GPO: Computer Configuration\Administrative Templates\System\Logon\ "Always wait for the network at computer startup and logon"