johnpsph
join:2003-11-16
Saint Louis, MO
 ·Charter Pipeline
| L2TP IPsec on OfficeConnect, can't see LAN
I recently set up my 3Com OfficeConnect as an L2TP server using L2TP over IPsec, but I'm having the following problem:
I can connect successfully to the OfficeConnect and ping it's LAN address (192.168.1.1) from another machine using the integrated Vista VPN client, but cannot ping any client on the OfficeConnect LAN. I'll post up some screen shots to give you an idea of my setup. The client I'm trying to ping has the following IP settings:
ip: 192.168.1.8
subnet: 255.255.255.0
DNS : 192.168.1.1
Gateway: 192.168.1.1
If anyone can make any suggestions as to settings I might want to change to be able to connect to a machine behind the OfficeConnect, I'd really appreciate it. Thanks |
|
johnpsph
join:2003-11-16
Saint Louis, MO
edit:
April 16th, @11:10PM
| All right, well, I can actually ping one client behind the OfficeConnect (an XP client), but not the 192.168.1.8 client that I WANT to ping, a Vista client. |
|
johnpsph
join:2003-11-16
Saint Louis, MO
·Charter Pipeline
| All right, sorry for all of the confusion, but I have it narrowed down to a firewall problem on my vista client. When I shut the firewall off completely, I was able to ping the client. At this point though, I'm not sure which port(s) to open. If anyone can help me out there, I'd appreciate it. Thanks |
|
Shrapnel64
Premium
join:2001-01-24
Hayes, VA | Usually allowing file and print sharing as an exception should solve that problem. |
|
NJH
join:2004-04-23
| I believe the Vista firewall blocks pings by default. If you want to be able to ping that machine you will either need to allow pings on its firewall, or as you found, disable the firewall completely. Note pings are not necessary to allow file and printer sharing, so if that is all you want to do, do as Shrapnel64 says. |
|
