|
|
OK, let me see if I can get this right, I'm a newbie at DNS.....
We are using Dynamic DNS with AD integration. We use Cisco VPN and
Client, NOT microsoft VPN. So when a user boots their laptop,
connects to their ISP, runs the VPN client and connects to VPN they
received a 192.168.x.x ip address. Now what happens is when they run
Outlook and connect to the Exchange server that 192.168.x.x address
gets registered in DNS. The problem is that after that person leaves
and another user comes in, about 3 out of 5 5 times they will get
registered in DNS with the same 192.168.x.x ip address. So when we
look at DNS there will be several computers with the same 192.168.x.x
address. What is going wrong or not happening behind the scenes that
causes this problem?
|
|
"Flash3200" <Flash3200[ at ]gmail.com> wrote in message
news:1180462733.479336.62490[ at ]o5g2000hsb.googlegroups.com...
[Quoted Text] > OK, let me see if I can get this right, I'm a newbie at DNS.....
>
> We are using Dynamic DNS with AD integration. We use Cisco VPN and
> Client, NOT microsoft VPN. So when a user boots their laptop,
> connects to their ISP, runs the VPN client and connects to VPN they
> received a 192.168.x.x ip address. Now what happens is when they run
> Outlook and connect to the Exchange server that 192.168.x.x address
> gets registered in DNS. The problem is that after that person leaves
> and another user comes in, about 3 out of 5 5 times they will get
> registered in DNS with the same 192.168.x.x ip address. So when we
> look at DNS there will be several computers with the same 192.168.x.x
> address.
So what? (most of the time this really doen't matter unless you have
thousands
of them.)
You can scavenge them in DNS.
> What is going wrong or not happening behind the scenes that
> causes this problem?
Clients are not deregistering which the MS DHCP server COULD
do for you if you used it instead of the Cisco or letting the clients do
this themselves.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
|
|
Flash3200 wrote:
[Quoted Text] > OK, let me see if I can get this right, I'm a newbie at DNS.....
>
> We are using Dynamic DNS with AD integration. We use Cisco VPN and
> Client, NOT microsoft VPN. So when a user boots their laptop,
> connects to their ISP, runs the VPN client and connects to VPN they
> received a 192.168.x.x ip address. Now what happens is when they run
> Outlook and connect to the Exchange server that 192.168.x.x address
> gets registered in DNS. The problem is that after that person leaves
> and another user comes in, about 3 out of 5 5 times they will get
> registered in DNS with the same 192.168.x.x ip address. So when we
> look at DNS there will be several computers with the same 192.168.x.x
> address. What is going wrong or not happening behind the scenes that
> causes this problem?
>
Often times remote VPN users get a separate address space just for them.
Something like:
Regular DHCP Scope: 192.168.1.100-192.168.1.200
VPN Users: 192.168.1.201-192.168.1.250
As Herb eluded to earlier though, it's not a huge concern.
|
|
Well the problem we are having because of all this is that when
someone from Desktop Support tries to Remote Desktop into a VPN user's
computer when they are Virtual they end up remoting into someone
else's PC because the name goes to the same IP address and without
much investigation its tidious (spelling?) to hunt down the correct IP
address, especially if the user isn't all that technical to help with
doing ipconfigs on their own laptop.
On May 30, 10:37 pm, James Beukelman <james...[ at ]gmail.com> wrote:
[Quoted Text] > Flash3200 wrote:
> > OK, let me see if I can get this right, I'm a newbie at DNS.....
>
> > We are using Dynamic DNS with AD integration. We use Cisco VPN and
> > Client, NOT microsoft VPN. So when a user boots their laptop,
> > connects to their ISP, runs the VPN client and connects to VPN they
> > received a 192.168.x.x ip address. Now what happens is when they run
> > Outlook and connect to the Exchange server that 192.168.x.x address
> > gets registered in DNS. The problem is that after that person leaves
> > and another user comes in, about 3 out of 5 5 times they will get
> > registered in DNS with the same 192.168.x.x ip address. So when we
> > look at DNS there will be several computers with the same 192.168.x.x
> > address. What is going wrong or not happening behind the scenes that
> > causes this problem?
>
> Often times remote VPN users get a separate address space just for them.
> Something like:
>
> Regular DHCP Scope: 192.168.1.100-192.168.1.200
> VPN Users: 192.168.1.201-192.168.1.250
>
> As Herb eluded to earlier though, it's not a huge concern.
|
|
It seems to me like you might be having a few issues. I will discuss a few
of them that might help you solve your issues. You should check your VPN
DHCP server to see how long it will allow an assigned IP address to be
active. If this threshold is high, like eight days or something, it will
keep assigning that ip address to the machines that had it before. Set the
threshold down to like a day or a few hours just to test it. Also, you need
to have each of your vpn users to flush their dns. This can be done manually
or via a login script. The command would be ipconfig /flushdns. This will
clear the dns cache on the XP machine.
--
Chan Heard
Corporate Systems Administrator II
Yellow Hammer
a Jack Henry Company
Office : (205) 981-1980
Fax: 866-248-9812
cheard[ at ]jackhenry.com
"Flash3200" wrote:
[Quoted Text] > Well the problem we are having because of all this is that when
> someone from Desktop Support tries to Remote Desktop into a VPN user's
> computer when they are Virtual they end up remoting into someone
> else's PC because the name goes to the same IP address and without
> much investigation its tidious (spelling?) to hunt down the correct IP
> address, especially if the user isn't all that technical to help with
> doing ipconfigs on their own laptop.
>
>
> On May 30, 10:37 pm, James Beukelman <james...[ at ]gmail.com> wrote:
> > Flash3200 wrote:
> > > OK, let me see if I can get this right, I'm a newbie at DNS.....
> >
> > > We are using Dynamic DNS with AD integration. We use Cisco VPN and
> > > Client, NOT microsoft VPN. So when a user boots their laptop,
> > > connects to their ISP, runs the VPN client and connects to VPN they
> > > received a 192.168.x.x ip address. Now what happens is when they run
> > > Outlook and connect to the Exchange server that 192.168.x.x address
> > > gets registered in DNS. The problem is that after that person leaves
> > > and another user comes in, about 3 out of 5 5 times they will get
> > > registered in DNS with the same 192.168.x.x ip address. So when we
> > > look at DNS there will be several computers with the same 192.168.x.x
> > > address. What is going wrong or not happening behind the scenes that
> > > causes this problem?
> >
> > Often times remote VPN users get a separate address space just for them.
> > Something like:
> >
> > Regular DHCP Scope: 192.168.1.100-192.168.1.200
> > VPN Users: 192.168.1.201-192.168.1.250
> >
> > As Herb eluded to earlier though, it's not a huge concern.
>
>
>
|
|
|