Tech Support Forum banner
Status
Not open for further replies.
1 - 5 of 5 Posts

·
Registered
Joined
·
48 Posts
Discussion Starter · #1 ·
Not sure what happened between last night and today but I am having connection issues with my server named "NS4DC". I am able to remote into the server from a local client but it is not communicating with another domain controller. It cannot connect to the internet either. Below is some information about "NS4DC".

It is an additional domain controller for a Windows Server 2003 domain. The server is only used as a DC and RRAS for VPN connections. There are two ethernet cards in use. Below is a result of "ipconfig /all".

Do you have any suggestions to resolve problem?

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : ns4dc
Primary Dns Suffix . . . . . . . : local.nira.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : local.nira.com
nira.com

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR GA311 Gigabit Adapter
Physical Address. . . . . . . . . : 00-0F-B5-FB-33-B4
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.110
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.100
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-C0-9F-1F-FE-82
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.104
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.100
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Documents and Settings\Administrator>
 

·
TSF Emeritus
Joined
·
16,395 Posts
You have both nics in the same subnet. You can't route [since there is no need to] between two ips in the same subnet.

Normally the setup would look like this

internet<>router<>nic1[server]nic2<>switch<>pcs
internet<>subnet 1<>[server]<>subnet 2
 

·
Registered
Joined
·
48 Posts
Discussion Starter · #3 ·
It has worked like that in the past.

I just installed IIS as a new role for that server because I was going to install Windows Software Updates Services. Would that have caused the problem?

Not sure what you mean by the following:

internet<>router<>nic1[server]nic2<>switch<>pcs
internet<>subnet 1<>[server]<>subnet 2
Are you talking about the cables?

What is "pcs"?
 

·
TSF Emeritus
Joined
·
16,395 Posts
Usually yes because you would not have people vpn to your lan but to your server.

Per the diagram I provided you have

Internet access coming to one nic in the server. That is in one subnet
Your lan connection to the server is via another nic in the server and is on a different subnet than the one for internet.

RRAS ROUTES between the two subnets while at the same time providing VPN access to the server via the internet connected nic. You can configure RRAS to provide just Server access or server and lan access.

Might want to spend a little time at Microsoft.com and technet reviewing proper RRAS configuration scenerios.
 
1 - 5 of 5 Posts
Status
Not open for further replies.
Top