Re: Moving from DMZ to internal network
- From: "Danny Sanders" <DSanders@xxxxxxxxxxxxxxx>
- Date: Fri, 9 May 2008 10:00:19 -0600
Depends on where it's authenticating now. If it's a member of a domain that
resides only in the DMZ then you will have to open ports in the firewall for
the SQL server to talk to the DMZ domain controller, If the SQL server is a
member of the internal domain and it was using an internal DC to
authenticate to then you can just move it inside and close the ports it was
using to talk to the internal DC.
hth
DDS
"Luiz" <Luiz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CE7A3A91-8986-47B5-BFB9-2422B2F7B1A8@xxxxxxxxxxxxxxxx
Hi Danny,
thank you for your response.
And about authentication?
Thanks again.
Luiz
"Danny Sanders" wrote:
Besides the IP address?
Firewall settings?
hth
DDS
"Luiz" <Luiz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7ACB0433-DD74-4720-BCCF-D7F9A3C6A37E@xxxxxxxxxxxxxxxx
Hi,
I have a Windows Server 2003 with SQL Server in a DMZ.
I intend to migrate it to my internal LAN, with a Domain Controller.
Must I change anything in the server?
Thanks.
Luiz
.
- Follow-Ups:
- Re: Moving from DMZ to internal network
- From: Luiz
- Re: Moving from DMZ to internal network
- References:
- Moving from DMZ to internal network
- From: Luiz
- Re: Moving from DMZ to internal network
- From: Danny Sanders
- Re: Moving from DMZ to internal network
- From: Luiz
- Moving from DMZ to internal network
- Prev by Date: MSMQ over HTTPS fails
- Next by Date: Server Freezing Up
- Previous by thread: Re: Moving from DMZ to internal network
- Next by thread: Re: Moving from DMZ to internal network
- Index(es):
Relevant Pages
|
Loading