vpn clinet cannot access resources on VPN server, but can get rest of LAN

[Steve Jacobs]

We have a server running:
Windows 2003 Standard
Sharepoint Portal Server 2003
The standard, Windows-built-in, VPN services.

If a client connects to the VPN server on this machine, he/she cannot
connect to the Sharepoint site. If the same client instead makes a VPN
connection to our other VPN serveron the LAN, he/she has no problem at all
accessing the Sharepoint site.

I've seen this crop up once before (could not access resources local to
the VPN server), and did not resolve it previously.

Obviously I'm doing something wrong. Any of you know what?

Thanks,
Steve

 

[Steve Jacobs]

A couple of other notes I neglected to mention:
There is no ISA server installed.
There is no WINS server running.
Clients are able to access other network resources, found on other network
servers.

-- Steve

 

[Steve Jacobs]

Well, maybe I'll get this solved myself sooner or later, but hopefully
someone down the road may benefit from my updates here.

I'm being incredibly dense about this whole thing, and have finally
figured out what should have been obvious. While I haven't solved the
puzzle yet, I believe I'm closer.

My VPN server is assigning an IP address to the vpn client connections via
DHCP. The vpn server interface carries a different IP address than the
physical, actual, network card in the server though. Therefore, my URL to
the Sharepoint site (http://serverIP:port/sharepoint) was pointing to the
wrong address. If I call up the VPN client properties and determine the
VPN server's IP address, and use that, I can connect.

BUT, that's not an adequate solution for end users. Ideally the user
shoudl be able to enter a much simpler URL. I'm resigned to the user
needing to include the " ort/sharepoint " at the end of the URL, but I'd
prefer they could enter the servername rather than the IP. I haven't made
that work yet.

I've tried adding NetBEUI to my VPN client settings, but upon connection I
get a message indicating the server and client couldn't agree on protocols
(error 733), and the NetBEUI protocol was unused.

If I try to browse to the site using the server name, the browser seems to
go off in search of the page indefinitely.

Thanks,
Steve

 

[Ian Ho]

I think I have quite the same problem as you. When you access the
VPN server service thourgh its LAN IP, it fails, but if you access the
VPN server service through its vpn server interface IP, it is done.
Do you get this same situation? I run into this trouble and still figuring
out how to solve it. Do you have any insight?

Ian