Wireless Connection to Internal Network

Home Forums Microsoft Networking and Management Services GPO Wireless Connection to Internal Network

Viewing 1 post (of 1 total)
  • Author
    Posts

  • Fash
    Member
    #113096

    Hi,

    I have 2 Linksys Routers(1 WRT54G and 1 BEFSR41) and ISA Server 2004.
    The BEFSR41(connected to DSLModem) is connected to the External Nic on the ISA Server and with the configuration below:

    BEFSR41
    DHCP = NO
    IP: 192.168.1.1
    SUBnet 255.255.255.0
    Gateway = NO

    ISASERVER
    External NIC:
    DHCP = NO
    IP: 192.1681.2
    Subnet: 255.255.255.0
    Gateway: 192.168.1.1

    Internal NIC:
    DHCP = NO
    IP: 192.168.20.1
    Subnet: 255.255.255.0
    Gateway: NO

    WRT54G
    DHCP = NO
    IP: 192.168.10.1
    Subnet: 255.255.255.0
    Gateway: 192.168.1.1

    The Wireless clients are getting IP Address from my Internal DHCP Server.
    The Problem that i’m having is that my Wireless Clients cannot access my internal Network through VPN, get an error 800. They can recieve emails from my internal Exchange Server, thye can browse the internet, and they can access shared directories internally. They cannot use Remoted Desktop or Terminal server into the internal server. Any help would be appreciated.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

Don't leave your business open to attack! Come learn how to protect your AD in this FREE masterclass!REGISTER NOW - Thursday, December 2, 2021 @ 1 pm ET

Active Directory (AD) is leveraged by over 90% of enterprises worldwide as the authentication and authorization hub of their IT infrastructure—but its inherent complexity leaves it prone to misconfigurations that can allow attackers to slip into your network and wreak havoc. 

Join this session with Microsoft MVP and MCT Sander Berkouwer, who will explore:

  • Whether you should upgrade your domain controllers to Windows Server
    2019 and beyond
  • Achieving mission impossible: updating DCs within 48 hours
  • How to disable legacy protocols and outdated compatibility options in
    Active Directory

Sponsored by: