Network Connect问题

简介:
本文出自Simmy的个人blog:西米在线  http://simmyonline.com/archives/168.html
 
东莞某用户使用Juniper Network Connect 链接USA office时出现此故障,询问后得知只有此用户有这种情况。
 
显示:
Network Connect会话已终止。是否要重新连接?(nc.windows.app.23712)
 
百度后发现有用的资料不多,搜索英文信息或国外用软件时,还是google好使,一下子定位到Juniper的KB中。找到方法,测试,bingo!
 
Solution:
To manually remove the Network Connect virtual adapter on Windows XP go to the Control Panel > System > Device Manager and delete the Juniper Network Connect virtual adapter from the Network Adapters.  If you do not see the Network Connect virtual adapter listed, select  "Show hidden devices" from the "View" drop-down menu on the toolbar in the Device Manager window.
 
Alternatively, to remove the Network Connect Virtual Adapter right-click on the adapter and choose "uninstall".
A new adapter will be reinstalled the next time a Network Connect session is launched.
 
在测试的过程中,有一点,我把Juniper Network Connect virtual adapter 删了,如何找回来呢 ?询问用户后,得知他们当时装就是上NC所要connect的那个网址装的,于是连上,在页面上先点卸载,然后再安装,这样virtual adapter 就又出来了,olay!



















本文转simmy51CTO博客,原文链接:http://blog.51cto.com/helpdesk/138236 ,如需转载请自行联系原作者
相关文章
|
Arthas 测试技术 网络安全
The telnet port 3658 is used by process
是否在本地使用Arthas的时候,遇到The telnet port 3658 is used by process 34725 instead of target process 44848, you will connect to an unexpected process的异常,其实解决方法很简单。
1296 0
The telnet port 3658 is used by process
|
5月前
|
存储 Cloud Native Linux
Failed to open/create the internal network ‘HostInterfaceNetworking-VirtualBox Host-Only Ethernet
Failed to open/create the internal network ‘HostInterfaceNetworking-VirtualBox Host-Only Ethernet
|
6月前
|
Kubernetes 网络协议 容器
kubectl命令报错:Unable to connect to the server: dial tcp XXX:16443: connect: no route to host
kubectl命令报错:Unable to connect to the server: dial tcp XXX:16443: connect: no route to host
293 0
|
10月前
|
Android开发
Error connecting to the service protocol failed to connect to错误
Error connecting to the service protocol failed to connect to错误
The connection to the server ip:6443 was refused - did you specify the right host or port
The connection to the server ip:6443 was refused - did you specify the right host or port