The first is your IP addressing of your internal network may create an issue. Lets say you are using non-Routable addressing ([https://en.wikipedia.org/wiki/Private_network|Private Network]) internally and your PRIVA automation system which is in the boiler rm has a fixed IP address in the address block you are using. Now the network path between the boiler rm and your office needs to be checked out. Ideally, you have a direct connection (no routers or switches) to the hub your office PC is sitting on. If you can't achieve that then make sure you only have layer 2 switching (no routing) devices between the two systems. Now within your management PC create a host file with the IP address and the host name. So now the systems routing tables see's this connection as a direct connection (same IP subnet on a flat network).
Now lets move on... Your management PC in your office likely has a DHCP address assignment. Thats fine but you'll want to reserve the IP address within the DHCP server (if you want you can also do this with the boiler system). That way the DHCP server won't alter the settings which could have messed you up. Ref: [https://technet.microsoft.com/en-us/library/cc781008(v=ws.10).aspx|What Is DHCP]
Now the bully in the room! Windows its self has a name service WINS. I Like to say you WINS you lose! As I hate it! It always messes you up as the pecking order is WINS first then it will fall over to IP name services (Host & DNS). What can happen is the WINS DB can get corrupted and depending on what you assign your systems for names it can confuse the lookup. So what I do is use a different name for the Windows systems (for WINS) than the TC/IP name I assign for the same system as an example ' '''w'''acme-school.com' and 'acme-school.com' That way WINS is bypassed! Ref: [https://technet.microsoft.com/en-us/library/cc725802(v=ws.11).aspx|Windows Internet Name Service (WINS) Overview]
As to gaining access to the Internet from this system (outwards) your DHCP settings should be fine setting the nearest routers IP address as your gateway and DNS, then use the helper function within the router to forward the request to your DNS in-house (that is if you have one) and then the ISP's DNS.
As to the reverse, gaining access to the PRIVA automation system from the Internet. I would recommend you do this through a VPN tunnel so you can control who is gaining access to the system (either one) and I would recommend you limit access if you can to the office system only (not the system in the boiler rm). Then piggy back the connection over to the PRIVA automation system in the boiler rm. That way you have a second door before someone can gain access to the system (you never know these days...) and limit it to as few people as needed (don't forget to alter the passwords for everyone if someone leaves! and delete their systems account and VPN access as well).
As to how to monitor things... You'll need to setup an RMON probe to pole the systems (not to often now!) Then review its logs for what happened. Ref: [https://en.wikipedia.org/wiki/RMON|RMON]
-
Last piece here.. As you have multiple buildings one of the issue you can encounter is a ground loop. Review with your cabler the [http://blog.siemon.com/standards/category/tia/tia-607-b-generic-telecommunications-bonding-and-grounding-earthing-for-customer-premises|ANSI/TIA-607-B Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises] You may want to ask them if they have [https://www.bicsi.org|BICSI certified] people on their staff.
+
Last piece here.. As you have multiple buildings one of the issues you can encounter is a ground loop. Review with your cabler the [http://blog.siemon.com/standards/category/tia/tia-607-b-generic-telecommunications-bonding-and-grounding-earthing-for-customer-premises|ANSI/TIA-607-B Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises] You may want to ask them if they have [https://www.bicsi.org|BICSI certified] people on their staff. You may need to have a power meter probe setup across the buildings to monitor each buildings ground.
The first is your IP addressing of your internal network may create an issue. Lets say you are using non-Routable addressing ([https://en.wikipedia.org/wiki/Private_network|Private Network]) internally and your PRIVA automation system which is in the boiler rm has a fixed IP address in the address block you are using. Now the network path between the boiler rm and your office needs to be checked out. Ideally, you have a direct connection (no routers or switches) to the hub your office PC is sitting on. If you can't achieve that then make sure you only have layer 2 switching (no routing) devices between the two systems. Now within your management PC create a host file with the IP address and the host name. So now the systems routing tables see's this connection as a direct connection (same IP subnet on a flat network).
Now lets move on... Your management PC in your office likely has a DHCP address assignment. Thats fine but you'll want to reserve the IP address within the DHCP server (if you want you can also do this with the boiler system). That way the DHCP server won't alter the settings which could have messed you up. Ref: [https://technet.microsoft.com/en-us/library/cc781008(v=ws.10).aspx|What Is DHCP]
Now the bully in the room! Windows its self has a name service WINS. I Like to say you WINS you lose! As I hate it! It always messes you up as the pecking order is WINS first then it will fall over to IP name services (Host & DNS). What can happen is the WINS DB can get corrupted and depending on what you assign your systems for names it can confuse the lookup. So what I do is use a different name for the Windows systems (for WINS) than the TC/IP name I assign for the same system as an example ' '''w'''acme-school.com' and 'acme-school.com' That way WINS is bypassed! Ref: [https://technet.microsoft.com/en-us/library/cc725802(v=ws.11).aspx|Windows Internet Name Service (WINS) Overview]
As to gaining access to the Internet from this system (outwards) your DHCP settings should be fine setting the nearest routers IP address as your gateway and DNS, then use the helper function within the router to forward the request to your DNS in-house (that is if you have one) and then the ISP's DNS.
As to the reverse, gaining access to the PRIVA automation system from the Internet. I would recommend you do this through a VPN tunnel so you can control who is gaining access to the system (either one) and I would recommend you limit access if you can to the office system only (not the system in the boiler rm). Then piggy back the connection over to the PRIVA automation system in the boiler rm. That way you have a second door before someone can gain access to the system (you never know these days...) and limit it to as few people as needed (don't forget to alter the passwords for everyone if someone leaves! and delete their systems account and VPN access as well).
-
As to how to monitor things... You'll need to setup an RMON probe to pole the systems (not to often now!) Then review its logs for what happened.
+
As to how to monitor things... You'll need to setup an RMON probe to pole the systems (not to often now!) Then review its logs for what happened. Ref: [https://en.wikipedia.org/wiki/RMON|RMON]
Last piece here.. As you have multiple buildings one of the issue you can encounter is a ground loop. Review with your cabler the [http://blog.siemon.com/standards/category/tia/tia-607-b-generic-telecommunications-bonding-and-grounding-earthing-for-customer-premises|ANSI/TIA-607-B Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises] You may want to ask them if they have [https://www.bicsi.org|BICSI certified] people on their staff.
The first is your IP addressing of your internal network may create an issue. Lets say you are using non-Routable addressing ([https://en.wikipedia.org/wiki/Private_network|Private Network]) internally and your PRIVA automation system which is in the boiler rm has a fixed IP address in the address block you are using. Now the network path between the boiler rm and your office needs to be checked out. Ideally, you have a direct connection (no routers or switches) to the hub your office PC is sitting on. If you can't achieve that then make sure you only have layer 2 switching (no routing) devices between the two systems. Now within your management PC create a host file with the IP address and the host name. So now the systems routing tables see's this connection as a direct connection (same IP subnet on a flat network).
Now lets move on... Your management PC in your office likely has a DHCP address assignment. Thats fine but you'll want to reserve the IP address within the DHCP server (if you want you can also do this with the boiler system). That way the DHCP server won't alter the settings which could have messed you up. Ref: [https://technet.microsoft.com/en-us/library/cc781008(v=ws.10).aspx|What Is DHCP]
Now the bully in the room! Windows its self has a name service WINS. I Like to say you WINS you lose! As I hate it! It always messes you up as the pecking order is WINS first then it will fall over to IP name services (Host & DNS). What can happen is the WINS DB can get corrupted and depending on what you assign your systems for names it can confuse the lookup. So what I do is use a different name for the Windows systems (for WINS) than the TC/IP name I assign for the same system as an example ' '''w'''acme-school.com' and 'acme-school.com' That way WINS is bypassed! Ref: [https://technet.microsoft.com/en-us/library/cc725802(v=ws.11).aspx|Windows Internet Name Service (WINS) Overview]
As to gaining access to the Internet from this system (outwards) your DHCP settings should be fine setting the nearest routers IP address as your gateway and DNS, then use the helper function within the router to forward the request to your DNS in-house (that is if you have one) and then the ISP's DNS.
-
As to the reverse, gaining access to the PRIVA automation system from the Internet. I would recommend you do this through a VPN tunnel so you can control who is gaining access to the system (either one) and I would recommend you limit access if you can to the office system. Then piggy back the connection over to the PRIVA automation system in the boiler rm. That way you have a second door before someone can gain access to the system (you never know these days...) and limit it to as few people as needed (don't forget to alter the passwords for everyone if someone leaves! and delete their systems account and VPN access as well).
+
As to the reverse, gaining access to the PRIVA automation system from the Internet. I would recommend you do this through a VPN tunnel so you can control who is gaining access to the system (either one) and I would recommend you limit access if you can to the office system only (not the system in the boiler rm). Then piggy back the connection over to the PRIVA automation system in the boiler rm. That way you have a second door before someone can gain access to the system (you never know these days...) and limit it to as few people as needed (don't forget to alter the passwords for everyone if someone leaves! and delete their systems account and VPN access as well).
As to how to monitor things... You'll need to setup an RMON probe to pole the systems (not to often now!) Then review its logs for what happened.
Last piece here.. As you have multiple buildings one of the issue you can encounter is a ground loop. Review with your cabler the [http://blog.siemon.com/standards/category/tia/tia-607-b-generic-telecommunications-bonding-and-grounding-earthing-for-customer-premises|ANSI/TIA-607-B Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises] You may want to ask them if they have [https://www.bicsi.org|BICSI certified] people on their staff.
The first is your IP addressing of your internal network may create an issue. Lets say you are using non-Routable addressing ([https://en.wikipedia.org/wiki/Private_network|Private Network]) internally and your PRIVA automation system which is in the boiler rm has a fixed IP address in the address block you are using. Now the network path between the boiler rm and your office needs to be checked out. Ideally, you have a direct connection (no routers or switches) to the hub your office PC is sitting on. If you can't achieve that then make sure you only have layer 2 switching (no routing) devices between the two systems. Now within your management PC create a host file with the IP address and the host name. So now the systems routing tables see's this connection as a direct connection (same IP subnet on a flat network).
Now lets move on... Your management PC in your office likely has a DHCP address assignment. Thats fine but you'll want to reserve the IP address within the DHCP server (if you want you can also do this with the boiler system). That way the DHCP server won't alter the settings which could have messed you up. Ref: [https://technet.microsoft.com/en-us/library/cc781008(v=ws.10).aspx|What Is DHCP]
Now the bully in the room! Windows its self has a name service WINS. I Like to say you WINS you lose! As I hate it! It always messes you up as the pecking order is WINS first then it will fall over to IP name services (Host & DNS). What can happen is the WINS DB can get corrupted and depending on what you assign your systems for names it can confuse the lookup. So what I do is use a different name for the Windows systems (for WINS) than the TC/IP name I assign for the same system as an example ' '''w'''acme-school.com' and 'acme-school.com' That way WINS is bypassed! Ref: [https://technet.microsoft.com/en-us/library/cc725802(v=ws.11).aspx|Windows Internet Name Service (WINS) Overview]
As to gaining access to the Internet from this system (outwards) your DHCP settings should be fine setting the nearest routers IP address as your gateway and DNS, then use the helper function within the router to forward the request to your DNS in-house (that is if you have one) and then the ISP's DNS.
-
As to the reverse gaining access to the PRIVA automation system from the Internet. I would recommend you do this through a VPN tunnel so you can control who is gaining access to the system (either one) and I would recommend you limit access if you can to the office system. Then piggy back the connection over to the PRIVA automation system in the boiler rm. That way you have a second door before someone can gain access to the system (you never know these days...) and limit it to as few people as needed (don't forget to alter the passwords for everyone if someone leaves! and delete their systems account and VPN access as well).
+
As to the reverse, gaining access to the PRIVA automation system from the Internet. I would recommend you do this through a VPN tunnel so you can control who is gaining access to the system (either one) and I would recommend you limit access if you can to the office system. Then piggy back the connection over to the PRIVA automation system in the boiler rm. That way you have a second door before someone can gain access to the system (you never know these days...) and limit it to as few people as needed (don't forget to alter the passwords for everyone if someone leaves! and delete their systems account and VPN access as well).
As to how to monitor things... You'll need to setup an RMON probe to pole the systems (not to often now!) Then review its logs for what happened.
Last piece here.. As you have multiple buildings one of the issue you can encounter is a ground loop. Review with your cabler the [http://blog.siemon.com/standards/category/tia/tia-607-b-generic-telecommunications-bonding-and-grounding-earthing-for-customer-premises|ANSI/TIA-607-B Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises] You may want to ask them if they have [https://www.bicsi.org|BICSI certified] people on their staff.
The first is your IP addressing of your internal network may create an issue. Lets say you are using non-Routable addressing ([https://en.wikipedia.org/wiki/Private_network|Private Network]) internally and your PRIVA automation system which is in the boiler rm has a fixed IP address in the address block you are using. Now the network path between the boiler rm and your office needs to be checked out. Ideally, you have a direct connection (no routers or switches) to the hub your office PC is sitting on. If you can't achieve that then make sure you only have layer 2 switching (no routing) devices between the two systems. Now within your management PC create a host file with the IP address and the host name. So now the systems routing tables see's this connection as a direct connection (same IP subnet on a flat network).
Now lets move on... Your management PC in your office likely has a DHCP address assignment. Thats fine but you'll want to reserve the IP address within the DHCP server (if you want you can also do this with the boiler system). That way the DHCP server won't alter the settings which could have messed you up. Ref: [https://technet.microsoft.com/en-us/library/cc781008(v=ws.10).aspx|What Is DHCP]
-
Now the bully in the room! Windows its self has a name service WINS. I Like to say you WINS you lose! As I hate it! It always messes you up as the pecking order is WINS first then it will fall over to IP name services (Host & DNS). What can happen is the WINS DB can get corrupted and depending on what you assign your systems for names it can confuse the lookup. So what I do is use a different name for the Windows systems (for WINS) than the TC/IP name I assign for the same system as an example ' '''w'''acme-school.com' and 'acme-school.com' That way WINS is bypassed!
+
Now the bully in the room! Windows its self has a name service WINS. I Like to say you WINS you lose! As I hate it! It always messes you up as the pecking order is WINS first then it will fall over to IP name services (Host & DNS). What can happen is the WINS DB can get corrupted and depending on what you assign your systems for names it can confuse the lookup. So what I do is use a different name for the Windows systems (for WINS) than the TC/IP name I assign for the same system as an example ' '''w'''acme-school.com' and 'acme-school.com' That way WINS is bypassed! Ref: [https://technet.microsoft.com/en-us/library/cc725802(v=ws.11).aspx|Windows Internet Name Service (WINS) Overview]
As to gaining access to the Internet from this system (outwards) your DHCP settings should be fine setting the nearest routers IP address as your gateway and DNS, then use the helper function within the router to forward the request to your DNS in-house (that is if you have one) and then the ISP's DNS.
As to the reverse gaining access to the PRIVA automation system from the Internet. I would recommend you do this through a VPN tunnel so you can control who is gaining access to the system (either one) and I would recommend you limit access if you can to the office system. Then piggy back the connection over to the PRIVA automation system in the boiler rm. That way you have a second door before someone can gain access to the system (you never know these days...) and limit it to as few people as needed (don't forget to alter the passwords for everyone if someone leaves! and delete their systems account and VPN access as well).
As to how to monitor things... You'll need to setup an RMON probe to pole the systems (not to often now!) Then review its logs for what happened.
Last piece here.. As you have multiple buildings one of the issue you can encounter is a ground loop. Review with your cabler the [http://blog.siemon.com/standards/category/tia/tia-607-b-generic-telecommunications-bonding-and-grounding-earthing-for-customer-premises|ANSI/TIA-607-B Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises] You may want to ask them if they have [https://www.bicsi.org|BICSI certified] people on their staff.
The first is your IP addressing of your internal network may create an issue. Lets say you are using non-Routable addressing ([https://en.wikipedia.org/wiki/Private_network|Private Network]) internally and your PRIVA automation system which is in the boiler rm has a fixed IP address in the address block you are using. Now the network path between the boiler rm and your office needs to be checked out. Ideally, you have a direct connection (no routers or switches) to the hub your office PC is sitting on. If you can't achieve that then make sure you only have layer 2 switching (no routing) devices between the two systems. Now within your management PC create a host file with the IP address and the host name. So now the systems routing tables see's this connection as a direct connection (same IP subnet on a flat network).
-
Now lets move on... Your management PC in your office likely has a DHCP address assignment. Thats fine but you'll want to reserve the IP address within the DHCP server (if you want you can also do this with the boiler system). That way the DHCP server won't alter the settings which could have messed you up.
+
Now lets move on... Your management PC in your office likely has a DHCP address assignment. Thats fine but you'll want to reserve the IP address within the DHCP server (if you want you can also do this with the boiler system). That way the DHCP server won't alter the settings which could have messed you up. Ref: [https://technet.microsoft.com/en-us/library/cc781008(v=ws.10).aspx|What Is DHCP]
Now the bully in the room! Windows its self has a name service WINS. I Like to say you WINS you lose! As I hate it! It always messes you up as the pecking order is WINS first then it will fall over to IP name services (Host & DNS). What can happen is the WINS DB can get corrupted and depending on what you assign your systems for names it can confuse the lookup. So what I do is use a different name for the Windows systems (for WINS) than the TC/IP name I assign for the same system as an example ' '''w'''acme-school.com' and 'acme-school.com' That way WINS is bypassed!
As to gaining access to the Internet from this system (outwards) your DHCP settings should be fine setting the nearest routers IP address as your gateway and DNS, then use the helper function within the router to forward the request to your DNS in-house (that is if you have one) and then the ISP's DNS.
As to the reverse gaining access to the PRIVA automation system from the Internet. I would recommend you do this through a VPN tunnel so you can control who is gaining access to the system (either one) and I would recommend you limit access if you can to the office system. Then piggy back the connection over to the PRIVA automation system in the boiler rm. That way you have a second door before someone can gain access to the system (you never know these days...) and limit it to as few people as needed (don't forget to alter the passwords for everyone if someone leaves! and delete their systems account and VPN access as well).
As to how to monitor things... You'll need to setup an RMON probe to pole the systems (not to often now!) Then review its logs for what happened.
Last piece here.. As you have multiple buildings one of the issue you can encounter is a ground loop. Review with your cabler the [http://blog.siemon.com/standards/category/tia/tia-607-b-generic-telecommunications-bonding-and-grounding-earthing-for-customer-premises|ANSI/TIA-607-B Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises] You may want to ask them if they have [https://www.bicsi.org|BICSI certified] people on their staff.
The first is your IP addressing of your internal network may create an issue. Lets say you are using non-Routable addressing ([https://en.wikipedia.org/wiki/Private_network|Private Network]) internally and your PRIVA automation system which is in the boiler rm has a fixed IP address in the address block you are using. Now the network path between the boiler rm and your office needs to be checked out. Ideally, you have a direct connection (no routers or switches) to the hub your office PC is sitting on. If you can't achieve that then make sure you only have layer 2 switching (no routing) devices between the two systems. Now within your management PC create a host file with the IP address and the host name. So now the systems routing tables see's this connection as a direct connection (same IP subnet).
+
The first is your IP addressing of your internal network may create an issue. Lets say you are using non-Routable addressing ([https://en.wikipedia.org/wiki/Private_network|Private Network]) internally and your PRIVA automation system which is in the boiler rm has a fixed IP address in the address block you are using. Now the network path between the boiler rm and your office needs to be checked out. Ideally, you have a direct connection (no routers or switches) to the hub your office PC is sitting on. If you can't achieve that then make sure you only have layer 2 switching (no routing) devices between the two systems. Now within your management PC create a host file with the IP address and the host name. So now the systems routing tables see's this connection as a direct connection (same IP subnet on a flat network).
Now lets move on... Your management PC in your office likely has a DHCP address assignment. Thats fine but you'll want to reserve the IP address within the DHCP server (if you want you can also do this with the boiler system). That way the DHCP server won't alter the settings which could have messed you up.
Now the bully in the room! Windows its self has a name service WINS. I Like to say you WINS you lose! As I hate it! It always messes you up as the pecking order is WINS first then it will fall over to IP name services (Host & DNS). What can happen is the WINS DB can get corrupted and depending on what you assign your systems for names it can confuse the lookup. So what I do is use a different name for the Windows systems (for WINS) than the TC/IP name I assign for the same system as an example ' '''w'''acme-school.com' and 'acme-school.com' That way WINS is bypassed!
As to gaining access to the Internet from this system (outwards) your DHCP settings should be fine setting the nearest routers IP address as your gateway and DNS, then use the helper function within the router to forward the request to your DNS in-house (that is if you have one) and then the ISP's DNS.
As to the reverse gaining access to the PRIVA automation system from the Internet. I would recommend you do this through a VPN tunnel so you can control who is gaining access to the system (either one) and I would recommend you limit access if you can to the office system. Then piggy back the connection over to the PRIVA automation system in the boiler rm. That way you have a second door before someone can gain access to the system (you never know these days...) and limit it to as few people as needed (don't forget to alter the passwords for everyone if someone leaves! and delete their systems account and VPN access as well).
As to how to monitor things... You'll need to setup an RMON probe to pole the systems (not to often now!) Then review its logs for what happened.
Last piece here.. As you have multiple buildings one of the issue you can encounter is a ground loop. Review with your cabler the [http://blog.siemon.com/standards/category/tia/tia-607-b-generic-telecommunications-bonding-and-grounding-earthing-for-customer-premises|ANSI/TIA-607-B Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises] You may want to ask them if they have [https://www.bicsi.org|BICSI certified] people on their staff.
The first is your IP addressing of your internal network may create an issue. Lets say you are using non-Routable addressing ([https://en.wikipedia.org/wiki/Private_network|Private Network]) internally and your PRIVA automation system which is in the boiler rm has a fixed IP address in the address block you are using. Now the network path between the boiler rm and your office needs to be checked out. Ideally, you have a direct connection (no routers or switches) to the hub your office PC is sitting on. If you can't achieve that then make sure you only have layer 2 switching (no routing) devices between the two systems. Now within your management PC create a host file with the IP address and the host name. So now the systems routing tables see's this connection as a direct connection (same IP subnet). Now lets move on... Your management PC in your office likely has a DHCP address assignment. Thats fine but you'll want to reserve the IP address within the DHCP server (if you want you can also do this with the boiler system). That way the DHCP server won't alter the settings which could have messed you up.
+
The first is your IP addressing of your internal network may create an issue. Lets say you are using non-Routable addressing ([https://en.wikipedia.org/wiki/Private_network|Private Network]) internally and your PRIVA automation system which is in the boiler rm has a fixed IP address in the address block you are using. Now the network path between the boiler rm and your office needs to be checked out. Ideally, you have a direct connection (no routers or switches) to the hub your office PC is sitting on. If you can't achieve that then make sure you only have layer 2 switching (no routing) devices between the two systems. Now within your management PC create a host file with the IP address and the host name. So now the systems routing tables see's this connection as a direct connection (same IP subnet).
+
+
Now lets move on... Your management PC in your office likely has a DHCP address assignment. Thats fine but you'll want to reserve the IP address within the DHCP server (if you want you can also do this with the boiler system). That way the DHCP server won't alter the settings which could have messed you up.
Now the bully in the room! Windows its self has a name service WINS. I Like to say you WINS you lose! As I hate it! It always messes you up as the pecking order is WINS first then it will fall over to IP name services (Host & DNS). What can happen is the WINS DB can get corrupted and depending on what you assign your systems for names it can confuse the lookup. So what I do is use a different name for the Windows systems (for WINS) than the TC/IP name I assign for the same system as an example ' '''w'''acme-school.com' and 'acme-school.com' That way WINS is bypassed!
As to gaining access to the Internet from this system (outwards) your DHCP settings should be fine setting the nearest routers IP address as your gateway and DNS, then use the helper function within the router to forward the request to your DNS in-house (that is if you have one) and then the ISP's DNS.
As to the reverse gaining access to the PRIVA automation system from the Internet. I would recommend you do this through a VPN tunnel so you can control who is gaining access to the system (either one) and I would recommend you limit access if you can to the office system. Then piggy back the connection over to the PRIVA automation system in the boiler rm. That way you have a second door before someone can gain access to the system (you never know these days...) and limit it to as few people as needed (don't forget to alter the passwords for everyone if someone leaves! and delete their systems account and VPN access as well).
As to how to monitor things... You'll need to setup an RMON probe to pole the systems (not to often now!) Then review its logs for what happened.
Last piece here.. As you have multiple buildings one of the issue you can encounter is a ground loop. Review with your cabler the [http://blog.siemon.com/standards/category/tia/tia-607-b-generic-telecommunications-bonding-and-grounding-earthing-for-customer-premises|ANSI/TIA-607-B Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises] You may want to ask them if they have [https://www.bicsi.org|BICSI certified] people on their staff.
You could have a few possible issues here:
The first is your IP addressing of your internal network may create an issue. Lets say you are using non-Routable addressing ([https://en.wikipedia.org/wiki/Private_network|Private Network]) internally and your PRIVA automation system which is in the boiler rm has a fixed IP address in the address block you are using. Now the network path between the boiler rm and your office needs to be checked out. Ideally, you have a direct connection (no routers or switches) to the hub your office PC is sitting on. If you can't achieve that then make sure you only have layer 2 switching (no routing) devices between the two systems. Now within your management PC create a host file with the IP address and the host name. So now the systems routing tables see's this connection as a direct connection (same IP subnet). Now lets move on... Your management PC in your office likely has a DHCP address assignment. Thats fine but you'll want to reserve the IP address within the DHCP server (if you want you can also do this with the boiler system). That way the DHCP server won't alter the settings which could have messed you up.
Now the bully in the room! Windows its self has a name service WINS. I Like to say you WINS you lose! As I hate it! It always messes you up as the pecking order is WINS first then it will fall over to IP name services (Host & DNS). What can happen is the WINS DB can get corrupted and depending on what you assign your systems for names it can confuse the lookup. So what I do is use a different name for the Windows systems (for WINS) than the TC/IP name I assign for the same system as an example ' '''w'''acme-school.com' and 'acme-school.com' That way WINS is bypassed!
As to gaining access to the Internet from this system (outwards) your DHCP settings should be fine setting the nearest routers IP address as your gateway and DNS, then use the helper function within the router to forward the request to your DNS in-house (that is if you have one) and then the ISP's DNS.
As to the reverse gaining access to the PRIVA automation system from the Internet. I would recommend you do this through a VPN tunnel so you can control who is gaining access to the system (either one) and I would recommend you limit access if you can to the office system. Then piggy back the connection over to the PRIVA automation system in the boiler rm. That way you have a second door before someone can gain access to the system (you never know these days...) and limit it to as few people as needed (don't forget to alter the passwords for everyone if someone leaves! and delete their systems account and VPN access as well).
As to how to monitor things... You'll need to setup an RMON probe to pole the systems (not to often now!) Then review its logs for what happened.
Last piece here.. As you have multiple buildings one of the issue you can encounter is a ground loop. Review with your cabler the [http://blog.siemon.com/standards/category/tia/tia-607-b-generic-telecommunications-bonding-and-grounding-earthing-for-customer-premises|ANSI/TIA-607-B Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises] You may want to ask them if they have [https://www.bicsi.org|BICSI certified] people on their staff.