[TriLUG] NT DHCP Server woes

[Christopher Knowles]

The Logs on the NT side don't claim that anything is amiss.  I've narrowed it 
down to one of two things, 

1) the NT server was originally a 3.51 server, and I've seen a bunch of old 
posts on Google about problems getting those to talk correctly.  The 4,0 was 
just an upgrade, and there is some other weird things that make me think that 
perhaps it's just cranky.

2) The Cisco Swtich we have in between seems to be forgetting that the linux 
box is there.  When I boot the linux box everything is just fine, but when I 
let it alone for awhile and try to ping the NT server, I get nothing unless I 
ping the linux box first from the server, then data will flow.  (Obviously 
this is after assinging a static IP.)

Thanks for at least letting me know that something is WAY out of spec 
somewhere.

CJK

On Friday 18 January 2002 12:47 am, Tom Bryan wrote:
> On Friday 18 January 2002 09:35 am, Christopher Knowles wrote:
> > We have an NT 4.0 Server doing DHCP serving for us.  Due to the Paranoid
> > climate, moving that service is NOT an option, believe me I've tried. 
> > The problem is that I can't get Linux boxen to use that DHCP server.
>
> I've never had a problem at my office.  I hook the laptop up to the
> network, turn it on, and it grabs an IP.  Whenever I've taken it from home
> to office without shutting down, I explicitly ifdown the interface before
> unplugging and then ifup the interface once I'm connected to the new
> network.
>
> > them time out.  (Pump, DHCPcd)  Is there anything special that one has to
> > do to the server to get it to serve properly,
>
> What do the logs on the NT side say?  Is it even seeing the request?
> Anything intereseting in the Linux machine's logs?
>
> > This is only a problem for me because I have started lugging a laptop to
> > home and work, and would like to plug in the built in NIC without
> > changing anything or even rebooting, and dang it, it should work.
>
> Does it work if you shut down and then boot up after plugging into the
> network at work?
>
> > Speaking of Paranoid... The lack of DHCP ability was actually used to
> > shoot down the use of Linux, even though it was to be a server.  "If they
> > can't get DHCP to work, who knows what else might go wrong"  Grrr...
>
> Ew.  The IT guys at work know next to nothing about Linux (and I know next
> to nothing about NT), but that wasn't a problem since it just worked.  No
> tweaking or troubleshooting involved.
>
> ---Tom
> _______________________________________________
> TriLUG mailing list
> http://www.trilug.org/mailman/listinfo/trilug