Discussion:
Odd issue with DHCP leases & RAS
(too old to reply)
zebulebu
2006-03-06 18:22:30 UTC
Permalink
Hi

I've got a test LAN setup at home running win2K/win2K3 with the main DC
running Windows 2000 (I also have a w2K3 DC and am in the process of
migrating everything to that)

My odd issue is that yesterday, as I was preparing to migrate DHCP from
one to the other, I noticed two entries in the DHCP scope that had
'RAS' in the unique ID field. Both were pointing to the same IP, which
was a box that I had assigned a static IP to. When I tried to delete
them I received an error message (which, stupidly, I didn't note down).
I rebooted the box in question and was subsequently able to delete the
leases without issue but am still a little bit concerned.

RRAS is not enabled on the box (in fact, its not enabled anywhere on my
LAN as far as I'm aware) so its puzzling me a little bit. Could it be
that when I RDP into my LAN from a remote location (or even RDP from
'inside' the perimter) onto the box in question the DC generates a DHCP
lease for that connection? The box that was being assigned the 'etxra'
leases is the one I use to remote onto when I'm away (Running XP SP2)
and I do occasionally use the RDP Web client.

I'm naturally a little bit worried - can anyone shed any light on this?

Cheers!

PS: Apologies to anyone who may have read this message twice - I've
cross-posted in other groups in the hope that someone will be able to
help me!
Bill Grant
2006-03-06 21:52:34 UTC
Permalink
If a workstation is leasing two IP addresses from DHCP as RAS, it almost
certainly has "Incoming Connections" enabled. Enabling this leases two IPs
from DHCP - one for the host and one for the guest.
Post by zebulebu
Hi
I've got a test LAN setup at home running win2K/win2K3 with the main
DC running Windows 2000 (I also have a w2K3 DC and am in the process
of migrating everything to that)
My odd issue is that yesterday, as I was preparing to migrate DHCP
from one to the other, I noticed two entries in the DHCP scope that
had 'RAS' in the unique ID field. Both were pointing to the same IP,
which was a box that I had assigned a static IP to. When I tried to
delete them I received an error message (which, stupidly, I didn't
note down). I rebooted the box in question and was subsequently able
to delete the leases without issue but am still a little bit
concerned.
RRAS is not enabled on the box (in fact, its not enabled anywhere on
my LAN as far as I'm aware) so its puzzling me a little bit. Could it
be that when I RDP into my LAN from a remote location (or even RDP
from 'inside' the perimter) onto the box in question the DC generates
a DHCP lease for that connection? The box that was being assigned the
'etxra' leases is the one I use to remote onto when I'm away (Running
XP SP2) and I do occasionally use the RDP Web client.
I'm naturally a little bit worried - can anyone shed any light on this?
Cheers!
PS: Apologies to anyone who may have read this message twice - I've
cross-posted in other groups in the hope that someone will be able to
help me!
zebulebu
2006-03-10 03:43:37 UTC
Permalink
OK, I can understand tat - but why would I have TWO extra RAS leases
for that IP? Surely if it were due to incoming connections then it
would only be one?

Still confused (and a little bit worried)
Bill Grant
2006-03-10 07:05:10 UTC
Permalink
No, RAS leases two IPs when you enable Incoming Connections. One is
required for the remote client and one for the host machine itself. The
"RAS" interface is quite separate from the LAN NIC and has its own IP
address.
Post by zebulebu
OK, I can understand tat - but why would I have TWO extra RAS leases
for that IP? Surely if it were due to incoming connections then it
would only be one?
Still confused (and a little bit worried)
zebulebu
2006-03-10 10:10:50 UTC
Permalink
That explains it then!

Thanks a lot - there is still an odd thing whereby occasionally when
the box reboots the two leases show up immediately in the scope and
occasionally they don't - in fact on a couple of occasions they have
NEVER shown up!

At least now I know there's nothing nasty at work here though

Cheers for the info!

Loading...