RE: Another Remote Connection Manager Problem
- From: "VirtualJay" <VirtualJay@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 20 Dec 2005 23:12:02 -0800
Thank you Karl and Derek. The consensus is in! Change the subnet to be
different on the external and internal NICS. I will try this tomorrow, being
as it is just after midnight.. Thanks for your help and your IP assigning
suggestions. I will report back after the change! Thanks again.
Jay (no longer in Oz)
--
"Their beauty has more meaning
Than the whole human race and the race of birds"
"VirtualJay" wrote:
> I am having a problem similar to CUBuffs, who also posted today. I have an
> SBS2003 server, standard edition with 2 NICS configured as 192.168.1.2
> internal and 192.168.1.3 for the internet connection. Attached 192.168.1.3
> is a Linksys BEFSR41 Router with an IP of 192.168.1.1. I am performing DHCP
> via the SBS server to all clients. I have configured Remote Access on the
> server to allow VPN connections and have port forwarded 443 and 1723 to
> 192.168.1.3 at the router.
>
> With this configuration OWA and Remote Workplace are operational. But one
> user has only his laptop, and wants to use network resources when he is out
> of the office. With no computer to "remote into", I want to instead use
> Connection Manager to connect to the VPN server and gain access to a shared
> folder. I installed Connection Manager via Remote Desktop onto his laptop.
> From a remote location (my office) I log in using his laptop (XP Pro),
> connected to a Linksys BEFVP41 router and DSL service, logging in using his
> usual username and domain. The internal network connection (internal NIC) is
> assigned an IP of, for example, 192.168.1.101. I then run the VPN
> connection from Connection Manager to establish the VPN back to his server,
> which connects. The "Connect to Small Business Server" connection is
> assigned an IP address of 192.168.1.78. If I check the Status Details, it
> reports this IP address, and also states that the server IP address is
> 192.168.1.80. I have also checked this connection from the Server side, and
> it confims that a VPN connection is established. From the server, I can ping
> 192.168.1.78. I have also configured the remote router (BEFVP41) to allow
> VPN pass-through and turned of ICF on the (remote) laptop. There is no other
> firewall on the laptop.
>
> From the remote, I can ping my VPN-assigned IP of 192.168.1.78, but I cannot
> ping 192.168.1.80, nor can I access any server resources.
>
> I am looking, I guess firstly, to understand why I cannot ping the server
> IP. Is it necessary for me to setup the remote site on a different subnet?
> It seems like I am fairly close on this, since the VPN connects, so I am
> probably missing something that is glowing and shaking it's hands at me, but
> I don't see it. I have read through the response to CUBuffs. I have not
> checked the WINS status on the server (and can't until tomorrow since that
> office is closed) but for now I am just trying to ping the IP address.
>
> I am using dynamic assigned public IPs at the outside of both routers, but
> have DDNS running at the Server to find the IP. I thought I would mention
> this, but don't think it is a problem, since OWA and Remote Desktop are fine
> and the VPN does seem to connect.
>
> I have also tried to connect by logging in to the laptop, checking the "use
> remote connection" box, selecting the VPN and authenticating, rather than
> using the cached authentication and then running the VPN after I am logged
> in. The result is the same.
>
> I would greatly appreciate any thoughts and ideas. Sorry about the long
> explanation, but wanted to give the needed details. Thanks!
>
> --
> "Their beauty has more meaning
> Than the whole human race and the race of birds"
.
- Prev by Date: Re: Another Remote Connection Manager Problem
- Next by Date: RE: Win2k to SBS 2003 migration questions
- Previous by thread: Re: Another Remote Connection Manager Problem
- Next by thread: RE: Win2k to SBS 2003 migration questions
- Index(es):
Relevant Pages
|
