[CUWiN-Dev] Fwd: rev 4074...

[dan blah]

i fixed it with mind force.  i had them unplug the server from their
internal lan and put it in their dmz.  the dmz is set up to have the
router from their t1 give dhcp addresses when the t1 is there (it's
not so there is no dhcp server in the dmz).  since the node isn't
getting a dhcp reply it's default route is the imc node.  i am going
to meet with them first thing monday morning when their t1 is
activated to make sure everything goes over good for us.

On 7/15/06, David Young <dyoung at pobox.com> wrote:
> On Sat, Jul 15, 2006 at 12:29:44AM -0500, tom wrote:
> > ----- Original Message -----
> > From: "David Young" <dyoung at pobox.com>
> > >This node is getting a DHCP lease with a default route.  It is acting
> > >just as expected.  It must be plugged into the same ethernet segment as
> > >a DHCP server.
> > >
> > >Dave
> > >
> >
> > I think what must have happened is that the people moving in to the 115 W.
> > Main building trying to get temporary internet access until their T1
> > arrives must have plugged something in that had a DHCP server on it. So
> > ironically enough when I called them to let them know that while I had
> > resolved the hardware issue I had spoken of earlier, there was still a
> > software problem, they were actually causing it. Looking at the network
> > remotely now everything looks great - all 4 of the nodes in range are
> > running 0.7.0rc1 and have internet access (including the library, once
> > again). They must have unplugged whatever it was at 115 W. Main that was
> > causing problems, unless one of us did something.
>
> Dan tells me he fixed it.
>
> Dave
>
> --
> David Young             OJC Technologies
> dyoung at ojctech.com      Urbana, IL * (217) 278-3933
> _______________________________________________
> CU-Wireless-Dev mailing list
> CU-Wireless-Dev at lists.cuwireless.net
> http://lists.chambana.net/cgi-bin/listinfo/cu-wireless-dev
>


-- 
Daniel