Re: Unable to connect to a share
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Sun, 11 Feb 2007 13:17:56 -0600
"DonC" <DonC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:35D9D53A-6E10-4AD9-80EE-0C7E4323B424@xxxxxxxxxxxxxxxx
I am trying to use DNS to modify where users connect in the event of a
server malfunction.
DNS (round robin) doesn't geneally provide fault tolerance since most
IP service clients will never use a second IP when the first (or best) IP
fails -- there are specific exceptions to this such as SMTP servers acting
as clients when sending email to OTHER SMTP server (even this exception
is not generally supported by regular SMTP clients like Outlook or Eudora.)
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.
After TTL expires it will. You have changed DNS, but DNS is typically
cached by resolving DNS servers and modern DNS clients for (up to)
TTL.
The problem with mapped drives. You are unable to map to \\Mach1\d$. It
just
keeps asking for a username/password.
But notice that Mach1 in your example above ALWAYS resolves toe .101.
Mapping as \\Mach1-dr\d4 and 10.1.1.102\d$ work.
Odds are you were expecting to still connect to .102.
Another possibility is that you are getting the wrong server due to
resolving
the NetBIOS name.
You can ping it, other services are fine. however using the original name
fails.
This part tends to imply the NetBIOS name resolution more strongly.
Anyone got any ideas.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- Prev by Date: Re: Adding a new DNS server first to replace unather later
- Next by Date: Re: Adding a new DNS server first to replace unather later
- Previous by thread: Re: Unable to connect to a share
- Next by thread: Re: Unable to connect to a share
- Index(es):
Relevant Pages
|
