asked on

Cannot telnet to Sco Unix Server thru a FVS318 Netgear VPN Router

I have a SCO Unix server at a client site that I'm trying to connect to by way of VPN. Also at the client site I have a FVS318 Netgear VPN Router - connected to the internet by cable broadband. From my location I can connect to the VPN Router without any problem, however, I can not telnet to SCO Unix server. Normally, it is an issue with the SCO Unix Server simiply adding a routing statement. Now, I have gone round about and is confused with whats going on.

My VPN is setup with 192.168.1.1 ipaddress and the server is setup with a 192.168.1.10 ipaddress. I can ping the server from the router and ping the router from the server. I can also ping the router from my VPN connection, but can not ping the server. My VPN connection is set to give me a 192.168.100.1 Virtual IP when connecting to the router. I added this routing statement to my SCO Unix server and have viewed it with netstat -r. However, when I do a ipconfig /all from my VPN connection I so not see the address 192.168.100.1 anywhere. I have also done a tracert on the domain name and no ip of 192.168.100.1.

I'm not sure what the routing statement should be nor if there should be a static route in the VPN Router.

A helpful note might be that I'm using Netgears VPN Client software, in the past I have use FVS318 to FVS318 and the routing statement worked fine. What is the issue now?

Thanks

gheist

Can you ping from client ???

cmelton

ASKER

Yes I can ping both the router and the server

SOLUTION

wesly_chen

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

gheist

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

cmelton

ASKER

I have now turned from my broadband (RoadRunner) and is testing with a dialup. As before I could not connect to the server with my broadband,however I can with my dialup. I was wrong about being able to ping the server 192.168.1.10.

The 192.168.100.1 is the virtual Ip I gave to the VPN setup in the Router and is what I setup the client software with here on my laptop. I have verified this setup with netgear and this is how the tech walked me thru to set it up.

Server Information:

# netstat -rn
Routing tables
Destination Gateway Flags Refs Use Interface
127.0.0.1 127.0.0.1 UH 2 348 lo0
192.168.1 192.168.1.10 UC 1 0 net0
192.168.1.10 127.0.0.1 UGHS 4 32 lo0
192.168.100 192.168.1.1 UGS 1 59 net0
224 192.168.1.10 UCS 0 0 net0

# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1 (192.168.1.1): icmp_seq=0 ttl=254 time=0.581 ms
64 bytes from 192.168.1.1 (192.168.1.1): icmp_seq=1 ttl=254 time=0.516 ms
64 bytes from 192.168.1.1 (192.168.1.1): icmp_seq=2 ttl=254 time=0.507 ms
64 bytes from 192.168.1.1 (192.168.1.1): icmp_seq=3 ttl=254 time=0.521 ms
64 bytes from 192.168.1.1 (192.168.1.1): icmp_seq=4 ttl=254 time=0.500 ms
64 bytes from 192.168.1.1 (192.168.1.1): icmp_seq=5 ttl=254 time=0.512 ms
64 bytes from 192.168.1.1 (192.168.1.1): icmp_seq=6 ttl=254 time=0.501 ms
64 bytes from 192.168.1.1 (192.168.1.1): icmp_seq=7 ttl=254 time=0.509 ms

--- 192.168.1.1 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 0.500/0.518/0.581 ms

# ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1): 56 data bytes
64 bytes from 192.168.100.1 (192.168.100.1): icmp_seq=0 ttl=128 time=340.355 ms
64 bytes from 192.168.100.1 (192.168.100.1): icmp_seq=1 ttl=128 time=308.302 ms
64 bytes from 192.168.100.1 (192.168.100.1): icmp_seq=2 ttl=128 time=308.246 ms
64 bytes from 192.168.100.1 (192.168.100.1): icmp_seq=3 ttl=128 time=305.393 ms
64 bytes from 192.168.100.1 (192.168.100.1): icmp_seq=4 ttl=128 time=305.955 ms
64 bytes from 192.168.100.1 (192.168.100.1): icmp_seq=5 ttl=128 time=299.889 ms
64 bytes from 192.168.100.1 (192.168.100.1): icmp_seq=6 ttl=128 time=291.974 ms

--- 192.168.100.1 ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max = 291.974/308.588/340.355 ms

# traceroute 192.168.100.1
traceroute to 192.168.100.1 (192.168.100.1), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 0.524 ms 0.449 ms 0.413 ms
2 * * *
3 * * *

