re: Network Drive Disconnects at same time every day
Friday, December 5, 2008 at 1:42 pm
Windows Server 2003 Annoyances Discussion Forum
Posted by appleoddity
(2369 messages posted)
Your problem with moving laptops between networks is because you dont have a DHCP
server setup properly.
Your windows server 2003 should have a DHCP server installed and configured. It
should be providing the IP, DNS, Subnet, and Gateway information to your computers
automatically. This way, the laptops (and all the computers for that matter) can
be set to obtain all their information automatically. When they are at home, the
laptop will automatically pull the correct information, and when they are at work
the laptop will automatically pull the correct information. There should be no need
to insert this information statically into each machine which then limits it to a
single network.
For your second question. If I understand you properly, you have someone hosting
your website off-site, and internally you use the same domain name. What you are
trying to achieve is very simple, but probably not recommended. You need to modify
the domain registrar information and instead of letting your webhost handle the DNS
services, you need to let a DNS server on your network handle the services. Let me
tell you why you don't want to do it this way, and how I do things in similar situations.
Number one, if your server or network goes down, your website, e-mail, etc. will
all fail because your DNS services will be down. A hosting provider is going to
have redundancy and with that comes the reliability you need to ensure your external
services such as web, and e-mail do not go down.
Secondly, to achieve full integration like you are talking about, where you only
have to change the DNS entry in one location for both internal and external clients,
you would have to integrate in with your current active directory (server 2003) DNS
server that is serving your internal clients. This is insecure. You don't want
people on the internet to interact with your AD integrated DNS server. There may
not be any significant security drawbacks to it, but an AD integrated DNS server
contains a lot of information about the internal workings of your network and a hacker
could use that information against you.
The way I do things is to allow my web host to handle the main DNS services for external
clients. I also run an AD integrated DNS server for my internal clients. I make
a change to both DNS servers whenever I want to insert a new record. This is the
drawback to having the same domain name used internally, as externally on the internet.
The absolute best way that things should be setup is that you should have a domain
name that you use strictly for your internal network and a different domain name
that you use for the internet and your website/e-mail. That way the two DNS servers
do not conflict.
|
All messages in this thread [show all]
 | | | |  | re: Network Drive Disconnects at same time every day (appleoddity: Fri, Dec 5, 2008, 1:42 pm) |
| |
| |
| |
Return to the Windows Server 2003 Discussion Forum
|
|
