View Single Post
  #1  
Old 11-06-2013, 08:35 AM
travec travec is offline
Aspiring Member
 
Join Date: Nov 2013
Posts: 1
travec has 10 reputation points
Default Local network not accessible with vpn client

Hello,

I cannot access my local network (network shares) when connected with the avaya vpn client.

here's my routing table before connecting with the vpn client:

Code:
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x100002 ...44 45 53 54 42 00 ...... Avaya IPSECSHM Adapter - Packet Scheduler M
iniport
0x100003 ...00 ff ea 55 53 e5 ...... Avaya VPN Adapter - Packet Scheduler Minipo
rt
0x110005 ...00 13 72 1a e8 6a ...... Broadcom NetXtreme 57xx Gigabit Controller
- Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.7.133    192.168.7.54       20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.7.0    255.255.255.0     192.168.7.54    192.168.7.54       20
     192.168.7.54  255.255.255.255        127.0.0.1       127.0.0.1       20
    192.168.7.255  255.255.255.255     192.168.7.54    192.168.7.54       20
        224.0.0.0        240.0.0.0     192.168.7.54    192.168.7.54       20
  255.255.255.255  255.255.255.255     192.168.7.54          100002       1
  255.255.255.255  255.255.255.255     192.168.7.54    192.168.7.54       1
  255.255.255.255  255.255.255.255     192.168.7.54          100003       1
Default Gateway:     192.168.7.133
===========================================================================

after:

Code:
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.7.133    192.168.7.54       21
          0.0.0.0          0.0.0.0  192.168.106.115  192.168.106.115      1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.7.0    255.255.255.0     192.168.7.54    192.168.7.54       20
      192.168.7.0    255.255.255.0  192.168.106.115  192.168.106.115      1
     192.168.7.54  255.255.255.255        127.0.0.1       127.0.0.1       20
    192.168.7.255  255.255.255.255     192.168.7.54    192.168.7.54       20
  192.168.106.115  255.255.255.255        127.0.0.1       127.0.0.1       30
  192.168.106.255  255.255.255.255  192.168.106.115  192.168.106.115      30
     208.67.168.5  255.255.255.255    192.168.7.133    192.168.7.54       1
        224.0.0.0        240.0.0.0     192.168.7.54    192.168.7.54       20
        224.0.0.0        240.0.0.0  192.168.106.115  192.168.106.115      1
  255.255.255.255  255.255.255.255     192.168.7.54    192.168.7.54       1
  255.255.255.255  255.255.255.255  192.168.106.115  192.168.106.115      1
  255.255.255.255  255.255.255.255  192.168.106.115          100003       1
Default Gateway:   192.168.106.115
===========================================================================
When I'm doing a tracert to a local address example : 192.168.7.20

It ends up somewhere on the internet going through the vpn, so I tried changing the routing table like that

route change 192.168.7.0 mask 255.255.255.0 192.168.106.115 METRIC 21 IF 0x100002
route change 0.0.0.0 mask 0.0.0.0 192.168.106.115 METRIC 21 IF 0x100002

After that I ran a tracert again and it does not go through the vpn this time but all the requests are timing out.
Reply With Quote