On July 28, 2004 12:47, Mike Roest wrote:
> Martin Glazer wrote:
> | I know I shouldn't be doing this and yes, I'm sure it does break some
>
> RFC's,
>
> | but I can see lots of advantages in something like this. Basically it
>
> is a
>
> | kind of plug-and-play for networking.
>
> That's what DHCP is. Plug and P{lay for networkings
>
Only if your computer is setup to use dhcp - there are many places that still
use static IP's.
> | I have heard of some such devices being used in the hotel industry in
>
> order to
>
> | provide internet access to the hotel rooms, but haven't found anything
>
> else.
>
> I've never heard of anything like this. Every hotel I've gone to that
> has ethernet has had some nice printed out documentation on setting the
> computer to DHCP.
>
> What's the problem with having some instructions available for people,
> on howto configure/enable DHCP for the 4 versions of windows and 2 mac
> os versions?
No problem at all, just in my experience, people are always quicker to make a
call than to read some set of instructions and figure something out. The
instructions also have to be available all the time (not lost or removed),
you may need them in a multitude of languages (with associated screenshots),
OS permissions to change network settings, you have to ensure that the
network configuration can be set back to what it was originally, etc.
A solution that handles 99% of the potential problems without any user
involvement appears to me at least, the way to go....
Martin
_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
