Re: Adding new DC help!!!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi
You should reconsider using a DC on FW, or in a Multihomed DC, why? Because
represents security issues for the DC and all information on it, and also
can lead you to a lot of problems like this that you're having now.
start by:
Name resolution and connectivity issues on a Routing and Remote Access
Server that also runs DNS or WINS
http://support.microsoft.com/?id=292822
Symptoms of multihomed browsers
http://support.microsoft.com/kb/191611/


--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Skc" <Skc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:05026905-8F7F-41CA-A360-773834336690@xxxxxxxxxxxxxxxx
Yes - is that a problem? Furthermore, I am using a hardware firewall (ISA
is
not my primary filewall to the outside world!).

S

"Jorge Silva" wrote:

Hi

Before starting to help you....
Is the DC running on ISA server?


--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Skc" <Skc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:13429B4E-D7FD-460A-9EBD-796A9097560E@xxxxxxxxxxxxxxxx
This is probably really silly, but here is my situation:

I have three new PowerEdge 2800 Servers:

1. A DC with x2 NICs as it is running ISA2004 behind a Watchgaurd
firewall
NIC1 - LAN: 192.168.16.2, 255.255.255.0, no gateway,
DNS=192.168.16.2
NIC2 - WAN: 192.168.111.4, 255.255.255.0, gateway=routerIP,
DNS=DNS
from ISP. This all works fine, DC can browse the web and ping
outbound
the other two servers (see IP addresses below)

2. A MailServer with x2 NICs, one enabled and one disabled
NIC - LAN: 192.168.16.3, 255.255.255.0, no gateway, DNS=192.168.16.2
I cannot join this to the DC as an additional DC. I have tried
DCPROMO
but
it keeps saying TIMEOUT_ERROR. Furthermore, I cannot ping the DC
(1)
above
on IP 192.168.16.2.

3. Same problem as (2) with a FileServer with x2 NICs, one is disabled
NIC - LAN: 192.168.16.4, 255.255.255.0, no gateway, DNS=192.168.16.2
I cannot join this to the DC as an additional DC. I have tried
DCPROMO
but
it keeps saying TIMEOUT_ERROR. Furthermore, I cannot ping the DC
(1)
above
on IP 192.168.16.2.

Please help - as I am blowing my brains out!

All machines are brand spanking new. I tried DCPROMO and made one of
the
servers a DC within itself (i.e. sparate) but demoted it again. This
was
Server (2).

I would appreciate some advise, as something is not correct here.

S






.

Relevant Pages

  • Re: RDP can not logon error
    ... Tracert & Ping to dc on the same subnet as the server that is having trouble. ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • Re: Cannot connect to Server
    ... Test 1 - the clients can ping one anotehr ... gpupdate/force - reboot both client and server - ping to server from client ... Suggestion 2 - ping to server works when running safe mode with networking ...
    (microsoft.public.windows.server.sbs)
  • Re: The specified network name is nolonger available
    ... My server is named FS1. ... > ping \\fs1 and I will get a successful return. ... I still can access the drives marked ... What is the point in these permissions as they can be bypassed by mapping ...
    (microsoft.public.win2000.networking)
  • Re: RDP can not logon error
    ... ping and tracert to the dc in that remote site (where this system ... Tracert & Ping to dc on the same subnet as the server that is having ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • RE: Unable to ping client2
    ... I understand that the server box can not ping one ... client workstation after upgraded to SBS 2003 SP1. ... Reboot the SBS Server. ... On the client workstation, run "ipconfig /release" and then run ...
    (microsoft.public.windows.server.sbs)