RE: Connect share in VPN



Thank for the info, Today I am in training, will test all that stuff for sure
tonight. Let you know tonight in a new post

"Edward Tian" wrote:

> Hi David:
> Thanks for posting here. Hello Russ, thanks for your suggestions.
>
> After reviewing the whole thread, I understand that some of your remote
> clients cannot access the DFS shares on the SBS Server remotely via VPN
> connection. You have already changed the IP schema of the remote side to be
> the different subnet of the SBS network. The problem even occurred when the
> problematic remote client was directly connected to the internet. The
> TCP/IP settings of the problematic clients are the same as the one of the
> healthy clients. From the problematic client, you can ping the server by
> name and IP address without difficulty once the VPN connection is
> established.
>
> Russ has asked some good questions, please verify the following settings
> first:
> 1. From the problematic client, can you access the shares on the server via
> \\Servername?
>
> 2. Please temporarily disable the "Windows Firewall" on the remote client,
> and see if the problem can be fixed. If you have any anti-virus software
> installed on the client, please also temporarily disable it.
>
> 3. Do you have ISA Server installed? If so, which version is the ISA Server?
>
> In addition, please help me gather the following information:
> 1. From the problematic client, once the VPN connection is established,
> please type "ipconfig/all > d:\filename.txt" and "route print >
> d:\filename.txt" (without the quotation mark) on both the SBS Server and
> the remote client, then send these four files to my mailbox:
> v-edtian@xxxxxxxxxxxxx so that I will have a clear understanding of your
> network diagram.
>
> 2. Please follow this KB article to configure the VPN connection on the
> remote client.
>
> How to configure a VPN connection to your corporate network in Windows XP
> Professional
> http://support.microsoft.com/default.aspx?scid=KB;EN-US;305550
>
> Then, try not using the remote gateway on the client, to do so:
> On the problematic client:
> 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.
>
> 3. From the problematic client, can you ping the internal client by
> name/IP? If ping works, can you access the shared folder on the internal
> clients? For example, suppose there is a shared folder called "shares" on
> one workstation located in the internal network of SBS Server, can you
> access this folder using \\computername\shares ?
>
> 4. Since the problem only occurred on particular remote users, please try
> the following tests:
> Here I assume user A is using the client A for VPN access without problem,
> and user B is having difficulty to access the DFS shares using computer B.
>
> a. From computer A, use the user account B to establish the VPN connection
> to the SBS Server, does the access to DFS work?
>
> b. From computer B, use the user account A to establish the VPN connection
> to the SBS Server, does it work?
>
> 5. Can you find any related event log in the Event Viewer on both the
> server and the remote client? If any, please send to me for further
> analysis.
>
> I appreciate your time and cooperation. Please feel free to let me know if
> there is anything I can do for 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: Connect share in VPN
> | thread-index: AcXPkkcc44cT77XWT+O52B4S4iLyyA==
> | X-WBNR-Posting-Host: 69.70.13.130
> | From: "=?Utf-8?B?RGF2aWQ=?=" <David@xxxxxxxxxxxxxxxxxxxxxxxxx>
> | Subject: Connect share in VPN
> | Date: Wed, 12 Oct 2005 18:06:01 -0700
> | Lines: 18
> | Message-ID: <6F277ADD-EAB4-4431-B36E-9DA37840A622@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:160920
> | X-Tomcat-NG: microsoft.public.windows.server.sbs
> |
> | We have setup and SBS 2003 server. We have 18 worker that work from
> remote
> | site. They use RWW, OWA, RPC to HTTP, and VPN. We got some issue with
> VPN.
> |
> | We can connect corectly but for a reason on some of the remote worker PC
> we
> | have difficulty to connect the main share of our company. By the way,
> just
> | to let you know that this main share is a DFS. The majority of our
> worker
> | are able to connect to this share. Few of them get the folowing message
> :
> | w:\Share is not accessible. The network location cannot be reached. For
> | information about network troubleshooting, see windows help.
> |
> | We can ping the server by name, by IP address no problem. I did an
> IPconfig
> | on the PC that are working and on the on that are not working, I got the
> | same config. Also, I remember to get those issue on different customer
> site
> | in the past. This time it is critical, I need to fix this.
> |
> | Thank in advance, if you need more info just ask.
> |
> | Dave
> |
>
>
.



Relevant Pages

  • RE: RWW client wont connect
    ... Right click My Computer on problematic client computer, ... Click Remote tab, ensure tick "Allow users to connect remotely to this ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW client wont connect
    ... Right click My Computer on problematic client computer, ... Click Remote tab, ensure tick "Allow users to connect remotely to this ...
    (microsoft.public.windows.server.sbs)
  • RE: RAS Setup and Implimentation
    ... establish the VPN connection using the remote connection disk. ... Run the setup.exe on the client computer from the floppy ... Connect the laptop directly to the external NIC of the SBS server, ...
    (microsoft.public.windows.server.sbs)
  • Re: Connectivity to the Remote Computer Could Not Be Established
    ... access client computers desktop thru VPN connection. ... Right click My Computer on problematic client computer, ... Click Remote tab, ensure tick "Allow users to connect remotely to this ... Ensure the problematic client computers do not install any 3rd-party ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN - Clients
    ... The problem is that when the vpn connection is active on the client box (clearly a remote lan), no other box on the client side lan can either ping or map a network drive to the box that has the vpn established. ...
    (microsoft.public.windows.server.sbs)