[nsp] Provide routable IP over dynamic assigned remote link

[Furnish, Trever G]

Been a *long* time, but when I used to do isdn dialups on a cisco, I could
use tacacs+ to assign a specific address to a specific user.  You would just
take that address out of your normally random pool and make a pool for the
user.  That may do what you want.

On the other hand, if all you need is to be able to find the client's
destination host each time it connects, then yes, dynamic dns ought to do
it, provided that the windows server is registering a unique name for that
interface and that the place it registers the name is a DNS domain
accessible by the server initiating the vpn connection (ie a public-facing
dns server).

-t.


> -----Original Message-----
> From: Dave [Hawk-Systems] [mailto:dave@hawk-systems.com]
> Sent: Monday, December 16, 2002 3:52 PM
> To: cisco-nsp@puck.nether.net
> Subject: [nsp] Provide routable IP over dynamic assigned remote link
> 
> 
> 
> An streaching a bit here at the theory level...
> 
> We have run into a hurdle with a pop we are running that 
> happens to be virtual
> (run though bell, no our equipment).
> 
> Connections terminate into an AS5300 with PRIs that happily 
> terminate ISDN
> connections have have been doing so for some time.  We have a 
> particular client
> that requires static IP addresses (at least 1) and the 
> existing setup only
> allows for dynamicly assigned IPs from a block assigned to the NAS.
> 
> We have had people ask for this before, but to date they 
> didn't REALLY need
> them, just saw it on a feature list somewhere and as such 
> asked for them.
> 
> Is it possible to...
> 
> Have the ISDN router establish a connection gaining its 
> dynamic IP address, then
> establish a VPN connection of some sort over which we could 
> extend the LAN/IP
> addresses from one of the datacenters to provide the required 
> IP address(es) to
> the client over this pseudo network?  This would solve issues 
> in the future
> where one or more routable IP addresses were required.
> 
> Another thought would be more focused on what this particular 
> client wants to
> do, which is;
> 
> "Connect 5 remote users to access a SQL database via Windows 
> 2000 terminal
> Services. I will be setting up a W2K server as a router for 
> VPN access and
> traffic filtering, hence the required additional IP address 
> for the external
> NIC.  I would need you to add a route on your Cisco router to 
> point to this new
> server."
> 
> I am not a windows guy, but does he require a static IP 
> address, or can we
> simply route a DNS entry to his dynamic assigend IP address 
> each time he
> connects? Or does Windows/VPN demand to know the IP address.
> 
> Appreciate the insight.
> 
> Dave
> 
> 
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>