Networking Forums

Networking Forums > Computer Networking > Windows Networking > Dial-in server problem: no routing

Reply
Thread Tools Display Modes

Dial-in server problem: no routing

 
 
v_iron
Guest
Posts: n/a

 
      04-25-2007, 03:01 PM
Hi all!

I have server connected to local network with internet access. To have
dial-up access from home I setup dial-in connections. TCP/IP properties:
access to local network granted, DHCP used for IP addresses. In the
properties of connection used for internet: firewall switched off, other
users can use internet access from this computer.
Then we try to connect to it from remote machine here are no problems
connecting but remote user can only ping this server, by PPP address or
by local network address (192.168.1.33). No access to local network or
internet. Please explain that I need to change to have routing to local
network and internet from remote computer.

Server OS: MS Windows XP Pro version 2002 SP1,v.1081

Here is routing info then client is connected:

================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x10004 ...00 15 58 63 80 1f ...... Realtek RTL8139/810x Family Fast
Ethernet NIC - Virtual Machine Network Services Driver
0x20003 ...00 18 f3 7a 24 de ...... ASUS NX1001 Network Adapter -
Virtual Machine Network Services Driver
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.33 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
169.254.55.208 255.255.255.255 127.0.0.1 127.0.0.1 50
169.254.229.222 255.255.255.255 169.254.55.208 169.254.55.208 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 20
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 20
192.168.1.0 255.255.255.0 192.168.1.33 192.168.1.33 20
192.168.1.33 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.33 192.168.1.33 20
224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1 20
224.0.0.0 240.0.0.0 192.168.1.33 192.168.1.33 20
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
255.255.255.255 255.255.255.255 192.168.1.33 192.168.1.33 1
Default Gateway: 192.168.1.1
================================================== =========================
Persistent Routes:
None


Windows IP Configuration

Host Name . . . . . . . . . . . . : Cvetana
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes

PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Внутренний интерфейс
RAS-сервера...
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 169.254.55.208
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :

Ethernet adapter Internet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family
Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-15-58-63-80-1F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.33
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : 24 кв_тня 2007 р. 10:01:37
Lease Expires . . . . . . . . . . : 27 кв_тня 2007 р. 10:01:37

Ethernet adapter Netware:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : ASUS NX1001 Network Adapter
Physical Address. . . . . . . . . : 00-18-F3-7A-24-DE
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
 
Reply With Quote
 
 
 
 
Robert L \(MS-MVP\)
Guest
Posts: n/a

 
      04-25-2007, 03:11 PM
We have some issues in this configuration.

1.The client doesn't receive IP from the DHCP, which is 169.254.x.x.
2. Where is the DHCP server?
3. Are both sites using the same IP range 192.168.1.x?
4. The RRAS server may not enable IP routing.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"v_iron" <(E-Mail Removed)> wrote in message news:f0nqg4$edf$(E-Mail Removed)...
> Hi all!
>
> I have server connected to local network with internet access. To have
> dial-up access from home I setup dial-in connections. TCP/IP properties:
> access to local network granted, DHCP used for IP addresses. In the
> properties of connection used for internet: firewall switched off, other
> users can use internet access from this computer.
> Then we try to connect to it from remote machine here are no problems
> connecting but remote user can only ping this server, by PPP address or
> by local network address (192.168.1.33). No access to local network or
> internet. Please explain that I need to change to have routing to local
> network and internet from remote computer.
>
> Server OS: MS Windows XP Pro version 2002 SP1,v.1081
>
> Here is routing info then client is connected:
>
> ================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> 0x10004 ...00 15 58 63 80 1f ...... Realtek RTL8139/810x Family Fast
> Ethernet NIC - Virtual Machine Network Services Driver
> 0x20003 ...00 18 f3 7a 24 de ...... ASUS NX1001 Network Adapter -
> Virtual Machine Network Services Driver
> ================================================== =========================
> ================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.33 20
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 169.254.55.208 255.255.255.255 127.0.0.1 127.0.0.1 50
> 169.254.229.222 255.255.255.255 169.254.55.208 169.254.55.208 1
> 192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 20
> 192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20
> 192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 20
> 192.168.1.0 255.255.255.0 192.168.1.33 192.168.1.33 20
> 192.168.1.33 255.255.255.255 127.0.0.1 127.0.0.1 20
> 192.168.1.255 255.255.255.255 192.168.1.33 192.168.1.33 20
> 224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1 20
> 224.0.0.0 240.0.0.0 192.168.1.33 192.168.1.33 20
> 255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
> 255.255.255.255 255.255.255.255 192.168.1.33 192.168.1.33 1
> Default Gateway: 192.168.1.1
> ================================================== =========================
> Persistent Routes:
> None
>
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : Cvetana
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : Yes
>
> PPP adapter RAS Server (Dial In) Interface:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : ?????????? ?????????
> RAS-???????...
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 169.254.55.208
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . :
>
> Ethernet adapter Internet:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Realtek RTL8139/810x Family
> Fast Ethernet NIC
> Physical Address. . . . . . . . . : 00-15-58-63-80-1F
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.1.33
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> Lease Obtained. . . . . . . . . . : 24 ??_??? 2007 ?. 10:01:37
> Lease Expires . . . . . . . . . . : 27 ??_??? 2007 ?. 10:01:37
>
> Ethernet adapter Netware:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : ASUS NX1001 Network Adapter
> Physical Address. . . . . . . . . : 00-18-F3-7A-24-DE
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.0.1
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :



 
Reply With Quote
 
