"Marcio Peixoto" <> wrote in message news:56EBA836-A958-4791-BBAF-...
> Good morning guys. I am an annoying problem on a client. He created an
> internal network with the name www.meudominio.com.br. So far no problem
> because there were estimates of placing it on the Internet. He created a
> field with the same name and the internal clients can not access it for the
> internal network. What to do to solve this uncomfortable problem ?
Hello Marcio,
Do you mean the website is being hosted internally, and the internal folks cannot access the internal web server because of the identical public/private domain name?
Simple fix:
Assuming the domain name of the website is the same as your internal name, you can simply create a www record under the internal zone, and provide it with the "external" (in your case, or the DMZ) 192.x.x.x address of the website. Keep in mind, to access it by
http://domain.local (or whatever the internal domain name is) without the www in front of it, will take a few more steps because that is the DC's LdapIpAddress record. If you need to make that work, that is a little more involved because you can't alter that record in DNS or it will affect DC functionality. H owever, you can go into IIS' default website properties on the DC, and configure a redirection to
www.domain.local to make it work. Just make sure that doesn't interfere with any SBS sites if you decide to do that otherwise just tell your folks to always use the www in front of the URL.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly. Please
check
http://support.microsoft.com for regional support phone numbers.
"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay
Similar Threads
Linear Mode
