Team,
You have done great job with the product and Thank you for the same.
We recently upgraded Xibo CMS and Client from 1.6.4 to 1.7.3 version and most of the components are working well except below issue.
We have an application X and which is internally calling applet server Y without FQDN name for Y. We have configured Application X on design Layout and assigned to the Display. Application X is coming up fine, but the content which needs to be displayed by applet server Y is not visible due to the fact that it does not have FQDN.
Same settings were working with Xibo 1.6.4 version, but not with new version 1.7.4.
Can you please provide help us with the solution, if any.
Thanks,
Anil
A few questoins:
Was/is application X calling Server Y via IP address?
Also is it not possible to change the application to call on Server Y with a FQDN and assign Server Y a FQDN?
What errors if any are you receiving?
What operating systems are you using?
Thank you for the response.
Here are my answers
Was/is application X calling Server Y via IP address?
Nope. It is calling by hostname without FQDN
Also is it not possible to change the application to call on Server Y with a FQDN and assign Server Y a FQDN?
This will impact services which are used by other applications and required production changes which is not seems to be correct solution.
What errors if any are you receiving?
We are getting blank page and XIBO Client, but on IE or Firefox, it is giving an error “Remote Server Address not found”, But we were able to fix that as workaround by adding the domain names on LAN DNS entries tab.
This changes not reflecting on XIBO Client.
What operating systems are you using?
Xibo Client is on Win7 and CMS is on Win 2012 Server
hope this helps to provide some insight on the resolution.
Thanks,
Anil
Yes the answers help.
So I if I understand correctly, you are trying to connect to the CMS server with just the server name?
What on your network is handling the DNS of the local network?
You may try adding a domain name into your router. Some routers have this option and may help if Server 2012 is not handling your DNS. You could also try enabling net Bios over TCP/IP.
If you are using the Server 2012 DNS Server are you running a domain on the network and if so is the client machine joined to the domain?
Thank you for your response.
Here are my answers.
So I if I understand correctly, you are trying to connect to the CMS server with just the server name?
It is not an issue with CMS server as we are using specific URL on the layout to initiate the connection on the Xibo Client machine directly.
x.y.com is configured on layout design and assigned to display. when it invokes x.y.com, it is displaying portion of the x.y.com content hosted on particular server.
But, the problem is x.y.com is having some applet/flash kind of server in it which call a.b.com server internally and that server content portion is not displaying on the Xibo Client.
So, Actual configuration is x.y.com which a.b.com internally and a.b.com portion is not displaying.
Same URL (x.y.com calling a.b.com) works on the browser of the same machine without any issue.
Hope this clarifies or at least not confused 
What on your network is handling the DNS of the local network?
We tried both with auto DNS and manual entries, but didn’t help
You may try adding a domain name into your router. Some routers have this option and may help if Server 2012 is not handling your DNS. You could also try enabling net Bios over TCP/IP.
We tried both with auto DNS and manual entries, but didn’t help
If you are using the Server 2012 DNS Server are you running a domain on the network and if so is the client machine joined to the domain?
Yes, both CMS and Client machines are on the same domain and subnet.
Please let me know, if you need more information.
Thanks,
Anil
sayaanil,
I will try to wrap my head around the first part in a bit. ( An external site calls a local network resource? , If so do you mind sharing the code of how the external site is calling the internal resource?)
I am still confused on what device or computer on the local network is handling your DNS request. Maybe you could tell me what is handling the DHCP on your network? It is more than likely the same device that is handling your local DNS.
I will try to wrap my head around the first part in a bit. ( An external site calls a local network resource? , If so do you mind sharing the code of how the external site is calling the internal resource?)
No. Both are internal sites. Same configuration was working with 1.6.4 with IE8
I am still confused on what device or computer on the local network is handling your DNS request. Maybe you could tell me what is handling the DHCP on your network? It is more than likely the same device that is handling your local DNS.
Xibo Client installed Windows 7 with IE11. Same configuration was working with 1.6.4 with IE8
Thanks,
Anil
sayaanil,
So with both machines being on the internal network, again it would point to a DNS configuration issue.
I have asked twice, what is handling the DNS on your network and have not gotten an answer as to what is handling the DNS. It would be much more benifical in allowing others to help you if you can provide the information needed.
I do understand that the problem you are experiencing did not exist on a previous install of Xibo. However, I do not think the problem is Xibo related. I think there is something different somehow in the configuration of the machines. Until we can rule out a DNS problem, I do not see how the problem can get resolved.
Sorry if a sound a bit rude, I am not trying to be. You do understand what I am asking for when I ask what is handling the DNS on your network, correct?
Sorry to confuse you and I know it is bit tricky to make you understand based on the scenario what we are facing.
Can you please clarify on the question “what is handling the DNS on your network?” more specifically.
Only recent change, we have done is Xibo upgrade from 1.6.4 to 1.7.3 and that is where we are suspecting, but definitely something else and not sure.
Thanks,
Anil
sayaanil,
Ok… I will try to explain this a bit for you.
On a network everything has an address, an IP address. When you want to communicate with another machine, to make it easier to remember machines are also given names. When you want to communicate with another machine you utilize the machine name, such as “server1”. So when you want to access “server1” from another machine the network does not know who “server1” is or what the IP address of the machine is.
This is where DNS (Domain Name Server) comes in. When you want to communicate with “server1” the current machine must figure out where “server1” is. It does this by asking the DNS server if it knows “server1” and what it’s address is. The DNS server will respond with an IP address of “server1” to your current machine. Then your current machine will then talk to “server1” via the IP address.
Depending how simple or complexed your network is and also what devices and computers you have, there are a number of different things that could be handling the DNS queries. If your network is simple and you only have a few machines, your DNS is most likely handled by your network router.
Since you are asking for clarification, I am going to assume that this is how your network is setup. So, if you could please do the following on the Xibo Client machine (x.y.com) that is not bring up the desired data.
- Click on start
- In the search box type cmd
- Wait about 5 seconds and then hit enter. This will bring up a command prompt
- Type in “ipconfig /all” and press enter.
- Please post what is returned for your IP Address, Gateway, and both DNS Servers.
Also do this on the machine (a.b.com) that the Xibo client is supposed to be getting data from.