v_iron
Guest
Posts: n/a

 
      04-25-2007, 04:04 PM
Robert L (MS-MVP) :
> We have some issues in this configuration.
>
> 1.The client doesn't receive IP from the DHCP, which is 169.254.x.x.

Attached info is from server, not from client. At client here is
adapter with 169.254.229.222 address with default routing to it.

> 2. Where is the DHCP server?

I think in PPP tunnel RAS server acts as DHCP and give 169.254.229.222
address to remote point. Is this right? In the local network ADSL modem
is the DHCP server.

> 3. Are both sites using the same IP range 192.168.1.x?

Office network with internet 192.168.1.0/24, additional network
192.168.0.0/24, tunnel 169.254.55.208 <-> 169.254.229.222, remote
computer alone.

> 4. The RRAS server may not enable IP routing.

Where I can see it?
 
Reply With Quote
 
Robert L \(MS-MVP\)
Guest
Posts: n/a

 
      04-25-2007, 05:46 PM
If the RRAS has an issue to access the DHCP for releasing the IP, it will
assign 169.254 IP. This search result may help,

routing issues on vpnResolutions: 1) if you have two NICs in the VPN server,
you may need to enable IP Routing. To do this, go to the RRAS>the Properties
of the server>IP, ...
http://www.chicagotech.net/routingissuesonvpn.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"v_iron" <(E-Mail Removed)> wrote in message news:f0nu65$o17$(E-Mail Removed)...
> Robert L (MS-MVP) :
>> We have some issues in this configuration.
>>
>> 1.The client doesn't receive IP from the DHCP, which is 169.254.x.x.

> Attached info is from server, not from client. At client here is adapter
> with 169.254.229.222 address with default routing to it.
>
>> 2. Where is the DHCP server?

> I think in PPP tunnel RAS server acts as DHCP and give 169.254.229.222
> address to remote point. Is this right? In the local network ADSL modem is
> the DHCP server.
>
>> 3. Are both sites using the same IP range 192.168.1.x?

> Office network with internet 192.168.1.0/24, additional network
> 192.168.0.0/24, tunnel 169.254.55.208 <-> 169.254.229.222, remote computer
> alone.
>
>> 4. The RRAS server may not enable IP routing.

> Where I can see it?



 
Reply With Quote
 
v_iron
Guest
Posts: n/a

 
      04-26-2007, 06:48 AM
Robert L (MS-MVP) :
> If the RRAS has an issue to access the DHCP for releasing the IP, it will
> assign 169.254 IP. This search result may help,

I change DHCP to fixed addresses so server now have 192.168.1.10 and
client 192.168.2.11 but this is not issue.

> routing issues on vpnResolutions: 1) if you have two NICs in the VPN server,
> you may need to enable IP Routing. To do this, go to the RRAS>the Properties
> of the server>IP, ...
> http://www.chicagotech.net/routingissuesonvpn.htm

