We have a user who is on the Sprint Mobile network. When he brings up Network Connect (6.0R2), his Sprint Mobile connection is terminated.
The early speculation here is that the Sprint Mobile client objects to the changes Network Connect makes to the PC routing table.
Anyone seen this with Sprint, or with another mobile card/service? Confirmation would be helpful; also any ideas for remediation. Thanks!
Thanks! The two solutions look functionally equivalent, except that the first one changes one rule, while the second one would seem to discard the entire set of rules. So as I understand it, the problem is that when the Network Connect "pseudo-interface" goes active, the Sprint SmartView client sees that as another live interface and drops out.
I have passed this back to our user and we'll see tomorrow if that fixes the issue. Thanks again.
(Don't know how I missed these in scanning the recent discussions....)