Removing "use default gateway on remote server" doesn't work



I have pasted this message three times now, but no one has answered me.

This is a real big problem for me, so it would be great with some help!



I have several XP Pro machines that has this behaviour. When I use a VPN
Connection to dial-in to a) a ISA-Server b) a WinXPProSP2 I have routing
issues.

Problem A:
I use RAS to dial-up another computer from a XPProSP2. The client is on a
LAN with a ISA Server as the default gateway. It doesn't appear to make any
difference what the server is. I've tried W2kPRO and XPPro and XPHome. The
same happens anyway. The ISA Server routes to the DMZ, where several servers
are placed. Whenever I dial-up to a server, I can ping the computers on the
LAN IP segment, but not the DMZ. Earlier I used to go to the RAS settings,
use properties, network, TCP/IP, and REMOVE the "use default gateway on
remote network", and this solved the problem. Now it seems like this setting
has no effect, because even if I remove this checkbox I still can't get
through to the DMZ. It looks like the RAS automatically uses this setting
anyway, regardless if I de-select it.

Problem 2
At home i have a XPProSP2. I use RAS and VPN to contact the office
ISA-server. Then I use "Remote Desktop Connection" to remote control my
XPProSP2 computer at work. This works fine. I do not have a ISDN line at
home, so I use my office computer to use RAS and ISDN. But whenever I
connect
to any server, the Remote Desktop Connection drops, stating that it cannot
contact the computer. Earlier this was because the "use default gateway on
remote network" was enabled. Disabling this feature fixed the problem. Now
it
seems that this setting has no effect.

Both problem 1 and problem 2 seem to have the same cause. This is new
behaviour in the operating system. This used to work just fine a few weeks
ago. I update my computers regularly with Windows Update, and it seem that
an
update from there has created this behaviour. I suspect that Microsoft has
done something to change or disable the checkbox "use default gateway on
remote network", or has made some changes to how Windows handles default
gateways and RAS.

I cannot find any information about this problem anywhere, so this is my
last resort to have this problem resolved.

Please do remember to send me e-mail with any answers to
steve(removve)@n(no-spaam)mi.no.

Best regards, Steve Gulliksen


.



Relevant Pages

  • Removing "Use default gateway on remote network" doesnt work
    ... I use RAS to dial-up another computer from a XPProSP2. ... LAN with a ISA Server as the default gateway. ... remote network", ...
    (microsoft.public.windowsxp.network_web)
  • Re: Routing through VPN (with RRAS) = remote network not reachable...
    ... my stations use my gateway as the default gateway. ... but I can't ping the remote server. ... In the past the same config has allready worked with another client. ... >> So, when a internal user try to reach a computer on the remote network, ...
    (microsoft.public.isa.vpn)
  • Re: Routing through VPN (with RRAS) = remote network not reachable...
    ... my stations use my gateway as the default gateway. ... but I can't ping the remote server. ... In the past the same config has allready worked with another client. ... >> So, when a internal user try to reach a computer on the remote network, ...
    (microsoft.public.windows.server.networking)
  • Re: RRAS client cant ping internal network
    ... Can't access the remote network after unchecking "Use default gateway on ... After following above instruction and uncheck "Use default gateway ... > I'm having a problem with our win2k routing and remote access server. ... > get the dialup clients to connect, but they can't see past the remote> access ...
    (microsoft.public.win2000.ras_routing)
  • Re: WLAN und LAN via W2K3-Server verbinden
    ... Gateway: ... Dann deaktivierst Du Routing und RAS und aktivierst das IP-Routing in der ... Technologieberater - Exchange Server ...
    (microsoft.public.de.german.windows.server.networking)