Jump to content
RESET Forums (homeservershow.com)

WSE R2 Essentials use dedicated NIC for DHCP


Recommended Posts

From Server:

Windows PowerShell
Copyright © 2013 Microsoft Corporation. All rights reserved.

PS C:\Users\chad> tracert google.com

Tracing route to google.com [173.194.33.105]
over a maximum of 30 hops:

  1    40 ms    25 ms    22 ms  CPE-76-178-18-129.natmtn.res.rr.com [76.178.18.129]
  2    15 ms     9 ms    11 ms  ge1-1-4.cralid-rtr1.cralid-rtr1.natnow.rr.com [65.28.217.57]
  3    20 ms    17 ms    17 ms  ae21.sstswa5802r.natnow.rr.com [65.28.218.248]
  4    22 ms    30 ms    18 ms  107.14.19.114
  5    38 ms    38 ms    38 ms  bu-ether11.sttswa5800w-bcr00.tbone.rr.com [66.109.6.16]
  6    40 ms    35 ms    38 ms  ae-2.cr0.sjc10.tbone.rr.com [66.109.9.44]
  7    35 ms    37 ms    37 ms  ae-0-0.pr0.sjc10.tbone.rr.com [66.109.6.141]
  8    54 ms    57 ms    55 ms  74.125.48.253
  9    37 ms    36 ms    37 ms  209.85.249.3
10    37 ms    36 ms    36 ms  209.85.246.253
11    40 ms    38 ms    36 ms  216.239.49.198
12    39 ms    36 ms    40 ms  209.85.248.221
13    35 ms    37 ms    36 ms  66.249.94.196
14    36 ms    36 ms    36 ms  209.85.244.63
15    37 ms    36 ms    36 ms  sea09s16-in-f9.1e100.net [173.194.33.105]

Trace complete.

 

When I do tracert "servername" or tracert "servername.local" it shows the single hop to the server.

From Workstation:

 

Unable to resolve target system name google.com.

Link to post
Share on other sites
  • Replies 49
  • Created
  • Last Reply

Top Posters In This Topic

  • ChadRT

    24

  • jmwills

    13

  • jem101

    6

  • ikon

    4

Top Posters In This Topic

jmwills

That first hop should be your local DHCP server and it looks like that is your external address so yes, none of the clients are getting an IP.

 

C:\>tracert google.com

Tracing route to google.com [74.125.21.138]
over a maximum of 30 hops:

  1     3 ms     5 ms     4 ms  router.asus.com [192.168.1.1]
  2    29 ms    17 ms    21 ms  96.120.19.13
  3    39 ms    14 ms    15 ms  te-9-3-ur02.huntsville.al.hunts.comcast.net [68.
85.33.97]
  4    16 ms    21 ms    16 ms  xe-0-0-8-0-ar04.huntsville.al.hunts.comcast.net
[68.85.227.5]
  5    23 ms    27 ms    25 ms  xe-19-1-3-0-ar01.b0atlanta.ga.atlanta.comcast.ne
t [162.151.13.34]
  6    23 ms    20 ms    20 ms  he-5-15-0-0-10-cr01.56marietta.ga.ibone.comcast.
net [68.86.87.201]
  7    48 ms    35 ms     *     as15169-1-c.56marietta.ga.ibone.comcast.net [23.
30.206.146]
  8    21 ms    23 ms    22 ms  72.14.233.54
  9    24 ms    29 ms    30 ms  66.249.94.6
 10    44 ms    44 ms    19 ms  64.233.175.12
 11     *        *        *     Request timed out.
 12    31 ms    24 ms    24 ms  yv-in-f138.1e100.net [74.125.21.138]
 

Link to post
Share on other sites

I found this!  And if the DNS server cannot start then "Houston we have a problem..."  could this be causing the mess I have now?

 

 

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4013
Date:  3/4/2014
Time:  2:28:37 PM
User:  N/A
Computer: xxxx.xxxx.local
Description:
The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


And this one!  Holy cow so if the DNS server cannot start or bind to 192.168.1.1 which is the default gateway for the clients then it would cause them not to have internet?

 

 

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 408
Date:  3/2/2014
Time:  3:32:44 PM
User:  N/A
Computer: xxxx.xxxx.local
Description:
The DNS server could not open socket for address 192.168.1.1.
Verify that this is a valid IP address for the server computer.  If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces.  Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error.  In that case remove the DNS\Parameters\ ListenAddress value in the services section of the registry and restart.)

If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.

For more information, see "DNS server log reference" in the online Help.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Link to post
Share on other sites
jmwills

No. It would not allow DNS resolution. Accessing the internet is about making connections.

DNS only turns IP addresses into friendly names.

Link to post
Share on other sites
timekills

No. It would not allow DNS resolution. Accessing the internet is about making connections.

DNS only turns IP addresses into friendly names.

 

The only part that throws me is his nslookup does show trying to reach 8.8.8.8, but he says he can't even ping 8.8.8.8.  Even without DNS resolution he should be able to ping the IP. If it were truly a DNS problem, he should be able to statically assign the DNS in his NIC's settings and resolve URLs. That's why I suggested that earlier to either confirm or rule out a true DNS problem.

 

