Dak,
Your problem yesterday was unrelated to what everyone else saw this
morning. As I recall, the report was that DHCP assigned a 192.168.x.x
IP address. I can assure you that our campus DHCP service doesn't do
such an assignment. I have yet to see a 192.168.x.x IP assignment that
didn't come from a local source, most often a wireless router that is
incorrectly connected into the building network. Those are generally
pretty easy to track down, if we can get details on the DHCP server
which is assigning the IPs.
Doug
On Wed, Jan 21, 2009 at 09:54:50AM -0500, Aldrich, Dak wrote:
> It's kinda funny... I started seeing this problem yesterday on campus.... DHCP was issuing incomplete information.... And the only thing ATS could come up with was "You must have a rouge DHCP server somewhere in your building.". Why is that that the pat answer to every problem I call with?
>
> -dak
>
>
>
> On 1/21/09 9:35 AM, "John B. Johnston" <[log in to unmask]> wrote:
>
> Lee Duynslager wrote:
> > All of my users systems that have DHCP assigned addresses can't
> > traceroute past a router in the computer center. The systems that
> > have static IP's can get out to the internet.
> >
> > Is that the case for all the campus?
> >
> >
> > LD
> Yes, that's the case here. Apparently it's a campus-wide problem.
>
> John
>
> --
> John B. Johnston
> 505 Biochemistry Building
> East Lansing, MI 48824
>
> Phone: (517) 432-7177
> Email: [log in to unmask]
>
>
> ********************
> * dak aldrich
> * network admin
> * college of music, msu
> * [log in to unmask]
> * 517.432.5045
> * comit.music.msu.edu
>
--
Doug Nelson, Network Manager | [log in to unmask]
Academic Technology Services | Ph: (517) 353-2980
Michigan State University | http://www.msu.edu/~nelson/
|
