Re: Please HELP... dhcp / ip / nic issues
From: microsoft (turbovw18_at_hotmail.com)
Date: 03/31/04
- Next message: Himalaya: "Re: install network monitor"
- Previous message: microsoft: "Re: Please HELP... dhcp / ip / nic issues"
- In reply to: microsoft: "Re: Please HELP... dhcp / ip / nic issues"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 31 Mar 2004 15:34:41 -0500
update...
it seems as if i release the adapter and reboot everything is ok... but...
if i release the adapter and renew it... it pulls 192.169.233.x as the
localhost ... and sets the gateway to 192.168.233.2 ....
i have never seen these ip's before and they ARE NOT any part of my WAN....
anyone ever run into this before????
thanks
sonny
"microsoft" <turbovw18@hotmail.com> wrote in message
news:%23AsAGI1FEHA.684@tk2msftngp13.phx.gbl...
> the subnets are physically seperated in respect to being at different
> sites... 192.16 and 192.168
>
> but the subnets 192.16.100 and 192.16.101 are inhouse, so they are
> logical... correct?
>
> if i remove the superscope, won't i have to reconfig my dhcp? also,
> wouldn't this require me to change the subnets already mapped? meaning i'd
> have to re-lease all ip's?
>
> as of now the users think everything is normal... so i do not want to
> interrupt their workflow...
>
> thanks for the reply
>
> and sorry for my ignorance.
> "Marc Reynolds [MSFT]" <marcrey@online.microsoft.com> wrote in message
> news:%23rkFh60FEHA.2404@TK2MSFTNGP11.phx.gbl...
> > Are the two subnets physically separated or logically separated? If they
> are
> > physically separated you should not use a superscope. You should remove
> the
> > superscope and you don't need to reboot the DHCP server to do this.
> >
> > --
> >
> > Thanks,
> > Marc Reynolds
> > Microsoft Technical Support
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "microsoft" <turbovw18@hotmail.com> wrote in message
> > news:#dYE4i0FEHA.2980@TK2MSFTNGP09.phx.gbl...
> > > Hello,
> > >
> > > I am in a tight situation here... we are currently rebuilding our
> > domain
> > > to allow clustering and live fail overs to avoid downtime. The people
> in
> > > charge of my company want ZERO downtime in any case... so we are
working
> > on
> > > that.
> > >
> > > in the meantime an issue has developed... please help me with any
> > > recommendations... i will try to spit it all out right here...
> > >
> > > issue at hand
> > > -------------------
> > >
> > > i have a win 2k master server... dealing out dhcp / dns / wins and is
> file
> > > serv / print serv and so on... i have 3 basic subnets... .2.0 .100.0
and
> > > .101.0... 2 is mainly servers and not dealt up with DHCP... i do
however
> > > have a super scope created for 192.16.0.0 but the DHCP range is
> > > 192.16.100.1 - 192.16.101.254 ... it seems that the leases for the 100
> > > subnet were all taken up ... and it also appears that it is not
dealing
> > out
> > > 101 subnet IPs.
> > >
> > > User end is showing no error, just sometimes popping up saying that
the
> > > roaming profile cannot be found and that they are logged on with a
> cached
> > > local.... ipconfig /all shows that it's pulling down a localhost IP...
> > > 192.168.233.x.... a release will release this ip and have no config...
> but
> > a
> > > /renew will return the error.... 'an error occured while renewing the
> > > interface local area connection: access is denied' .... i'm doing this
> as
> > > the network admin account and the local admin account... same error...
> > >
> > > i killed all intersite replication and stopped the dhcp services on my
> > > remote site DC's just to rule them out... the ONLY way to get my
people
> > back
> > > up on the network is to jump them to a new subnet, and MANUALLY set
the
> ip
> > /
> > > mask / gate / dns.... i just picked the subnet 192.16.200.x ...
everyone
> > is
> > > working fine now and is good to go, but that is because we ran around
> for
> > 3
> > > hours manually setting ip adds.
> > >
> > > i've done everything i can think of and have found no solution... no
> > domain
> > > policy set, security policy, group policy... no event log errors or
even
> > > information about anything wrong with DHCP... it thinks that it's
> fine...
> > >
> > > i do not want to kill my super scope and scope out seperate subnets...
.
> > > mainly because i CANNOT reboot this server until friday night or
> > saturday...
> > > so i would like to come to a conclusion... i extended the leases on
DHCP
> > to
> > > avoid people getting dropped... but i would really like to know why
> these
> > > cards are pulling some bogus local IP ... then once dropped not
allowing
> a
> > > network DHCP config.
> > >
> > > Thank you for any responce.
> > >
> > > Sonny
> > > smcmanigle@thorpreed.com
> > >
> > >
> >
> >
>
>
- Next message: Himalaya: "Re: install network monitor"
- Previous message: microsoft: "Re: Please HELP... dhcp / ip / nic issues"
- In reply to: microsoft: "Re: Please HELP... dhcp / ip / nic issues"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|