Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 5834 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SSL VPN Problem with IP 10.242.2.14

DanielTenten

We have a strange Problem with one of our UTMs.

When connecting via SSLVPN Client everything seems to work, except for the client getting the IP 10.242.2.14

On this station the connection is established, but no remote host is reachable...

Tried today with 4 simultanious connections: IPs .6, .10, .18 are working fine. .14 nothing reachable

disconnected 2 Clients, reconnected in different order, so the other machine gets the .14 and now this machine has the problem and the other one is working fine.

There are no errors in the SSLVPN or the Firewall Log.

Is this on known issue? Couldn't find anything...

Any ideas how to solve this problem?

Greets

Daniel



This thread was automatically locked due to age.
Parents
  • 0

    Hi, Daniel, and welcome to the UTM Community!

    Does route print on the client PC with .14 give any clues?  When you don't have a client with the .14 IP, what happens when you ping 10.242.2.14 from the 'Suppport >> Tools' menu?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    Hi Bob,
    thanks for your reply!
    This is the result of a ping from the UTM (with no.14 client present):
    PING 10.242.2.14 (10.242.2.14) 56(84) bytes of data.
    --- 10.242.2.14 ping statistics ---
    5 packets transmitted, 0 received, 100% packet loss, time 4031ms

    At the moment the problem is not reproducable. The Client with the .14 ist working without problems...

    I will write again when the problem appears again.

    Greets Daniel
Reply
  • 0 in reply to BAlfson
    Hi Bob,
    thanks for your reply!
    This is the result of a ping from the UTM (with no.14 client present):
    PING 10.242.2.14 (10.242.2.14) 56(84) bytes of data.
    --- 10.242.2.14 ping statistics ---
    5 packets transmitted, 0 received, 100% packet loss, time 4031ms

    At the moment the problem is not reproducable. The Client with the .14 ist working without problems...

    I will write again when the problem appears again.

    Greets Daniel
Children
No Data
Unfiltered HTML