Gents....
We use ghost for imaging client machines at work. We do it on a seperate lan (vs. the production network) so as to keep traffic off of the production network. I build reference machines on the private lan and as is the way with windows machines, I need to get out to the world to get updates/patches, etc. (windowsupdate.com). So what I did was....
Slap an SME 5.6 server in place, created an ibay to house the image files, plug the external nic into our production network and pointed to our inhouse dns server. Works great... for the most part. Question though: We (the helpdesk) keep 99% of all of the software that we use for desktop installations out on one of the production servers. From any machine on the production network, we can just click START | RUN | \INSTALLSRV\INSTALLSW
and get to it. I would like to be able to get the same sort of name resolution working for the private lan space on the inside of the SME box. I can get to the production resources, but I have to use IP to get to 'em, ie; 'INSTALLSRV' is really 172.16.1.69...
Getting out to the web is no problem, ie; www.google.com gets me to google. It is just internal/production machines that I can see unless I use fqdn against them. ( I can't ping INSTALLSRV, but I can ping INSTALLSRV.OURNET.NET )
What (or can I? - I think I can) do I have to do to make this work like I would like it to? (See the production machines by short/host name)
Thanks guys...
-=- jd -=-
1 Replies
342 Views