RAS Connection works only if LAN Adapter is disabled

  • Thread starter Thread starter Markus Broy
  • Start date Start date
M

Markus Broy

Hello,

If I connect to a customer corporate network via RAS over ISDN I get only
connection to any server if I disabled my LAN adapter and if I logged on
with the local domain of my computer.

If LAN is enabled or if I logged on in our domain it is possible to dial
into the customer corporate network but I cannot access any server neither
via name nor via IP address.

Is there a possibility to connect to the customer network and to our LAN at
the same time?

Thanks.

Markus Broy
 
sounds like routing issue. posting the result of routing table here may
help. to do that, use route print command.

--
For more and other information, go to http://howtonetworking.com.

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on
http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
 
Hi Robert,

here are the results of route print and of ipconfig -all. You can see both
results twice. The first two results with enabled LAN adapter and connected
via RAS and the second two results with disabled LAN adapter and connected
via RAS.

Thank you in advance.

Markus Broy

P. S.: The results are in German. I hope that does not matter. If you need
any translation please let me know.


############################################
with enabled LAN and with RAS connected


C:\>route print
===========================================================================
Schnittstellenliste
0x1 ........................... MS TCP Loopback interface
0x2 ...44 45 53 54 42 00 ...... NOC Extranet Access Adapter
0x3 ...00 10 a4 90 24 d2 ...... Intel(R) PRO/100+ MiniPCI
0x2000005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Aktive Routen:
Netzwerkziel Netzwerkmaske Gateway Schnittstelle Anzahl
0.0.0.0 0.0.0.0 10.0.0.254 10.0.0.13 2
0.0.0.0 0.0.0.0 10.247.81.25 10.247.81.25 1
10.0.0.0 255.0.0.0 10.0.0.13 10.0.0.13 1
10.0.0.13 255.255.255.255 127.0.0.1 127.0.0.1 1
10.247.81.25 255.255.255.255 127.0.0.1 127.0.0.1 1
10.247.81.254 255.255.255.255 10.247.81.25 10.247.81.25 1
10.255.255.255 255.255.255.255 10.0.0.13 10.0.0.13 1
10.255.255.255 255.255.255.255 10.247.81.25 10.247.81.25 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 224.0.0.0 10.0.0.13 10.0.0.13 1
224.0.0.0 224.0.0.0 10.247.81.25 10.247.81.25 1
255.255.255.255 255.255.255.255 10.247.81.25 2 1
Standardgateway: 10.247.81.25
===========================================================================
Ständige Routen:
Keine


C:\>ipconfig -all

Windows 2000-IP-Konfiguration

Hostname. . . . . . . . . . . . . : NOTEBOOK1
Primäres DNS-Suffix . . . . . . . : dws.local
Knotentyp . . . . . . . . . . . . : Hybridadapter
IP-Routing aktiviert. . . . . . . : Nein
WINS-Proxy aktiviert. . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : mu.de.pri.wyeth.com

Ethernetadapter "{DCB6F2C1-C77A-4D7B-B34B-891B73DF0740}":

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : NOC Extranet Access Adapter
Physikalische Adresse . . . . . . : 44-45-53-54-42-00
DHCP-aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 0.0.0.0
Subnetzmaske. . . . . . . . . . . : 0.0.0.0
Standardgateway . . . . . . . . . :
DNS-Server. . . . . . . . . . . . :

Ethernetadapter "LAN-Internal":

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Intel(R) PRO/100+ MiniPCI
Physikalische Adresse . . . . . . : 00-10-A4-90-24-D2
DHCP-aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
IP-Adresse. . . . . . . . . . . . : 10.0.0.13
Subnetzmaske. . . . . . . . . . . : 255.0.0.0
Standardgateway . . . . . . . . . : 10.0.0.254
DHCP-Server . . . . . . . . . . . : 10.0.0.100
DNS-Server. . . . . . . . . . . . : 10.0.0.254
10.0.0.100
Lease erhalten. . . . . . . . . . : Samstag, 29. Januar 2005
21:20:21
Lease läuft ab. . . . . . . . . . : Montag, 28. Februar 2005
21:20:21

