RE: VPN Connects, but no Internal IP or network resources.
- From: "Scott" <Scott@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 13 Aug 2005 17:18:01 -0700
Charlie and Rolfs00,
I have a W2k3 server with ISA2000. I was having the same problem of not
getting any internal IP addresses unless I set up a static IP address field.
Charlie is correct in that manner that you will have to choose the Internal
adaper to look for the DHCP server.
Now the problem I am still having is that once I get connected I still
cannot browse the network or get access to any resources. Most of the
documentation I have found deals with connecting and getting connected with
client to server or server to server. I havent found much on getting
connected but unable to use network resources.
If anyone has any ideas, please let me know.
Any and all help is welcome.. :) Thank you.
Scott
"Charlie" wrote:
> Most likely you are also getting Event Log messages that say the RRAS server
> (or ISA) can't contact a DHCP server.
> Sorry to be vague about this, but I don't have access to an ISA 2004 or
> Win2003 box at the moment.
> Generally when I have had this problem in the past, it's because the RRAS
> server is trying to contact a DHCP server on the external interface.
> Even though you are using ISA, you might want to check this in the RRAS
> properties:
> Right click on the Server and go to Properties and the IP tab. At the
> bottom where it says "Use the following adapter to obtain DHCP.....", make
> sure Local Area Connection is chosen. Keep in mind that I am looking at W2K
> RRAS, so I might be completely off with the interface that you will see in
> W2K3 (I assume). But generally, I think this is the direction you need to go
> to fix the problem. (The setting may be on the ISA server in the case of ISA
> 2004.)
>
> "rolfs00" wrote:
>
> > Hi!
> >
> > I am having a heck of a time getting VPN to work. I have followed the guides
> > posted here and at MS. I have also read the forum, searched the MS site, and
> > bought the Configuring ISA Server 2004 book to no avail. My problem, I am
> > afraid, is very simple but I am too dumb to figure it out. Here is what
> > happens:
> >
> > 1) I can connect via PPTP to the ISA Server, no problem. On the Details tab
> > of the Connection icon in the system tray, it matches the screenshots posted
> > here and elsewhere -- which signify a successful connection.
> >
> > 2) I cannot get an internal IP (192.168.1.X) to save my life (unless I do it
> > through a statically assigned address pool). I only get a 169.254.X.X address.
> >
> > 3) I also cannot ping any internal network resources including the server
> > (either its internal or external NIC). They cannot ping me either.
> >
> > 4) The server is called "Server" and then I do Start -- Run -- "\\Server", I
> > get a message that says it is not found.
> >
> > 5) I also cannot browse for network resources.
> >
> > I have set up the DHCP scope to go from 192.168.1.0 - 192.168.1.254. I have
> > set up the internal network to go from 192.168.1.1 - 192.168.1.99. I have
> > also set up exclusions for external NIC (192.168.10.100) and the internal NIC
> > (192.168.1.50).
> >
> > The client computer is running Win XP Pro SP2.
> >
> > I have no idea if this makes a difference, but when (under ISA Server) I go
> > to Configuration - Networks - Double Click on Interal (which shows the
> > 192.168.1.0 - 192.168.1.255), select Addresses, then Add Adapter, I notice 2
> > things:
> >
> > 1) There is a "new" RAS Server (Dial-in) Interface. It states in the info
> > box beneath it:
> >
> > Name: WAN (PPP/SLIP) Interface
> > IP Addresses: 169.254.45.252
> > Route Information: 169.254.45.252 - 169.254.45.25
> >
> > 2) On the external NIC, it states:
> > Name: U.S. Robotics 10/100 PCI NIC TX - Packet Scheduler Miniport
> > IP Addresses: 192.168.10.100
> > Route Information:
> > 0.0.0.1 - 126.255.255.255,
> > 128.0.0.0 - 169.254.45.251,
> > 169.254.45.253 - 192.168.0.255,
> > 192.168.2.0 - 223.255.255.255,
> > 240.0.0.0 - 255.255.255.254
> >
> > PLEASE PLEASE PLEASE HELP ME. At this point, I about to start forcing my
> > users to use carrier pidgeons for remote access.
> >
> > Cheers,
> > rolf
.
- Follow-Ups:
- References:
- VPN Connects, but no Internal IP or network resources.
- From: rolfs00
- RE: VPN Connects, but no Internal IP or network resources.
- From: Charlie
- VPN Connects, but no Internal IP or network resources.
- Prev by Date: RE: VPN Connects, but no Internal IP or network resources.
- Next by Date: RE: VPN Connects, but no Internal IP or network resources.
- Previous by thread: RE: VPN Connects, but no Internal IP or network resources.
- Next by thread: RE: VPN Connects, but no Internal IP or network resources.
- Index(es):
Relevant Pages
|
Loading