The tunnel seems fine - at least, there are never any problems establishing
the connection.
Pinging by name gives some peculiar results:-
Pinging from PC: at first the target server name resolves to the ip address
of the server vpn adapter, but after that it resolves to the actual server ip
address. However, no packets get through at all when pinging from the PC to
the remote server, so it's just the DNS giving the resolution without any
real icmp traffic.
Pinging from the remote server gives variable results: at first the PC name
resolves to the correct ip, but no packets get through, then after a minute
or two (without any extra commands or traffic in between) I get 100% packet
return at avg 45ms. Attempting the same ping a little later during the same
session fails again with 100% loss.
Pinging the IP addresses from either end never seemed to work at all. At
one point the remote server was failing to resolve the PC name also. I never
managed to get tracert working at all.
This seems really odd - why would ping results vary so widely during the
same vpn session?
When performing the same tests on a connection that I know I can map through
I get far more sensible results with both names ip addresses returning 100%
from the inception of the connection. Theres no variation and all the routes
came out as expected.
Thanks for starting me off on this TCP/IP ramble - I now I have a far better
idea about how this thing is working, but I'm a bit lost as to how to improve
the stability!
"Lanwench [MVP - Exchange]" wrote:
> James S Clark wrote:
> > Has anyone else encountered a problem with mapping network drives
> > across vpns after installing MS updates for win2003 server or win2K
> > in the last month or two?
> >
> > Does anybody know of issues in any recent MS updates that might
> > affect such operations, such as increased security on network name
> > resolution or something?
> >
> > Platform: Win2K PC on TCP/IP based LAN mapping a drive to a Win2003
> > server share on remote TCP/IP LAN via ADSL routers using either
> > manual desktop or programmatic methods (ie: using funcitons from
> > rasapi32.dll). A number of these vpns & mappings have been working
> > fine for months, but now suddenly 3 out of 10 identical setups have
> > stopped working - the only difference i can think of is the MS
> > updates (the 3 offenders being the most up to date), any ideas of
> > where to start?
>
> What happens when you try? Is the tunnel established properly? Can you still
> ping by IP and name to the remote network?
>
>
>
|