This is:
(1) An FYI to those who may come after to help them miss the pitfalls
-I- had.
(2) A request for information - if these effects are caused by
mis-configuration - PLEASE let me know!
Now, on to the "REAL untold story!"
STN (in a dial-on-demand dial-up connection) seems to require that you
set up -BOTH- DNS and DHCP.
(a) Without DNS, STN will not dial.
(b) Without DHCP, STN will not route to the outside network, even if
you have another DHCP server generating the same settings.
This is interesting. What if you wanted to implement STN on a system
that already had several dedicated DNS servers, and was statically
addressed. . . It seems like it is guaranteed to fail!
I have a suspicion that this is something like a design decision in the
origninal implementation:
I suspect that the original design for STN was to implement a
"quick-and-dirty" (OK, not so dirty!!) gateway between an
un-sophisticated "home" or "office" net and the void. Since the
"typical" home net is likely to be using something like NETBEUI in
peer-to-peer, (or maybe TCP/IP, statically assigned in a peer-to-peer
arrangement), the addition of STN as both a DHCP and DNS server is not a
huge issue. It was not expected to be installed in a "larger" network
environment with existing DNS/DHCP server(s). Right?
I also suspect that the original designers of STN did -NOT- expect the
variety of uses it would be put to!
Jim
--
Visit http://www.ShareTheNet.com for info about ShareTheNet
Visit http://www.topica.com/lists/sharethenet for info about this list
________________________________________________________________________
Start an Email List For Free at Topica. http://www.topica.com/register
