cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
701
Views
0
Helpful
6
Replies

Is a DNS issue??

msallemmaroon
Level 1
Level 1

hello,

I have an issue with forms.office.com, it's not loading all its content.

We have two dns server in the head office, a primary (192.168.0.5) and an alternative (192.168.0.6). everything works fine in the HO with the users, also in each branch we have a dns server (192.168.x.x) and the alternative is (192.168.0.5) and the link above works fine.

we faces issue in the small branches where there is no a dhcp server nor a dns server. we configure a dhcp server on a master  ap and we set the dns server as follow (192.168.0.5) on the aruba ap.
the forms.office.com, does not fully load, unless I set a static primary dns server ip : 8.8.8.8 on each pc and an alternative ip:192.168.0.5, if i set google's dns server as an alternative the page won't load.

advise,

Thank you.

6 Replies 6

ammahend
VIP Alumni
VIP Alumni

start with basics, are you able to reach 192.168.0.5 from small branches, can you ping it ? when you type "nslookup 192.168.0.5" on your windows command prompt, are you able to resolve the URL

-hope this helps-

@msallemmaroon 

Does this form page use information from different web server? There are links to other URL? 

msallemmaroon
Level 1
Level 1

hello, yes it is pingable and can resolve the dns name using nslookup

msallemmaroon_0-1736435457247.png

 


@Flavio Miranda content needs to be download from cdn.forms.office.net and from forms.office.com

@msallemmaroon  HTTP error 401 is unauthorized. It seems application problem. 

but why it is working properly when we're loading the page in other branches or at the head office using the same user (same privileges')

I can only guess as I dont know your infrastructure. It could be related to IP range for example. If you have some security tool or if the application have some security feature that have white list IP address and this branch was not added to the list. 

 The problem does not seems to be related to routing or DNS. Otherwise, the HTTP error would be something else or you would not receive any HTTP error.