- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
No. You are on two different networks. Regardless of the hardware. Treat the home server just like any other PC or tablet. Make sure it has a dynamic IP via DHCP from your home router or ISP modem. Then connect via VPN.
You will not be able to network the two servers unless you have right equipment and network configuration. You would have to work with your service provider to obtain static IP's.
Internal IPs are irrelevant, because you can assign them your self internally. That means no one else sees them.
DNS-servers translate names, such as 'www.fixya.com' to IP-addresses, because routing of IP-packets on the Internet is done using the IP-addresses, not by using the names of each computer.
If you have a router between your computers and your cable-modem (or DSL-modem), then the router can automatically supply the "Primary DNS Server" and "Secondary DNS Server" and "IP Address" to your server computer, if you configure the network-adapter on the server to "automatically obtain an IP Address".
As long as you leave your server running, the "dynamic" IP-address that it obtains will, in effect, become a "static" (namely "non-changing") IP-address.
This is more a configuration error. Depending on how you have your DHCP setup, you may need to adjust it's setting. No mention of what os you are using but if you set your DHCP to give IP addresses only to the LAN, set the ISP NIC address to receive its ip from the ISP provider, you should be able to get Internet access to your server and the LAN.
If you have done so, use the server os to setup your Internet connection. Answer a few questions about how you connect to the Net and the os will do most of the configuration for you.
Assuming that your objective is to have an ISA server to protect each building's separate internet connection while maintaining a separate link for the internal networks between buildings then the answer is yes.
Here are a few things to watch:
1. Each building needs to be on its own subnet
2. You can connect the buildings to each other through ISA in several ways or by using a layer 3 switch or router on each end. Either way, you'll need to provide routes between the two private networks.
3. If you only have on DC and it's handling all DHCP you'll need to make sure that the switches can handle DHCP helpers and configure this appropriately. If you need help on this, let me know.
4. If you want to have the ability to quickly configure one ISA server to handle traffic for the opposite building in the event of an internet failure you'll need to configure a short DHCP lease. That way you can re-configure the gateway and get it out quickly to the clients after a failure, i.e. if you can stand an hour without internet easily, a one hour lease would be appropriate. The price for this is increased DHCP overhead traffic on the network.
If you are looking for a true high availability solution where you'll have no downtime on either side if the internet goes down then you will need ISA Enterprise on each end and the implementation will be quite complex and well beyond the scope of what we can do here.
If any of my assumptions are wrong, let me know and I'll try to fill in the holes.
Check below things:
1) Check Primary DNS server ip in TCP IP Configuration
2) Stop Unwanted services from start up
3) Run Chkdsk /R command from command prompt and restart the server. It will check your harddrive and recover data.