we are having trouble with server to server demand dial PPTP routing
since win2003sp1 has been released. we have clients running the server
to server vpn currently but since using w2003svrsp1 the config we
normally use will no longer work.
Here are some basic notes about server configs that work.
w2ksvr to w2ksvr OK
w2ksvr to w2003svr ok
w2003svr to w2003svr ok
w2003svr to w2003svrsp1 fail
w2003svrsp1 to w2003svrsp1 fail
symptoms
when the remote server dials in it can see anything on the local
network (ping, vnc, telnet) but its clients cannot. At the local server
it or any of its clients cannot ping anything on the remote network. It
can ping the internal ipaddress used by ras
ip addresses
local clients 192.1.1.20
local server 192.1.1.11
local ras 192.1.1.15
192.1.1.75
remote server 10.0.40.1
remote clients 10.0.40.100
local client 192.1.1.20 can ping 192.1.1.11,15 and 75 but not 10.0.40.1
& 100
local server can ping 192.1.1.20, 11, 15, 75 but not 10.0.40.1 & 100
remote clients can ping 10.0.40.1 but not 192.1.1.20,11,15 & 75
remote server can ping any ip address
the demaind dial interface on the remote site has a static route back
to 192.1.1.0 set and the demaind dial user has a static route of
10.0.40.0
rras firewall disabled on both servers, does anybody know of a hidden
firewall that stops this from working
tryed the username must match the demanddial name with no success but
when uninstalled sp1 all springs back to life. But how can you
uninstall sp1 from an sp1 integrated install.
|