Forum Discussion
No Internet Accesss issues across AVD
jmann3627 Did you ever get to the bottom of this issue, we seem to be getting it randomly also.
Thanks
gjone92 We've not come up with a permanent solution, but we have found that configuring the Network Card with a Static IP Address temporarily does resolve the issue without a restart. However this isn't a recommended solution. We have also been advised to try restarting the "DHCP Client" Service on the Virtual Machine but this is yet to be tested. Please let me know if you test this and it resolves.
- gjone92Jan 18, 2023Copper ContributorConfiguring Network card with a static IP has worked for me this morning also. But doing a restart of the DHCP Client service did nothing.
- KevHalJan 20, 2023Iron Contributor
This particular client is still facing this issue randomly, can go for a few days and its fine, then will get a machine that thinks it has no Internet.
Testing the Static IP of the machine and see if it improves.
- gjone92Jan 17, 2023Copper Contributor
KevHal did you get anywhere with the issue by any chance?
jmann3627 I have logged this with MS and currently working with them, but at the moment doesn't matter what we do the fix seems to last a week at most then the problem is back.
Do you have any Host Pools that are using AutoScale by any chance and then a pool that doesn't? What we seem to notice is that the pool that doesn't use Autoscale never seems to have the issue.
- jmann3627Jan 20, 2023Copper ContributorWe're using Scaling Plans for all our environments, so I can't help there unfortunately. Interesting to know that configuring the Interface with a Static IP works for you also. Have you notified Microsoft of this? Makes me think it's a DHCP Lease issue from the Azure Backend? Appreciate the update on the DHCP Client service, will scrap that from my testing plan!
- gjone92Jan 23, 2023Copper ContributorI have informed MS of this, and they got me to run some logging tool today seems to be looking more into NET NCSI more than anything this though. But I have a feeling its something to do with Azure's DHCP.
One thing I noticed last week was this issue happened on one of the VM's but that VM was not in our DC's DNS? But all the other VM's were... which seems to be a little odd. This morning i have set all NIC's of the Pools to be static also see if I get any issues this week.
Will update you if MS finds anything and anything from my further testing.