RE: Remote Access problems



I have been unable to attempt changing the gateway as of yet.
However, I do have further "enlightenment" as to the specifics of my problem.
Over the PPP connection, Outlook connects to exchange fine, you can print,
and you can access shares on the server. However, the remotely connected
computer cannot connect to shares on the local computers. Would this be a
security setting, or a general connectivity issue that should be tackled
after changing the gateway?

--Thanks again,
Alex Kubacki

"Edward Tian" wrote:

> Hello:
> Thank you for your update. I appreciate your effort and patience. :)
>
> Since the remote client uses a SBS VPN connection package, it's quite
> different from the one which is manually created. We can follow the steps
> below:
>
> 1. Locate the following folder:
> C:\Documents and Settings\<username>\Application
> Data\Microsoft\Network\Connections\Cm\remote\
>
> 2. Use Notepad to open the remote.cms file. It is in plain text format.
>
> 3. Locate Gateway_On_Remote
>
> 4. Change Gateway_On_Remote=1 to Gateway_On_Remote=0
>
> 5. Save this file.
>
> 6. Reconnect with Connection Manager and the default gateway will not be
> changed.
>
> Then the remote default gateway will no longer be used, you can type
> 'ipconfig/all' under the prompt command to check whether the setting has
> been changed. (The default gateway on the PPP adapter will be blank)
>
> If you type "route print" under prompt command, you will see that your
> local gateway is defined to be the default gateway.
>
> By the way: we can also manually create a new VPN connection, here are the
> detailed steps, you may take a look at your convenience.
>
> How to create a new VPN connection:
> 1. Click Start, click Control Panel, click Network and Internet
> Connections, and then click Network Connections.
>
> 2. Click Create a new connection, and then click Next.
>
> 3. Click Connect to the network at my workplace, and then click Next.
>
> 4. Click Virtual Private Network connection, and then click Next.
>
> 5. Type a descriptive name for your company, and then click Next.
>
> 6. Click Do not dial the initial connection, and then click Next.
>
> 7. Type the host name or IP address of the computer where you are
> connecting, and then click Next.
>
> 8. Use one of the following methods:
>
> Click Anyone's use if you want to share the connection with all users.
>
> Click My use only if you do not want to share the connection.
>
> 9. Click Next, and then click Finish.
>
> Then manually configure this connection not to use the default remote
> gateway.
> For your convenience, I attached the steps:
>
> 1). Double-click My Computer, and then click the Network and Dial-up
> Connections link.
> 2). Right-click the VPN connection that you want to change, and then click
> Properties.
> 3). Click the Networking tab, click Internet Protocol (TCP/IP) in the
> 'Components checked are used by this connection' list, and then click
> Properties.
> 4). Click Advanced, and then click to clear the Use default gateway on
> remote network check box.
> 5). Click OK, click OK, and then click OK.
>
> After the VPN connection is established, type 'ipconfig/all' in the prompt
> command, you will find that the remote gateway is no longer used by the
> local client. :)
>
> Hope this helps. I look forward to hearing from you. If you encounter any
> difficulties, please feel free to let me know, I am standing by to help you.
>
> Have a nice day!
>
> Best Regards
> Edward Tian(MSFT)
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
> ======================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> | Thread-Topic: Remote Access problems
> | thread-index: AcWWsszH0qr71mawT0CNz/MJfe+Lkw==
> | X-WBNR-Posting-Host: 24.172.168.154
> | From: =?Utf-8?B?QmFsYW5jZUVuZ2luZWVyaW5n?=
> <BalanceEngineering@xxxxxxxxxxxxxxxxxxxxxxxxx>
> | References: <90FC4DA9-FC0A-4B42-86B5-5FE77850EBBE@xxxxxxxxxxxxx>
> <1tMACtBlFHA.588@xxxxxxxxxxxxxxxxxxxxx>
> <11A80550-7352-4FE9-9074-C964FFCAFA16@xxxxxxxxxxxxx>
> <XtKH8KjlFHA.940@xxxxxxxxxxxxxxxxxxxxx>
> | Subject: RE: Remote Access problems
> | Date: Mon, 1 Aug 2005 09:05:13 -0700
> | Lines: 50
> | Message-ID: <C374B0E7-3C67-4CFD-88BE-88492A97C0CE@xxxxxxxxxxxxx>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.windows.server.sbs
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:140514
> | X-Tomcat-NG: microsoft.public.windows.server.sbs
> |
> | Changing the IP scheme worked, for the most part. Remote client has
> access to
> | local network and SBS services, but cannot access the internet through
> the
> | VPN. On the "Connect to Small Business Server" PPP connection properties,
> | there is no option to not use the default gateway, so I am at a loss as
> how
> | to proceed.
> |
> | The ipconfig of the remote computer is as follows. I notice the gateway
> on
> | the PPP adapter is the adapter's address, not an actual gateway?
> |
> | Windows IP Configuration
> | Host Name . . . . . . . . . . . . : BALANCEMARY
> | Primary Dns Suffix . . . . . . . : BalEng.local
> | Node Type . . . . . . . . . . . . : Hybrid
> | IP Routing Enabled. . . . . . . . : No
> | WINS Proxy Enabled. . . . . . . . : No
> | DNS Suffix Search List. . . . . . : BalEng.local
> | BalEng.local
> |
> | Ethernet adapter Local Area Connection:
> | Connection-specific DNS Suffix . :
> | Description . . . . . . . . . . . : Broadcom 440x 10/100
> Integrated
> | Cont
> | Physical Address. . . . . . . . . : 00-12-3F-17-69-D4
> | Dhcp Enabled. . . . . . . . . . . : Yes
> | Autoconfiguration Enabled . . . . : Yes
> | IP Address. . . . . . . . . . . . : 192.168.1.100
> | Subnet Mask . . . . . . . . . . . : 255.255.255.0
> | Default Gateway . . . . . . . . . : 192.168.1.1
> | DHCP Server . . . . . . . . . . . : 192.168.1.1
> | DNS Servers . . . . . . . . . . . : 63.240.76.135
> | 204.127.194.11
> | Lease Obtained. . . . . . . . . . : Monday, August 01, 2005
> 11:40:43
> | AM
> | Lease Expires . . . . . . . . . . : Tuesday, August 02, 2005
> | 11:40:43 AM
> |
> | PPP adapter Connect to Small Business Server:
> | Connection-specific DNS Suffix . : BalEng.local
> | Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> | Physical Address. . . . . . . . . : 00-53-45-00-00-00
> | Dhcp Enabled. . . . . . . . . . . : No
> | IP Address. . . . . . . . . . . . : 123.123.123.128
> | Subnet Mask . . . . . . . . . . . : 255.255.255.255
> | Default Gateway . . . . . . . . . : 123.123.123.128
> | DNS Servers . . . . . . . . . . . : 123.123.123.124
> | Primary WINS Server . . . . . . . : 123.123.123.124
> |
> |
> |
> |
> |
>
>
.



Relevant Pages

  • Re: Using Remote Desktop From an SBS Domain
    ... Right click My Network Places...Properties. ... computer that is on a remote network now. ... Internet connection, bypassing my SBS/ISA network all together. ... the port number you connect to from 80 to a port of your ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem with RWW, can list computers/servers, cannot get logged in
    ... > When I say "outside the network" I mean accessing the network via a ... > one of two errors at the remote desktop, ... > connection might not be enabled or the computer might be too bust to ... Even turned off connection limits in ISA General... ...
    (microsoft.public.windows.server.sbs)
  • Re: Using Remote Desktop From an SBS Domain
    ... Internet connection, bypassing my SBS/ISA network all together. ... machine that I'm trying to connect to is configured to accept Remote Desktop ... the port number you connect to from 80 to a port of your ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN and remote gateway
    ... 317025, we could know that if you use local gateway, your internet connection will not be a problem, but, you could not access your ... remote network since there is no route between you computer and your remote company network. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem with RWW, can list computers/servers, cannot get logge
    ... I believe I have the certificate address handled correctly, ... >> to which the network in connected. ... The client could not establis a connection to the remote ... >> connection might not be enabled or the computer might be too bust to ...
    (microsoft.public.windows.server.sbs)