1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Wireless clients are unable to authenticate on Windows 2003

Discussion in 'Networking Issues' started by MRSchu, May 22, 2005.

  1. MRSchu

    MRSchu Network Guru Member

    I have a home network that I have just put a wireless WRT54gs on. I have 8 wireless laptops that are able to access the internet if I allow the WRT54gs to pass DHCP. If I attempt to have the Domain contrller pass DHCP and the WRT54gs act as gateway, which is my goal, the clients are unable to get validated on the domain. I have tried every configurtion I can think of.

    Here is the configuration:

    Autoconfigure IP from ISP
    Local IP set to
    Subnet Mask

    Advanced Routing Settings
    Operating Mode - Gateway
    Static Routing - Set 1 Named - Rubyred
    Destination LAN IP
    Subnet Mask
    Default Gateway

    Windows 2003 Server
    Configured as a DC running the following
    Active directory
    Routing and Remote Access

    Ip configuration
    IP address
    Subnet mask

    Any help would be greatly appreciated.
    Thank you
  2. Guyfromhe

    Guyfromhe Network Guru Member

    try taking that static route out, it's not even a proper route...
  3. MRSchu

    MRSchu Network Guru Member

    Much love on the internal network side.......no love on the internet side.....
  4. MRSchu

    MRSchu Network Guru Member

    I am desperate to get these computer to connect. Is there anyone who has any suggestions?

    Wireless clients recieve

    "The system cannot log you on now because the domain RUBYRED is not available"
  5. Jarhead1899

    Jarhead1899 Network Guru Member

    MRSchu: I am in a similiar situation.

    I would not use a static route. Ensure your DHCP server on your router is disabled. The only way I was able to join my domain was to assign all static IPs to my clients.

    Assign your Active Directory DNS IP address to your clients. However, you clients will not be able to surf, unless your DNS has a forwarding lookup enabled (or secondary DNS server). This is my current problem. I use DnyDNS to resolve my domain name, now if I want to surf I need to subscribe to the DnyDNS Secondary DNS service. (So says the DNS techs)

    I was able to join my workstations to the domain using just the Active Directory DNS server. As noted above I was not able to surf.

    When my ISP DNS is listed as an alternate, or the DynDNS recursive lookup is used I can surf, but I cannot find the Active Directory server. (Microsoft KB states this is a DNS problem, hence my thoughts on having to use a Secondary DNS server)

    I think the only resolution I have left is to subscribe to the Secondary DNS service from DynDNS. Without this the DNS service is unable to resolve names because my ISP DNS will not allow any forwarding from DNS servers behind it.

    Hope this helps some. Maybe we can get an answer.
  6. ReDFlaG

    ReDFlaG Network Guru Member

    try this:

    on your router:
    set up isp stuff
    don't use advanced routing (remove your static route)

    W2k3 srv
    why do you use wins?
    why do you use rras since your w2k is just here for DC, dhcp, DNS ?
    (gateway / NAT is your linksys)

    check your subnet, you wrote instead of
    set the first DNS of the w2k to be, then second one to be
    check your DHCP:
    - make the proper reservation for the router and the server (exclude ips)
    - you have option to set and to 'tell' to your clients that the gateway to use is
    - You had to tell them the DNS too. first one then

    after all that do your clients receive an ip with the correcte settings (dns, gateway...)?

    i hope this help and that i have well understood what you want to do...

Share This Page