Re: VPN Server will not allow information to Pass-through.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Why would you need a diagram... The router plays no role in this setup.
there is a workstation on the 10 net that needs to connect to a resource on
the 137 net. There is a server running RAS that has two nics, 1 using a 10
number another using a 137 number. when connecting to the 10 card from a 10
client everything looks as if it will route properly, but then nothing gets
routed throught the 137 card to the 137 resource.

"Bill Grant" wrote:

> Like Bob, I am a bit mystified by this setup. Is this some sort of
> testing setup? Why would you want to use VPN when the client is directly
> connected to the RRAS server?
>
> Do you perhaps want a setup where the clients in 10.1 cannot see
> anything in 137.135.128 unless they use a VPN connection? I presume IP
> routing is not enabled on the RRAS server.
>
> A simple diagram of the network would help. eg
>
> Router?
> |
> workstations
> 10.1.x.y dg ?
> |
> 10.1.1.57 dg blank
> RRAS
> 137.135.128.112 dg blank
> |
> 137.135.128.x dg ?
>
> realitychx wrote:
> > I have a Win 2000 Server machine acting as a remote access VPN
> > server. When a client machine connects to the Remote access server
> > it is unable to connect to any resources on the 137.135.128.x network
> > segment. Any ideas?
> > Thanks in advance.
> >
> > Server:
> > LAN1: 10.1.1.67
> > LAN2: 137.135.128.112
> >
> > Client:
> > LAN: 10.1.1.57
> > After connecting to the VPN Server
> > LAN: 10.1.1.57
> > WAN: 137.135.128.4
> >
> > A ping, from the VPN client, to the servers LAN2 card is successful
> > only after the VPN connection has been established.
> >
> > A ping, from the VPN client, to 137.135.128.253 (another server)
> > fails.
> >
> > In the remote access administrative tool, static routes appear as
> > such:
> >
> > LAN 2
> > Destination:137.135.128.0
> > Net Mask: 255.255.255.0
> > Gateway: 137.135.128.112
> > Metric: 1
> >
> > LAN 1
> > Destination: 10.1.0.0
> > Net Mask: 255.255.0.0
> > Gateway: 10.1.1.67
> > Metric: 1
>
>
>
.

Relevant Pages

  • Re: VPN clients unable to connect to other resources.
    ... gateway matches the IP of the remote client, and DNS and WINS point to the ... remote (although it takes close to a minute to connect, ... This is just regular Windows VPN, ... VPN server, remote routing and access running on the SBS 2003 server ...
    (microsoft.public.windows.server.sbs)
  • RE: Problems with connectcomputer and active directory
    ... I understand that you would like to join a remote client to the domain. ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ... Create a VPN connection to ISA/RRAS on the Internet ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote connectivity problems
    ... do you mean you have added a remote client to SBS ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN clients unable to connect to other resources.
    ... Are you saying that an XP Home PC wouldn't be able to connect to a server share over VPN? ... Can ping the SBS but not the client PCs on the same network. ... gateway matches the IP of the remote client, ...
    (microsoft.public.windows.server.sbs)
  • Re: How to configure for Two different IP subnets
    ... Active Directory will go haywire in a setup like that. ... AD integrates with the local DNS, so you cannot use the DNS at your ISP ... With Server 2003 Standard ... for its internal interface (ie the VPN endpoint). ...
    (microsoft.public.windows.server.networking)