problem accessing the internet for some clients after microsoft updates.
we have a windows 2012 server v2 std edition running hyperv with 2 virtual machines. One is our domain controller and one is just a standard file server.
All has been working well till we installed some new updates over the weekend.
Now our file server and several of our clients can no longer access the internet. there are several strangely who still can.
On the domain controller, we find that the forwarders that point to our ISP dns and google for dns, can no longer resolve their IP addresses?? The other vm which is just a file server still can.
All local clients can access the shared folders on or DC.
Can anyone advise how we can go about diagnosing and fixing this problem?
Any assistance much appreciated.
Many thanks.
All has been working well till we installed some new updates over the weekend.
Now our file server and several of our clients can no longer access the internet. there are several strangely who still can.
On the domain controller, we find that the forwarders that point to our ISP dns and google for dns, can no longer resolve their IP addresses?? The other vm which is just a file server still can.
All local clients can access the shared folders on or DC.
Can anyone advise how we can go about diagnosing and fixing this problem?
Any assistance much appreciated.
Many thanks.
ASKER
unfortunately, our server cannot currently connect to the internet, so we cannot check for further updates.
i dont know if this is relevant, but we have had problems with other servers witn a .net update.
i notice that when i view the update history, i can see that kb4481484 a .net update is detailed as having been installed, but when i check add remove programs, this update is not listed so cant remove it.
any further suggestions?
thanks
i dont know if this is relevant, but we have had problems with other servers witn a .net update.
i notice that when i view the update history, i can see that kb4481484 a .net update is detailed as having been installed, but when i check add remove programs, this update is not listed so cant remove it.
any further suggestions?
thanks
See if you can get a date on the most recent updates.
Looking at my Windows 10 Pro machine:
Patch Tuesday Jan 8, 2019
.NET update Jan 23, 2019
Cumulative Update Jan 25, 2019.
The most recent update was Friday (3 days ago).
Looking at my Windows 10 Pro machine:
Patch Tuesday Jan 8, 2019
.NET update Jan 23, 2019
Cumulative Update Jan 25, 2019.
The most recent update was Friday (3 days ago).
ASKER
here are the detailsof the .net update.
ASKER
As I said earlier, I cannot find any trace of this when I investigate a possible removal. ie it is not detailed in the items installed.
This may not be at all relevant of course.
Should I remove all of the updates installed in the last batch?
screenshot.jpg
This may not be at all relevant of course.
Should I remove all of the updates installed in the last batch?
screenshot.jpg
On the one server 2012 I have here, that one is waiting for a server restart one evening this week. I will see what happens then.
ASKER
the updates that are listed as having been installed are 4480963, 4480064 and 4480054. No sign of the kb4481584 which is detailed in the update history??
Some of these in the list waiting to install here.
What do you mean? Is it just the domain names that are inaccessible? Can you ping 1.1.1.1? Can you ping a local IP address? If you can ping it, then it's just DNS. Check your DNS server. If you can't ping it, is your network adapter working?
ASKER
we can ping all internal IP's but not external ip's or names. This applies to our single domain controller, and probably 20 of our 30 client workstations. We also have an additional VM fileserver which works perfectly.
Would not expect it to be the network adapter as some work. NSLOOKUP finds everything OK on the DC and I can ping all of the servers including the DNS server. Cannot PING 1.1.1.1 OR 8.8.8.8 / 8.8.4.4, and as I said before the entries in our server forwarders cannot resolve either. These have been working OK for years, so I am ASSUMING it is related to the recent updates, but it may just be coincidence.
Thanks.
Would not expect it to be the network adapter as some work. NSLOOKUP finds everything OK on the DC and I can ping all of the servers including the DNS server. Cannot PING 1.1.1.1 OR 8.8.8.8 / 8.8.4.4, and as I said before the entries in our server forwarders cannot resolve either. These have been working OK for years, so I am ASSUMING it is related to the recent updates, but it may just be coincidence.
Thanks.
Hi. Back at a client and we updated a physical Server 2012 R2 - all critical updates including KB4481484 and KB4480963 and others. We restart and Internet and File Access are all normal.
1. Are there any network drivers on the Guest VM that you can update?
2. Have you tried finding more updates?
1. Are there any network drivers on the Guest VM that you can update?
2. Have you tried finding more updates?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Strange resolution as that (a) should have come to light prior to updates and (b) does not have anything to do with updates.
ASKER
it just goes to show how coincidence can lead you in the wrong direction! quite why this happened in the first place is beyond me, but the timing of the problem happening straight after updates, made that the prime suspect. clearly unrelated, but so random, which made it difficult to track. the problem only came to light once i had updated the firmware of our router, as the normal conflict warnings were completely absent.
ASKER
found own solution
Now our file server and several of our clients can no longer access the internet. there are several strangely who still can.
Some updates may still need to download and install. I would check this first.