Did you have the IP of server 1 hardcoded in the Linksys?

On Tue, Nov 16, 2010 at 12:28 PM, David Lum <[email protected]> wrote:

>  Small network, subnet is 25-bit. Been fine for years, no recent changes,
> except as described below.
>
>
>
> ServerA: 2003 R2 is a DHCP server (also DC, DNS, file/print etc). ServerA
> sits on hardware that will get flatted and 2008 R2 on it, so  I stand up
> ServerB, again with 2003 R2. I make it a DHCP server, same scope and
> settings, authorize it, etc. Network was fine with this thing forever.
>
>
>
> I turn off DHCP of Server A so clients will start getting IP’s from Server
> B and it works. Sometimes. Other times clients get an IP from 192.168.1.1.
> Some troubleshooting finds a Linksys router that I had totally forgot about
> using in just “switch” mode. WAN side unused, just the 5 port switch side
> utilizes (I don’t even remember doing it, but I am the only guy who does IT
> stuff at this place, and in hindsight I can’t believe this hadn’t been only
> a temp solution). I bought a proper switch and solved the issue.
>
>
>
> My curiosity is why wasn’t it an issue when ServerA was the DHCP server?
> The DHCP lease was set for 8 days on ServerA so it’s not like in the last
> several months the PC’s hadn’t been doing DHCPDISCOVER several times…
>
> *David Lum** **// *SYSTEMS ENGINEER
> NORTHWEST EVALUATION ASSOCIATION
> (Desk) 971.222.1025 *// *(Cell) 503.267.9764
>
>
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to