Re: DHCP issues (solved!)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Claus - many thanks. Yes, the post is getting long! The problem was mainly
with the internal LAN (connectivity was lost & I had to input fixed IP's to
the client PC's NICs.)
However, all your pointers focused me in the right direction & I seem to
have resolved the issue!! - last week the day before the issue had started,
I had set up a new Firewall Policy on ISA called Block Forbidden Sites (the
object of which was to prevent staff accessing sites that could either have
objectionable content or be likely to be a security risk). That policy
seemed to be working fine (I followed instructions from the ISA forum),
however on switching the policy off the LAN Clients suddenly have DHCP
connectivity!! I have then tested by making an exception to the protocols
being blocked to allow dhcp reply & request and re-applied the Policy - the
DHCP still works. So it seems that somehow that Policy was also blocking
internal dhcp/udp traffic?
Only thing o/s is that the internal interface on RRAS shows status as
"enabled" yet under Ip Routing>General the IP address shows as "not
available"!! (ratherthan teh 169.254.x.x. of before!) Will wait to see what
happens when a VPN client attempts to access!!
Many thanks everyone
"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:%23NmgtgcvHHA.2068@xxxxxxxxxxxxxxxxxxxxxxx
Al,

This post is getting long and I'm not sure if you had any issue with any
computer on the local LAN. If so, I would pop in a laptop and test.

As to RRAS you definitely have a problem. The Internal Interface should
show a valid IP from the LAN. Check a few settings. Right-click on the
RRAS, select properties. Check that "Router" and "LAN routing only" and
"remote access server" are selected. Click on the IP tab and make sure
that all 3 checkboxes are checked, the DHCP radio button is selected and
on the bottom it shows "Server Local Area Connection".
If you had to make any changes, restart RRAS.

--
Claus
"Al" <nospamplease@xxxxxxxxxxxxxxxxxx> wrote in message
news:4e-dnfnERLZ4JBfbnZ2dnUVZ8qminZ2d@xxxxxxxxxxxxxxxxx
Claus thanks, yes I see the point now that this demonstrates that the
168.254.x.x is being caused by the lack of DHCP leases. However, what I
need to know is "why" - I have checked & DHCP server seems to be running,
but something must be blocking teh issue or receipt of the IP's. The
only other thing I have noticed is that in RRAS, under IP Routing >
General the Internal Interface shows as 169.254.88.91, but perhaps this
again is just a result of the dhcp not working ratherthan a cause of it?
Any help gratefully received!!!

"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:%23DL5tJWvHHA.4012@xxxxxxxxxxxxxxxxxxxxxxx
Al,

As I pointed out in my earlier post, 169.254.x.x addresses are used by
Windows as a default when the computer doesn't get a valid address from
the DHCP.

--
Claus
"Al" <nospamplease@xxxxxxxxxxxxxxxxxx> wrote in message
news:f6d4hn$18fo$2@xxxxxxxxxxxxxxxxxxxx
Having now tried to VPN into teh SBS network, I find this works fine
but that the the VPN server (I assume this is part of ISA) is giving
out 169.254.x.x. range IP's - the Network connection on the client
VPN'ing in is reporting that the Server address is 169.254.88.91 & that
it has a Client Address of 169.254.5.234
Does this in some way relate to the issue? Previously the VPN
addresses were definitely on the 10.0.0.x subnet.
Thanks


"Henry Craven {SBS-MVP}" <sme@xxxxxxxxxxxxxx> wrote in message
news:A5F8841E-B3F2-42DC-A04D-B9320DE724BE@xxxxxxxxxxxxxxxx
That together with printers and routers I include as reservations
within the scope.

--
Henry Craven {SBS-MVP}


"nik" <nik_AT_cict.co.uk> wrote in message
news:%23YRlVNPvHHA.484@xxxxxxxxxxxxxxxxxxxxxxx


Scope should be 10.0.0.1 > 10.0.0.254
( .255 like .0 is reserved )
Subnet Mask: 255.255.255.0

Surely you must keep at least one fixed IP for the server? If scope
includes x.x.x.1 all the way to .x.x.x.254, what's the DHCP server
using?
Just a thought...
Nik











.


Quantcast