Laptop Information:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Chris>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : WEBMD-NC1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-02-A5-6D-94-33

Ethernet adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : 3Com 3CRWE737A AirConnect Wireless L
AN PC Card
Physical Address. . . . . . . . . : 00-50-DA-F5-CA-A5

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN Network Driver
Physical Address. . . . . . . . . : 00-03-8A-00-00-11
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 152.163.0.0
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :

PPP adapter RoadRunner:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 66.61.159.112
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 66.61.159.112
DNS Servers . . . . . . . . . . . : 24.30.211.35
24.30.211.39

C:\Documents and Settings\Chris>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 02 a5 6d 94 33 ...... Intel(R) PRO/100 VE Network Connection - Packet
Scheduler Miniport
0x3 ...00 50 da f5 ca a5 ...... 3Com 3CRWE737A AirConnect Wireless LAN PC Card -
Packet Scheduler Miniport
0x4 ...00 03 8a 00 00 11 ...... WAN Network Driver - Packet Scheduler Miniport
0x20006 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 66.61.159.112 66.61.159.112 1
66.61.159.112 255.255.255.255 127.0.0.1 127.0.0.1 50
66.255.255.255 255.255.255.255 66.61.159.112 66.61.159.112 50
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
152.163.0.0 255.255.255.255 127.0.0.1 127.0.0.1 30
152.163.255.255 255.255.255.255 152.163.0.0 152.163.0.0 30
205.188.64.111 255.255.255.255 66.61.159.112 66.61.159.112 1
224.0.0.0 240.0.0.0 152.163.0.0 152.163.0.0 30
224.0.0.0 240.0.0.0 66.61.159.112 66.61.159.112 1
255.255.255.255 255.255.255.255 152.163.0.0 2 1
255.255.255.255 255.255.255.255 152.163.0.0 152.163.0.0 1
255.255.255.255 255.255.255.255 152.163.0.0 3 1
Default Gateway: 66.61.159.112
===========================================================================
Persistent Routes:
None

C:\Documents and Settings\Chris>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=283ms TTL=128
Reply from 192.168.1.1: bytes=32 time=387ms TTL=128
Reply from 192.168.1.1: bytes=32 time=281ms TTL=128
Reply from 192.168.1.1: bytes=32 time=392ms TTL=128

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 281ms, Maximum = 392ms, Average = 335ms

C:\Documents and Settings\Chris>ping 192.168.1.10

Pinging 192.168.1.10 with 32 bytes of data:

Reply from 192.168.1.10: bytes=32 time=334ms TTL=63
Reply from 192.168.1.10: bytes=32 time=261ms TTL=63
Reply from 192.168.1.10: bytes=32 time=284ms TTL=63
Reply from 192.168.1.10: bytes=32 time=395ms TTL=63

Ping statistics for 192.168.1.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 261ms, Maximum = 395ms, Average = 318ms

C:\Documents and Settings\Chris>ping 192.168.100.1

Pinging 192.168.100.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.100.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\Chris>

Router Information:

192.168.1.0 255.255.255.0 192.168.1.1 1 YES
24.182.89.0 255.255.252.0 24.182.89.163 1 YES
0.0.0.0 0.0.0.0 24.182.89.1 1 YES

gheist

can you ping over link from router to router ???

wesly_chen

Hi,

Your PC (A) ---- Dialup--- (internet) ---- FVS318 VPN router (C) ---- SCO Unix box (D)
(192.168.100.1 in VPN) 192.168.1.1 192.168.1.10

What type of VPN does Netgear VPN router use? IPSec or PPTP?

For originally broadband router (R) at your home,
does that router allow IPSec pass through (or setting)?
As my experience, you might need to set your broadband modem
(come with your ISP) to bridge mode (not NAT) to avoid
blocking any packet.
Then your VPN connection can be pass through broadband router (R).

Wesly

gheist

based on diagnostics you provided it seems that your NetGear router does not appear to have route via VPN to network where SCO is ( maybe IPSEC in host mode instead of net mode ???)

cmelton

ASKER

Thanks guys, I appreciate the help from both that why I split the points. However I think I had all of use pointed in the wrong direction. What I did to resolve the issue is added a routing statement on the local PC.

route add 192.168.1.0 mask 255.255.255.0 192.168.1.1 -p

after which I then was able to ping the 192.168.1.10 sco server and also telnet to it.
Thansk again for your help