locked
DHCP Relay Agent problem RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've some problems with Relay Agent on W2k3. My config:

     

    Server1:

    1 NIC

    IP: 10.0.0.1

    DHCP Server running on it. Scope:192.168.0.1-192.168.0.10

     

    Server2:

    2 NIC's

    NIC's 1 address IP: 10.0.0.2

    NIC's 2 address IP: 192.168.0.3

    RRAS with DHCP Relay Agent running on Local Connection2 (192.168.0.3)

     

    Client:

    IP:automatically

     

    I want this client to accuire IP from Server1 (192.168.0.x) by Relay Agent. Unfortunatelly this config won't work. Client don't get IP from Server1. Any ideas?

    • Changed type Bruce-Liu Monday, November 29, 2010 9:33 AM
    Friday, November 19, 2010 12:47 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    You would probably get a better idea of what is going on if you check the DHCP server logs and also run a packet capture on both sides of the RRAS server.  For a DHCP lease to be issued successfully, you'll need to see at least 4 packets: DHCPDISCOVER, DHCPOFFER, DHCPREQUEST, and DHCPACK.

    The DHCP Process: Negotiating a Lease
    http://www.anitkb.com/2010/04/dhcp-process-negotiating-lease.html

     

    Visit: anITKB.com, an IT Knowledge Base.
    • Marked as answer by Bruce-Liu Monday, November 29, 2010 9:48 AM
    Friday, November 19, 2010 2:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I agree with JM. A packet capture would be the best thing to nail down where it's stopping it.

    Also, make sure the Windows firewalls on the server are disabled, as well as any other third party firewalls. Also to take another look at the relay agent to make sure it's set to 10.0.0.1.

    If no firewalls, and the agent's properly configured, maybe it could be a route issue, but I can't see that with the agent on the same machine with interfaces configured to both subnets.

    Ace

    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    • Marked as answer by Bruce-Liu Monday, November 29, 2010 9:48 AM
    Friday, November 19, 2010 8:57 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    You would probably get a better idea of what is going on if you check the DHCP server logs and also run a packet capture on both sides of the RRAS server.  For a DHCP lease to be issued successfully, you'll need to see at least 4 packets: DHCPDISCOVER, DHCPOFFER, DHCPREQUEST, and DHCPACK.

    The DHCP Process: Negotiating a Lease
    http://www.anitkb.com/2010/04/dhcp-process-negotiating-lease.html

     

    Visit: anITKB.com, an IT Knowledge Base.
    • Marked as answer by Bruce-Liu Monday, November 29, 2010 9:48 AM
    Friday, November 19, 2010 2:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I agree with JM. A packet capture would be the best thing to nail down where it's stopping it.

    Also, make sure the Windows firewalls on the server are disabled, as well as any other third party firewalls. Also to take another look at the relay agent to make sure it's set to 10.0.0.1.

    If no firewalls, and the agent's properly configured, maybe it could be a route issue, but I can't see that with the agent on the same machine with interfaces configured to both subnets.

    Ace

    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    • Marked as answer by Bruce-Liu Monday, November 29, 2010 9:48 AM
    Friday, November 19, 2010 8:57 PM