Clearly he isn't resolving the names to IPs, but the lack of any internet connectivity would make me look elsewhere. Of course, the rule of thumb is after layer 1, blame DNS so...

Link to post
Share on other sites
jmwills

But still, that first hop should be his local DHCP server and it's not.  This is why the clients are not pulling an address.  There is a configuration issue somewhere either in cabling or RRA.

 

If the server is being used as the DHCP server, once cable should be coming from the router/modem WAN port  to the NIC where DHCP is bound.  The "WAN NIC" on the server should go back to the LAN port(s) on the router as would any other NIC needing external access.

Link to post
Share on other sites

We have three possible issues here 

1) DHCP is not working correctly on the LAN side

2) DNS is not working correctly on the LAN side

3) Routing internet traffic between the networks on the server is not working properly.

 

Of these 3) is going to be the hardest to fix, so we'll start with checking that out.

 

On one of your client PCs, statically set the following IP address parameters

IP address : 192.168.1.99

Subnet mask : 255.255.255.0

Default gateway : 192.168.1.1

 

Set DNS to be 8.8.8.8 (this doesn't really matter for this test)

 

By the way I am assuming that .99 is not being used for anything else.

 

Then on the client side open a command prompt or powershell and try

 

tracert 8.8.8.8 and see if it gets out to the internet - if not (ie it gives out at the first hop) then we have a RRAS issue and nothing is going to work until we get that working.

 

If it does go out ok, then try 

 

tracert www.google.com

 

and see what that returns. If nothing then we have a DNS issue to look into.

 

 

John

 

Ah  I've just read back some of your earlier posts, if the RRAS role is installed on the server then it shouldn't have a default gateway entered on the LAN side - only the WAN side nic should have a gateway address.

 

So the LAN nic should have

 

IP address 192.16.1.1

Subnet  255.255.255.0

Gateway address : leave this blank

 

DNS - well if the server also has the DNS role installed then this should be 127.0.0.1 or 192.168.1.1 (either is OK)

Edited by jem101
Link to post
Share on other sites

But still, that first hop should be his local DHCP server and it's not.  This is why the clients are not pulling an address.  There is a configuration issue somewhere either in cabling or RRA.

 

 

I would assume that since I was able to move files from computer to computer and access the server from the client workstations that cabling would be ruled out completely?  I am able to ping the server, ping other workstation from a workstation, ping workstation from server and the workstations receive an IP from DHCP. 

 

 

 

On one of your client PCs, statically set the following IP address parameters

IP address : 192.168.1.99

Subnet mask : 255.255.255.0

Default gateway : 192.168.1.1

 

Set DNS to be 8.8.8.8 (this doesn't really matter for this test)

 

By the way I am assuming that .99 is not being used for anything else.

 

Then on the client side open a command prompt or powershell and try

 

tracert 8.8.8.8 and see if it gets out to the internet - if not (ie it gives out at the first hop) then we have a RRAS issue and nothing is going to work until we get that working.

 

If it does go out ok, then try 

 

tracert www.google.com

 

and see what that returns. If nothing then we have a DNS issue to look into.

 

 

So the LAN nic should have

 

IP address 192.16.1.1

Subnet  255.255.255.0

Gateway address : leave this blank

 

DNS - well if the server also has the DNS role installed then this should be 127.0.0.1 or 192.168.1.1 (either is OK)

 

This is all really good stuff were talking about here.  Things I have not tried.

Link to post
Share on other sites

John,

 

I followed your steps.  One thing I did have was in the LAN adaptor I had statically set the DNS entries to google's but I did have the gateway empty.  Now that I have the LAN running 192.168.1.1 as the primary DNS server here are the results.

 

 

 

(BOTH OF THE FOLLOWING HAVE STATIC .99 AS PER INSTRUCTIONS ABOVE)

 

Client Computer Configured for Google DNS:

ping 192.168.1.1 = good result

tracert 8.8.8.8 = first hop thru the server and each consequtive hop is "Request timed out."

tracert google.com = Unable to resolve target system name google.com.

 

Client Computer Configured for Server IP as DNS:

tracert = all requests time out

tracert google.com = Unable to resolve target system name google.com.

Link to post
Share on other sites

But still, that first hop should be his local DHCP server and it's not.  This is why the clients are not pulling an address.  There is a configuration issue somewhere either in cabling or RRA.

 

If the server is being used as the DHCP server, once cable should be coming from the router/modem WAN port  to the NIC where DHCP is bound.  The "WAN NIC" on the server should go back to the LAN port(s) on the router as would any other NIC needing external access.

 

I have three NIC's...

  • WAN - Connected to TW cable modem with an assigned static IP from TW (internet works good on server directly)
  • LAN - Connected to a 16 port switch
  • INT - Disabled NIC built into the motherboard

Each of the two client computer workstations are connected to the switch, workstations receive a DHCP assignement from the server those workstations are able to file share between themselves, view server intRAnet pages (remote access pages) and also respond to pings from server and eachother.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...