dial.
From: Carl Houseman [mailto:c.house...@gmail.com]
Sent: Wednesday, December 17, 2008 10:53 AM
To: NT System Admin Issues
Subject: RE: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
Thanks Bob, hadn't run into that widget before.
Now
ccess to local domain servers when connected w/VPN to
remote / different Windows domain
> Anybody know of a way to script the removal of something from the saved
passwords list?
I haven't followed this whole thread but the answer to that particular
question, cmdkey may be your friend
me.mydomain.com always
prompts. Even when servername.mydomain.com is added to Intranet or Trusted
zones, it still prompts.
Carl
From: Carl Houseman [mailto:c.house...@gmail.com]
Sent: Saturday, December 13, 2008 12:24 PM
To: NT System Admin Issues
Subject: RE: Lose access to loca
: Re: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
On Sat, Dec 13, 2008 at 12:23 PM, Carl Houseman
wrote:
> psexec \\server command
> Couldn't access server:
>
> Meanwhile, psexec \\server.mydomain.com worked just fine.
Maybe the
PM
To: NT System Admin Issues
Subject: Re: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
On Sat, Dec 13, 2008 at 11:01 AM, Carl Houseman
wrote:
> I'll let you explain them however you like!
I don't have enough information to explain anythi
On Sat, Dec 13, 2008 at 12:23 PM, Carl Houseman wrote:
> psexec \\server command
> Couldn't access server:
>
> Meanwhile, psexec \\server.mydomain.com worked just fine.
Maybe the customer has a wildcard DNS record, or a server or other
entity with the same name as "server" in your local environ
On Sat, Dec 13, 2008 at 11:01 AM, Carl Houseman wrote:
> I'll let you explain them however you like!
I don't have enough information to explain anything definitively,
I'm afraid. :)
> A local LAN adapter references one Windows AD DNS - TLD= a.com
Just so you know, TLD is "Top Level Domain"
Here's a new way I can see this problem... I don't know if this would have
happened before the reboot, but I rebooted the DC in my local environment
(it's the only DC).
Following that, from the Vista machine I wanted to run something on the
DC I typed
psexec \\server command
Respo
t [mailto:mailvor...@gmail.com]
Sent: Friday, December 12, 2008 7:35 PM
To: NT System Admin Issues
Subject: Re: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
On Fri, Dec 12, 2008 at 12:37 PM, Carl Houseman
wrote:
> When there are multiple adapt
ge.com]
Sent: Friday, December 12, 2008 3:06 PM
To: NT System Admin Issues
Subject: RE: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
What does your wins look like?
What's the Kerb lifetime of the remote and are they defaulting to UDP or TCP
gt; other workarounds. A single entry in the hosts files for my AD domain to
> avoid this problem is a very minor and acceptable workaround.
>
> Carl
>
> -Original Message-
> From: Kurt Buff [mailto:kurt.b...@gmail.com]
> Sent: Thursday, December 11, 2008 8:41 PM
&
On Fri, Dec 12, 2008 at 12:37 PM, Carl Houseman wrote:
> When there are multiple adapters each with their own DNS, DNS
> resolution is attempted on each adapter in turn until one resolves
> it and only fails if none of them resolve it.
I believe that is inaccurate.
To the best of my knowledg
useman [mailto:c.house...@gmail.com]
Sent: Friday, December 12, 2008 2:45 PM
To: NT System Admin Issues
Subject: RE: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
Well crap. The problem just happened again. Sorry John, looks like you
don'
Carl
From: Carl Houseman [mailto:c.house...@gmail.com]
Sent: Friday, December 12, 2008 1:29 PM
To: NT System Admin Issues
Subject: RE: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
It looks like the problem is solved. I've been reviewing
Carl,
Is this what you guys do? Make popcorn? What's the website, I might put an
order in too...I love that stuff.
Steve
On Fri, Dec 12, 2008 at 12:29 PM, Carl Houseman wrote:
> It looks like the problem is solved. I've been reviewing all the
> responses to see if anyone won the popcorn... :)
It looks like the problem is solved. I've been reviewing all the responses
to see if anyone won the popcorn... :)
John Gwinner's answer was the first to call DNS into question and he also
described what ended up being the problem - the fact that my AD domain name
was being resolved by the remo
--
From: Ben Scott [mailto:mailvor...@gmail.com]
Sent: Wednesday, December 10, 2008 9:35 PM
To: NT System Admin Issues
Subject: Re: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
On Wed, Dec 10, 2008 at 4:29 PM, Carl Houseman wrote:
> The default DNS af
Subject: Re: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
On Thu, Dec 11, 2008 at 6:45 AM, Carl Houseman wrote:
> "Use default gateway on remote network" is NOT checked for the VPN TCP/IP
> configuration.
Dang. That eliminates my
On Thu, Dec 11, 2008 at 6:45 AM, Carl Houseman wrote:
> "Use default gateway on remote network" is NOT checked for the VPN TCP/IP
> configuration.
Dang. That eliminates my best guess.
> I agree with the recommendations about diagnosing in a methodical way. Here
> are the results. If you don't
name\share" - still fails. Still cached somewhere?
I'll have to reboot and start again with only the hosts entry for
mydomain.com as the workaround, and see what the results are. More when I
know more. Thanks everybody for your comments.
Carl
-Original Message-
From: Kurt Buf
Thursday, December 11, 2008 8:25 AM
> To: NT System Admin Issues
> Subject: Re: Lose access to local domain servers when connected w/VPN
> to remote / different Windows domain
>
> On Wed, Dec 10, 2008 at 11:34 PM, Kurt Buff <[EMAIL PROTECTED]>
> wrote:
> > Start at the beg
On Wed, Dec 10, 2008 at 11:34 PM, Kurt Buff <[EMAIL PROTECTED]> wrote:
> Start at the beginning... When this problem occurs, can you ping
> the hard-to-reach server by IP address? ...
Indeed. It's always a good idea to follow a methodical approach.
Work step-by-step to identify what works, and
Start at the beginning...
When this problem occurs, can you ping the hard-to-reach server by IP
address? What does 'ping -a ip.add.re.ss' reveal? If those work, ping
by name, but if those fail, what does tracert reveal? What does
ipconfig /all reveal - as others have voiced, I have my suspicions
a
On Wed, Dec 10, 2008 at 4:29 PM, Carl Houseman <[EMAIL PROTECTED]> wrote:
> The default DNS after connecting (the one that
> NSLOOKUP identifies) is a server on the client
> network's in the client's AD domain ...
I'd bet money (or, at least, popcorn) that's your problem.
The list of DNS serv
From: Carl Houseman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2008 4:30 PM
To: NT System Admin Issues
Subject: RE: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
The default DNS after connecting (the one that NSLOOKUP identifies) is a
se
92.168.0.X.
== John ==
From: Carl Houseman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2008 12:30 PM
To: NT System Admin Issues
Subject: RE: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
No, the usernames and passwords are
ld be able to present different credentials manually.
From: Carl Houseman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2008 15:30
To: NT System Admin Issues
Subject: RE: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
No, the use
local domain servers when connected w/VPN to
remote / different Windows domain
Have you tried un-checking the option to "Use default gateway on remote
network", under the general tab of the advanced tcp/ip settings for the VPN
connection?
From: Carl Houseman [mailto:[EMAIL PROTECTE
Have you tried un-checking the option to "Use default gateway on remote
network", under the general tab of the advanced tcp/ip settings for the
VPN connection?
From: Carl Houseman [mailto:[EMAIL PROTECTED]
Posted At: Wednesday, December 10, 2008 2:28 PM
Posted To: Sunbelt NT
Conversation: Lose
To: NT System Admin Issues
Subject: RE: Lose access to local domain servers when connected w/VPN to
remote / different Windows domain
No, the usernames and passwords are different, and they must remain that
way.
Carl
From: Steve Ens [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10,
No, the usernames and passwords are different, and they must remain that
way.
Carl
From: Steve Ens [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2008 2:35 PM
To: NT System Admin Issues
Subject: Re: Lose access to local domain servers when connected w/VPN to
remote / different
You do have a local account on the remote serversame username and
password I presume?
On Wed, Dec 10, 2008 at 1:28 PM, Carl Houseman <[EMAIL PROTECTED]> wrote:
> This problem has bothered me a long time, and happens daily. It's so
> bothersome, I'll send some Dale & Thomas popcorn to the fi
32 matches
Mail list logo