PPP-Adapter "Wyeth 2005":

Verbindungsspezifisches DNS-Suffix: mu.de.pri.wyeth.com
Beschreibung. . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physikalische Adresse . . . . . . : 00-53-45-00-00-00
DHCP-aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 10.247.81.25
Subnetzmaske. . . . . . . . . . . : 255.255.255.255
Standardgateway . . . . . . . . . : 10.247.81.25
DNS-Server. . . . . . . . . . . . : 10.247.74.11
10.245.24.1



############################################
with disabled LAN and with RAS connected


C:\>route print
===========================================================================
Schnittstellenliste
0x1 ........................... MS TCP Loopback interface
0x2 ...44 45 53 54 42 00 ...... NOC Extranet Access Adapter
0x2000005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Aktive Routen:
Netzwerkziel Netzwerkmaske Gateway Schnittstelle Anzahl
0.0.0.0 0.0.0.0 10.247.81.25 10.247.81.25 1
10.247.81.25 255.255.255.255 127.0.0.1 127.0.0.1 1
10.247.81.254 255.255.255.255 10.247.81.25 10.247.81.25 1
10.255.255.255 255.255.255.255 10.247.81.25 10.247.81.25 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 224.0.0.0 10.247.81.25 10.247.81.25 1
255.255.255.255 255.255.255.255 10.247.81.25 2 1
Standardgateway: 10.247.81.25
===========================================================================
Ständige Routen:
Keine


C:\>ipconfig -all

Windows 2000-IP-Konfiguration

Hostname. . . . . . . . . . . . . : NOTEBOOK1
Primäres DNS-Suffix . . . . . . . : dws.local
Knotentyp . . . . . . . . . . . . : Hybridadapter
IP-Routing aktiviert. . . . . . . : Nein
WINS-Proxy aktiviert. . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : mu.de.pri.wyeth.com

Ethernetadapter "{DCB6F2C1-C77A-4D7B-B34B-891B73DF0740}":

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : NOC Extranet Access Adapter
Physikalische Adresse . . . . . . : 44-45-53-54-42-00
DHCP-aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 0.0.0.0
Subnetzmaske. . . . . . . . . . . : 0.0.0.0
Standardgateway . . . . . . . . . :
DNS-Server. . . . . . . . . . . . :

PPP-Adapter "Wyeth 2005":

Verbindungsspezifisches DNS-Suffix: mu.de.pri.wyeth.com
Beschreibung. . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physikalische Adresse . . . . . . : 00-53-45-00-00-00
DHCP-aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 10.247.81.25
Subnetzmaske. . . . . . . . . . . : 255.255.255.255
Standardgateway . . . . . . . . . : 10.247.81.25
DNS-Server. . . . . . . . . . . . : 10.247.74.11
10.245.24.1
 
are the both sites using the same ip range 10.0.0.0/16?or I would change
the VPN ip pool to some other ip. this may help. quote from
http://www.howtonetworking.com/vpn.htm
Can't access the remote network at home only

Symptoms: you setup VPN on a laptop connecting to the office VPN Server.
At home, you can connect and authenticate just fine but can't ping any
address on the remote network. If using the same laptop in a different
location, the VPN works.

Cause: The problem is the home LAN (VPN client) using the same IP and Subnet
as the remote LAN you were trying to dial into.


--
For more and other information, go to http://howtonetworking.com.

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on
http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
 
Your local addressing scheme covers all of the remote addresses. So no
traffic will ever get to the PPP adapter if the local LAN NIC is active.

Using a 24-bit subnet mask on your local LAN (ie 10.0.0.0 with a subnet
mask 255.255.255.0) will solve the problem. 10.247.x.y are now not local
addresses and will go to the PPP adapter.
 
To all of you:

I changed the subnet mask to 255.255.255.0 and it works ;-)

Thank you!

Markus
 
Back
Top