In news:(E-Mail Removed) ups.com,
pbd22 <(E-Mail Removed)> typed:
> hi.
>
> I am really having a hard time figuring out my Windows Server 2003
> network
> setup and i think i have gotten myself quite confused. I have been
> trying to install exchange server 2003 on a stand-alone server - ARIA.
> but, when i run DCDiag i am told that network connectivity failed. so,
> that started it. i have since tried to sort out my network and i think
> i need some help at this point. i think i may be getting confused over
> my router's ip and the gateway to my router's
> ip (fugue: 192.168.0.101).
What do you mean by "gateway to my router's IP" ?
Generally - you have a default gateway IP address defined in the
server/computers' IP config - and that's the LAN IP of your router.
> I'd appreciate some specific instructions
> on how to resolve my problem.
>
> I have included as much relevant information as possible below
> (apologies if it is information overload).
A bit - but that's OK. :-D
>
> The HOSTS file for both computers is below:
A HOSTS file is not relevant - if you have AD you need functional DNS.
Make sure your servers & all clients specify only the internal DNS server IP
(probably your domain controller - AD-integrated DNS) in their IP config -
no external addresses at all. The forwarders or root hints used by the
internal DNS server are the way that requests for non-local name resolution
will be handled.
HOSTS files are to be avoided.
>
> HOSTS file on Gateway-Server and Aria
>
> 127.0.0.1 localhost
> 192.168.0.101 fugue (this was intended to be the door to the router)
> 192.168.0.100 aria
> 192.168.0.1 gateway-server (this is the router's IP)
What do you mean? What is your DC's name and IP address? Your router is not
relevant....why would GATEWAY-SERVER not specify the IP address of your DC?
Anyway, ditch HOSTS, as I said.
>
> Below Is the result of DCDiag. As you can see, connectivity between
> ARIA and the Domain
> Controller fails. The command was "DCDiag /s: fugue".
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\GATEWAY-SERVER
> Starting test: Connectivity
> The host
> 67678ec1-2b00-47b2-ae20-0aada49a1ac2._msdcs.parchmentmedia.com could
> not be resolved to an
> IP address. Check the DNS server, DHCP, server name, etc
> Although the Guid DNS name
>
>
> (67678ec1-2b00-47b2-ae20-0aada49a1ac2._msdcs.parchmentmedia.com)
>
> couldn't be resolved, the server name
>
> (gateway-server.parchmentmedia.com) resolved to the IP address
>
> (192.168.0.1) and was pingable.
What is your DC's name and IP?
> Check that the IP address is
<snip>
>
> HERE IS IPCONFIG ON GATEWAY-SERVER:
>
> Windows IP Configuration
> Ethernet adapter Public Network:
> Connection-specific DNS Suffix . :
> Autoconfiguration IP Address. . . : 169.254.52.15
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . :
> Ethernet adapter Local Area Connection 2:
> Connection-specific DNS Suffix . :
> Autoconfiguration IP Address. . . : 169.254.6.78
That's bad. What is this NIC connected to? Disable any NIC not in use, in
your Device Manager - and use static IPs on your servers. DHCP is for
clients.
>
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . :
>
> Ethernet adapter Local Network:
> Connection-specific DNS Suffix . : parchmentmedia.com
> IP Address. . . . . . . . . . . . : 192.168.0.101
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.1
>
Where's your DNS server IP?
> HERE IS IPCONFIG ON ARIA:
>
> Windows IP Configuration
>
> Ethernet adapter Local Area Connection:
> Connection-specific DNS Suffix . : parchmentmedia.com
> IP Address. . . . . . . . . . . . : 192.168.0.100
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.1
You're missing DNS here too.
> HERE IS MY ROUTING TABLE ON GATEWAY-SERVER:
>
> IPv4 Route Table
> ================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10003 ...00 40 05 3d 89 61 ...... Realtek RTL8139 Family PCI Fast
> Ethernet NIC
> 0x10004 ...00 20 78 11 f3 69 ...... Linksys LNE100TX Fast Ethernet
> Adapter(LNE100TX v4)
> 0x10005 ...00 e0 18 02 92 d6 ...... Intel 8255x-based PCI Ethernet
> Adapter (10/100)
Why do you have three NICs in there? I'm really a bit confused as to your
setup/topology.
<snip>
> How should i set up my network so ARIA can succussfully connect to the
> Domain Controller? I thank you for your help in advance.
Again, I don't know what you've got/are trying to do, specifically - but
basics:
1. One NIC per server - with a static IP (and frankly I'd use lower IP
addresses - I tend to use .1 - .50 for statics on small networks, with .1
for routers
2. All servers/clients specify only the internal DNS server - no public IPs,
not your router's LAN IP.
3. No HOSTS files should be needed at all
4. All servers/clients should be using parchmentmedia.com as their DNS
suffix, and should be registered in DNS on your internal DNS server (again,
likely GATEWAY-SERVER presuming it's your DC).
|
Similar Threads
Linear Mode
