Re: Unable to connect to a share
- From: "Jeremy Lyons" <i.am.jammo@xxxxxxxxx>
- Date: 11 Feb 2007 10:49:45 -0800
Hello,
You cannot use DNS for fault-tolerance. Round-robin DNS is when you
have multiple A records pointing to different IPs. However, once a
client queries DNS, that is cached locally for the duration of the
TTL. DNS will also resolve the IP of a server whether it is online or
not, so it will not detect failure and resolve another name.
Your first example:
Mach1 10.1.1.101
Mach1-dr 10.1.1.102
....will work as long as your users are trained to connect to Mach1-dr
in the event the other fails, and that you are keeping both file
servers synchronized. The only high-availability machanism I know of
for Windows file servers is clustering, which requires Windows Server
EE, shared storage, and can get pretty expensive. This will allow you
to use a single hostname, and will failover to the passive node in the
event your active node fails. This would be transparent to your end
users.
HTH,
JL
On Feb 11, 8:01 am, DonC <D...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I am trying to use DNS to modify where users connect in the event of a
server malfunction.
Two machines:
Mach1 10.1.1.101
Mach1-dr 10.1.1.102
Users connect to Mach1 normally but if it fails, DNS is changed to:
Mach1 10.1.1.101
Mach1-dr 10.1.1.101
Users should now connect to the DR machine.
The problem with mapped drives. You are unable to map to \\Mach1\d$. It just
keeps asking for a username/password.
Mapping as \\Mach1-dr\d4 and 10.1.1.102\d$ work.
You can ping it, other services are fine. however using the original name
fails.
Anyone got any ideas.
.
- Prev by Date: Re: Best Practice for setting up DNS for ISPs with Microsoft Server 2003 Enterprise
- Next by Date: Re: Overlapping Reverse Zone Files
- Previous by thread: Overlapping Reverse Zone Files
- Next by thread: Re: Unable to connect to a share
- Index(es):
Relevant Pages
|
Loading
