VPN connection to Cisco router

Hi,

I want to establish a VPN from my Windows Server 2003 to another 2003
server.

At first I configured a VPN connection in "Network Connections" and it
connects OK.

Then I realized that I must create it in RRAS instead if I want to route
traffic between both sites.

I created a new demand-dial interface in RRAS, using the same settings
(logon, password, key, etc.) than the previous connection. But it does not
connect.

In Event viewer, the only RemoteAccess related event is number 20167, "No IP
address is available to hand out to the dial-in client." Strange because my
erver is dialing in, not the opposite.

Any ideas ?

Title edit. It through a router, no to a router.

"Pierrot Robert" <mcthepro_at_hotmail.com> a écrit dans le message de news:
eg4Ms$(E-Mail Removed)...
> Hi,
>
> I want to establish a VPN from my Windows Server 2003 to another 2003
> server.
>
> At first I configured a VPN connection in "Network Connections" and it
> connects OK.
>
> Then I realized that I must create it in RRAS instead if I want to route
> traffic between both sites.
>
> I created a new demand-dial interface in RRAS, using the same settings
> (logon, password, key, etc.) than the previous connection. But it does not
> connect.
>
> In Event viewer, the only RemoteAccess related event is number 20167, "No
> IP address is available to hand out to the dial-in client." Strange
> because my erver is dialing in, not the opposite.
>
> Any ideas ?
>

"Pierrot Robert" <mcthepro_at_hotmail.com> wrote in message
news:eg4Ms$(E-Mail Removed)...
> In Event viewer, the only RemoteAccess related event is number 20167, "No
IP
> address is available to hand out to the dial-in client." Strange because
my
> erver is dialing in, not the opposite.

Probably two different things. The failed connection probably does not
create a log entry. The "no IP" thing is probably because you configured
RRAS to do both outbound and inbound and it cannot locate any IP#s to use
for incomming connections. RRAS always gathers the IP#s it might need for
incomming clients *ahead of time* and has them "ready" for when a client
connects in. If it can't get the address it whines about it.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------