Private in-house domain
    Tech Writer 
    TechWtr at handspun.com
       
    Tue May 15 20:10:54 EDT 2007
    
    
  
Thanks for all of the suggestions, so far.  I'm going to look at them more 
carefully, and see if I can fix this by changing my routing table.
Both replies suggested that I change my internal domain to a 192.168.1.x IP 
range (to match the Linksys) or change my Linksys router to the 10.25.1.x 
range (to match my mini-domain).  Actually, I'm aware that either of these 
will work.  My goal was to try NOT to do this.  I purposely wanted my "mini 
domain" to have a different IP range, since I will eventually have to set 
this demo up in a larger lab.  When I move my sample, I will not be able to 
have any control over the DHCP server in the larger lab environment (to 
change its IP address) nor will I be able to define my own IP addresses 
(which my domain server will need to do) in the range that the existing DHCP 
server already owns.
So, my goal is to try to find a way to set up a mini-domain of 10.25.1.x 
addresses within a LAN that's already set up with DHCP-assigned 192.168.1.n 
addresses.
I hope that makes sense.
>> ...  I'm not familiar with
>> CentOS, so I don't know if there's an easy way to do that.
>>
btw... CentOS is just Red Hat Enterprise Linux, with a different logo.
Peg 
    
    
More information about the gnhlug-discuss
mailing list