neilherbertuk

Hi Phillip, I've been having this issue on some new windows 7 ent laptops recently. After some research I came to the same conclusion as you with the TabletInputService but as you have too, found it wasn't. This issue is to do with Windows Search Service getting corrupt. By default the Windows Search Service doesn't index the AppData folder, I've found that it gets corrupt (I have some idea to how it's getting corrupt for us) and starts to index that folder. It's an easy fix, though perhaps time consuming if you've got alot of machines doing this: Go to "Turn Windows Features on or off" from Programs and Features in the control panel. Untick the Windows Search feature and press ok. Reboot Delete the profiles you are having issues with. Repeat the process but re-tick Windows Search to reinstall the feature. Perhaps slightly unrelated but we came across this with when setting up new laptops for our staff. I've seen this happen alot when you add a domain account as a local admin before you've let the account login and cache. For our laptop users we give them local admin rights. We ran into this problem when someone in our office started to add their permissions before caching the account. Neil

Ok a quick update. Thank you for everyones help and all the suggestions. I've just attemped the NIC uninstall and re-install on the sqlserver to find that didn't correct the problem. Just before I did this on the mailserver I ran a command mac_shinobi suggested to me in a PM netsh winsock reset catalog but hadn't checked if it had worked as it said to reboot. I've just run the command on our sqlserver to find instantly that it could ping any hostname!

It seems to have worked. It's rebooted and the Exchange Management console will now load. Before it just came up with an initalisation error. All the services related to exchange seem to have started too. I've just loaded up my outlook and it works too Thank you so much for your advice and help. Uninstalling and Reinstalling on the mailserver did the trick and reset everything ip related. Need to try this on the sql server now.

Setting the primary dns to the 2003 server (x.x.128.252) didn't make a difference.

I've uninstalled and reinstalled the NIC and it seems to be able to ping itself and any hostname I throw at it. We will see what happens after a reboot.

I'll give that ago too achandler. Again will have to do it locally will let you know if it changes anything.

I've removed ipv4 and reinstalled it on the mailserver with no change to the issue.

Bare with me sukh, I will have to do that locally. IPv6 is disabled. It's disabled across the entire network. Saying that if you ping the mailserver from the win2k8 dc it shows an ipv6 address rather than ipv4 which is very very odd...

ok nslookup C:\Users\administrator.DOMAIN>nslookup Default Server: UnKnown Address: x.x.128.251 > mailserver Server: UnKnown Address: x.x.128.251 *** UnKnown can't find mailserver: No response from server > domaincontroller Server: UnKnown Address: x.x.128.251 *** UnKnown can't find domaincontroller: No response from server > I've made a few changes to save erm, embarisment lol. The ip x.x.128.251 is the ip for domaincontroller (thats the new secondary server, its using the same name and ip as the dc that crashed) Using telnet Connecting To x.x.128.251...Could not open connection to the host, on port 53. The requested service provider could not be loaded or initialized. Windows Firewall on both DCs are turned off...

Sorry sukh, didn't see your reply. 1) Not getting a 2080 error (though the specialist who has been looking did clear the logs about half hour ago) 2) As I get an initalisation error when loading the Exchange Console I can only tell you its Exchange 2010 4) I reset the tcp/ip stack using the netsh command "netsh int ip reset" 5) Yes the dns ip addresses are manually set. ipconfig /all does show the correct settings. As for 3 not sure how to do that. My boss who should know how to do that is on holiday! So by myself! As for enviroment its windows 2008 r2 standard with sp1

Yes DNS is set correctly but it can not ping any hostname at all! I've just put one of the servers onto dhcp to see if it could resolve anything without luck.

Hi Achandler Yes we can ping IP addresses without an issue it's purely down to hostname resolution / dns. Like our Exchange server won't come back online as the Active Directory Topology service wont start. In the eventlog it lists the 2 domain controllers but says it cant find them. Same as websites, it cant resolve domain names. Yet you can connect to the mailserver using it's hostname from another computer (rdp) and get the owa login box through the browser. I haven't yet tried an sfc but that will be on the cards shortly. Neil

That is an option but I really would like to keep that as a last resort!

Hello all, Got a rather puzzling and urgent issue. On Wednesday night we had a powercut which took out our Primary Domain Controller (win2k8r2). We're back up and running on the secondary server (now primary) running server 2003. We also have a new win 2k8 r2 server back up with the same configuration as before but this has for now been left as a secondary dc. It has the exact same setup as before. We have a fair few servers but we are only having issues with 2 of them, both running win 2k8 r2, one running our SQL server and the other our Exchange 2010 server. Both of these servers have gone mad and can't resolve any hostnames including it's own or even localhost! On the exchange server I've tried to reset the TCP/IP stack and had a specialist looking at it too. Under nslookup it says Default Server: Unknown. Because of the hostname resolution issues the servers cant talk to AD or the internet which is obviously stopping both sql and exchange from starting back up. Wondered if anyone else had come across this and might help point us in the right direction? Neil

Are you importing the master certificate? I've been playing with iTalc 2 for some time now. When I found the program I set it up and had similar issues. This to me sounds like your not issuing the certificates properly. As far as I have found you need to generate an Administrator certificate to be able to take full control of a system. In each of our IT Suites I have setup a Teacher and Administrator Certificate which seems to give me full access using the administrator certificate on my workstation. Neil

I've seen a few posts about this but relating to Moodle rather than Sharepoint. We have a Sharepoint VLE (with Talmos) and SIMS. All Staff and Students are issued with an active directory account which we generate rather than using the SIMS AD Provisioning. This is for account naming standards (using staff initials as logins and 12SurFir for Students). To get our Talmos and SIMS to link up for timetabling and such we have to consolidate (SLG - SIMS AD Provisioning) accounts which gets done via the Capita SIMS Web Parts. As far as I am aware each account has to be consolidated manually by going to the Capita SIMS Web Parts and using the Consolidate function. I'm really keen to know if theres anything like a scripts or such that can handle the consolidation for us? If not do you know roughly what happens in the backend during this consolidation that might help me write something myself?

Hi Nick, It sounds like you're having the same issue we've been having. The netbooks would like yours say limited connectivity, they wouldn't get IP addresses. The moment I turned Spanning Tree Protocol off on our Management Switches the netbooks instantly received IP addresses. I turned it off on both of our switches. We do get the odd machine here and there still having the issue but we're no longer getting an entire class (30+ Netbooks) unable to connect. Neil

No, nothing has been done recently. We installed a couple of extra APs (which have newer firmware) back over Easter but the issues have appeared long after they went in! I think I've figured out the problem anyway. I've disasbled Spanning Tree Protocol on the Management Switch and instantly the netbooks that had the issue managed to get IP addresses

Hello All, I'm really, really struggling with this issue and wondered if anyone could point me in the right direction. We have 2 D-Link DWS-3024L Wireless Management Switches. Between these 2 switches we have 39 D-Link DWL-3500APs. Each AP broadcasts 2 networks. The past few months I've been getting more and more reports of wireless clients not being able contact DHCP to get an IP address. I'll get an entire class of 30 netbooks all unable to get ip addresses. The only solution seems to be to reboot the switches, which reboots the APs. I'm now having to reboot these every couple of days! It's driving me mad and causing a fair bit of disruption when it happens as we have a fair number of netbooks and staff laptops. Any thoughts or ideas for where to start looking would be really appreciated! N