Access shared files throough VPN

  • Thread starter Thread starter Wan
  • Start date Start date
W

Wan

Hi,

Here is my set up:
- an XP Home computer that acts as a file server
- an Win98SE laptop

My router supports VPN tunneling. From my laptop, logon
to an ISP via modem. Access internet OK. Launch a VPN
client. It logs on the network successfully. Can ping my
XP computer.

Try to setup a network drive such that I can access the
files. Windows reports cannot access the drive. I used
to be able to do this when the XP box was a Windows ME box.

If I connect the laptop to the XP box using the normal
LAN. I can map and access the network drive without
problems. What do I need to do to make it work?

Also, I notice that the XP box has a Network Bridge (have
a NIC and Firewire interfaces in the XP box). What is the
Network Bridge for?

Thanks.
Wan
 
try this: net use \\xpname\shared /u:administrator. can you access the
shared? post back with the result.

--
For more and other information, go to
http://www25.brinkster.com/ChicagoTech

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Windows & Network Support, Tips and FAQs on
http://www25.brinkster.com/ChicagoTech
This posting is provided "AS IS" with no warranties.
 
Robert,

Thanks for the information.

Tried your command at my laptop. The /u:administrator is
not a valid option.

However, the error message gives me a clue. Basically, it
cannot resolve the \\xpname IP address. I added the IP
address of the "xpname" in my DNS server pool. It maps
the drive OK.

I don't understand why I need this because when I am on
the LAN, it does not have problem to resolve the IP
address of "xpname". Why has problem when through the
VPN? Shouldn't my laptop work like I am on the LAN?

I have another problem. The old WinME box had a fixed IP
address. With this new XP, it configures (self configure
when installing XP) to use DHCP and uses the router as the
DHCP server. I configured it to have a fixed address.
Then I cannot access the internet from this XP box
anymore. Is this something to do with the Network Bridge?

The problem of using DHCP is the "xpname" IP address may
change. I would not be able to find out the IP address of
the "xpname" when I am on the road. Any idea to make
the "xpname" to have a fixed IP address?

Thanks.
Wan
 
1. win me: I would check the dns first.
2. vpn: quoted from http://www25.brinkster.com/ChicagoTech
Unable to browse through PPTP/VPN connection
Symptoms: 1. If the WINS server is on the same computer as the PPTP/VPN
server, and you attempt to connect to a computer using a PPTP/VPN client,
you may experience following problem: 1) The NetBIOS name of the computer to
which you are attempting to connect is not resolved. 2) You may receive an
error message similar to the following error message: "System error 53 has
occurred. The network path was not found" when using net view or opening
Network Knighthood.
2. If the WINS server is not on the same computer as the PPTP server and you
attempt to connect to a computer using a PPTP client, you may be able to
connect to computers on your local area network (LAN), but you may be unable
to connect to network shares or resources on the PPTP server.
Resolutions: Inability to browse often means the client can't resolve
NetBIOS names.
1. If this is a workgroup network, enable NetBIOS over TCP/IP on the server
and clients.
2. If this is domain network and the WINS server is on the same computer as
the PPTP/VPN server, move the WINS server to a different computer.
3. Add the NetBEUI protocol for your PPTP tunnel instead of, or in addition
to, TCP/IP.
4. By default, most routers and firewalls prevent the transmission of
NetBIOS names unless you enable UDP ports 137 and 138 and TCP port 139. Try
to enable UDP ports 137 and 138 and TCP port 139 across all routers and
firewalls between the PPTP/VPN client and PPTP/VPN server.
5. Make sure the client has correct DNS, WINS and Master Browser settings.
6. Make sure the default gateway points to the remote network rather than to
the ISP.
7. Some ISP might block ports required for NetBIOS name broadcasts.
8. If WINS address is not distributed upon connection to VPN, LMHOSTS should
be configured to enable Domain to be located.
9. If you try these techniques and the client still can't browse, try to use
UNC to connect to the remote resources by ip, for example, use the net use
h: \\serverip\sharename command.

--
For more and other information, go to
http://www25.brinkster.com/ChicagoTech

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Windows & Network Support, Tips and FAQs on
http://www25.brinkster.com/ChicagoTech
This posting is provided "AS IS" with no warranties.
 
Back
Top