Here is no rras.msc in Windows XP Pro. I set HKEY_LOCAL_MACHINE
\SYSTEM\CurrentControlSet\Services\Tcpip\Parameter s "IPEnableRouter" to
1 but no result.
And I found some peoples have the same problem as me but nobody answers
that to do in this situation.

Additional questions: can VPN route traffic without "Default gateway"
set in parameters? I mean this place (see my first message):
-->8------------------------------------------------------
....
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 169.254.55.208
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : <------
-->8------------------------------------------------------
 
Reply With Quote
 
Bill Grant
Guest
Posts: n/a

 
      04-26-2007, 07:40 AM

"v_iron" <(E-Mail Removed)> wrote in message news:f0pi0r$s0q$(E-Mail Removed)...
> Robert L (MS-MVP) :
>> If the RRAS has an issue to access the DHCP for releasing the IP, it will
>> assign 169.254 IP. This search result may help,

> I change DHCP to fixed addresses so server now have 192.168.1.10 and
> client 192.168.2.11 but this is not issue.
>
>> routing issues on vpnResolutions: 1) if you have two NICs in the VPN
>> server, you may need to enable IP Routing. To do this, go to the RRAS>the
>> Properties of the server>IP, ...
>> http://www.chicagotech.net/routingissuesonvpn.htm

> Here is no rras.msc in Windows XP Pro. I set HKEY_LOCAL_MACHINE
> \SYSTEM\CurrentControlSet\Services\Tcpip\Parameter s "IPEnableRouter" to 1
> but no result.
> And I found some peoples have the same problem as me but nobody answers
> that to do in this situation.
>
> Additional questions: can VPN route traffic without "Default gateway" set
> in parameters? I mean this place (see my first message):
> -->8------------------------------------------------------
> ...
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 169.254.55.208
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . : <------
> -->8------------------------------------------------------



No, you cannot route between subnets without a default gateway set. And
with an APIPA address (ie 169.254.x.y) you will not get a default gateway
address. APIPA is a fallback for people who accidentally leave the network
config set to automatic but do not have a DHCP server. APIPA will give them
local networking by default.

The basic problem is that your XPPro "server" is not getting addresses
from DHCP to use for the remote connection, forcing it to use APIPA
addresses (which won't route). If you cannot find out why this is not
working, delete the incoming connection and set it up again from the New
Connection wizard. Instead of using DHCP, set up a pool of addresses to use
(in the TCP/IP settings). The pool must have at least two IP addresses in it
(one for the remote client and one for the server itself). Use addresses in
the same IP subnet as the LAN machines are using. You could use IP addresses
from the high end of your DHCP scope, like 192.168.1.241 to 192.168.1.246 .

If the client gets a 192.168.1.x IP from RAS it will also get the same
IP address as its gateway address. The remote client can then see the
machines on the LAN because all 192.168.1.x traffic goes across the PPP link
and is delivered on the LAN. The server does proxy ARP on the LAN to receive
packets addressed to the remote client and forwards them across the PPP
link. It will never work with APIPA addresses.


 
Reply With Quote
 
v_iron
Guest
Posts: n/a

 
      04-27-2007, 04:51 AM
Bill Grant :
.............
> (in the TCP/IP settings). The pool must have at least two IP addresses in it
> (one for the remote client and one for the server itself). Use addresses in
> the same IP subnet as the LAN machines are using. You could use IP addresses
> from the high end of your DHCP scope, like 192.168.1.241 to 192.168.1.246 .

I do it but still no result. In any case thanks for your help. How I
understand how tunnel must work.
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem with dial-up on Windows Server Michael S. Androsov Windows Networking 0 04-29-2005 05:30 AM
OTish: NTL dial-up groups? Problem with game server Nigel M Broadband 13 04-08-2005 11:29 AM
dial-in server problem Borut Linux Networking 2 01-25-2004 03:19 AM
Problem dial-in server with internet connection Richard Boekamp Linux Networking 2 12-29-2003 02:20 PM
Dial-in server problem - RH 9 Ashoka D. Polpitiya Linux Networking 8 07-13-2003 03:34 AM



1 2 3 4 5 6 7 8 9 10 11