Forum Discussion
Solved
Surface Hubs not Pingable / Not pulling meetings or accounts from GAL
Hey all, A couple of issues that have popped up for us the during the last week. We got reports that 3 of our Hubs are showing the following issues: Scheduled meetings are not showing on the We...
- Hi Josh
My testing says that Surface Hubs don't respond to ping requests (although our internal DNS does resolve the device name to the IP correctly). So pinging to determine network status is a no go.
All of the symptoms you've described would be for one of the two following reasons:
- Either the device account is locked/password expired
- The Surface Hub has no internet access
So, firstly check the device account in AD (or AAD if online) and ensure that the password hasn't expired, and the account isn't locked. If you have a policy to expire passwords after a set number of days, remember to enable the setting to allow the Surface Hub to rotate the password automatically.
Regarding internet access, you can check the general status under Settings > Network & Internet. Assuming you're plugged into ethernet, it'll show as Connected if the Surface Hub believes it has internet access. You can easily test this by going to Edge and just trying to access a webpage.
If you have a proxy server, also check your proxy settings on the Surface Hub and authentication methods to make sure it can access the internet successfully.
If all that fails, I'd double check your firewall port/IP range permissions to make sure nothing is being blocked that the Surface Hub needs. You can find more information on these ranges here: https://docs.microsoft.com/en-gb/surface-hub/prepare-your-environment-for-surface-hub
Thanks
D
Hi Josh
My testing says that Surface Hubs don't respond to ping requests (although our internal DNS does resolve the device name to the IP correctly). So pinging to determine network status is a no go.
All of the symptoms you've described would be for one of the two following reasons:
- Either the device account is locked/password expired
- The Surface Hub has no internet access
So, firstly check the device account in AD (or AAD if online) and ensure that the password hasn't expired, and the account isn't locked. If you have a policy to expire passwords after a set number of days, remember to enable the setting to allow the Surface Hub to rotate the password automatically.
Regarding internet access, you can check the general status under Settings > Network & Internet. Assuming you're plugged into ethernet, it'll show as Connected if the Surface Hub believes it has internet access. You can easily test this by going to Edge and just trying to access a webpage.
If you have a proxy server, also check your proxy settings on the Surface Hub and authentication methods to make sure it can access the internet successfully.
If all that fails, I'd double check your firewall port/IP range permissions to make sure nothing is being blocked that the Surface Hub needs. You can find more information on these ranges here: https://docs.microsoft.com/en-gb/surface-hub/prepare-your-environment-for-surface-hub
Thanks
D
My testing says that Surface Hubs don't respond to ping requests (although our internal DNS does resolve the device name to the IP correctly). So pinging to determine network status is a no go.
All of the symptoms you've described would be for one of the two following reasons:
- Either the device account is locked/password expired
- The Surface Hub has no internet access
So, firstly check the device account in AD (or AAD if online) and ensure that the password hasn't expired, and the account isn't locked. If you have a policy to expire passwords after a set number of days, remember to enable the setting to allow the Surface Hub to rotate the password automatically.
Regarding internet access, you can check the general status under Settings > Network & Internet. Assuming you're plugged into ethernet, it'll show as Connected if the Surface Hub believes it has internet access. You can easily test this by going to Edge and just trying to access a webpage.
If you have a proxy server, also check your proxy settings on the Surface Hub and authentication methods to make sure it can access the internet successfully.
If all that fails, I'd double check your firewall port/IP range permissions to make sure nothing is being blocked that the Surface Hub needs. You can find more information on these ranges here: https://docs.microsoft.com/en-gb/surface-hub/prepare-your-environment-for-surface-hub
Thanks
D