{5} Accepted, Active Tickets by Owner (Full Description) (4 matches)
List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.
mgrooms (4 matches)
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #1 | Reconnect attempts fail on Vista using Dialup | ike daemon | Version 2.1.5 | defect | 12/06/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
As I tested the new dialup option with the beta a few weeks ago it did work at first glance (as I wrote you). But I set up my tunnels during the same session, so I didn't realize the problem then. The problem occurs if the dialup interface goes down and up again, e.g. if I travel by train and I use my cellular data card for internet access. So you change your access points very often in conjunction with longer periods of no internet access at all. It goes like this: 1) I uninstall the VPN client (2.1.4), reboot my system and install 2.1.4 again, then I can connect without any problems with my dialup adapter. Everything else like mail, ssh and browsing works fine as it should, with and without a VPN tunnel enabled, everything is fine. 2) The problem appears after the dialup adapter goes down - it doesn't matter if I disable it manually to remove the data card or it goes down because of losing connection to a cellular access point during travelling by train. If I reconnect and the dailup adapter goes up, I can ping any IP address like before, but DNS doesn't work any longer. "ping <IP>" works, but "ping <hostname>" doesn't, neither nslookup does. I can connect to a host via ssh e.g. if I connect to its IP address, but not to its domain name. 3) Setting the DNS server IP manually doesn't help, although the same DNS server did work the first time and the server is reachable by ping. 4) I can't establish a VPN tunnel with your client then even if I connect to the IP address. 5) The only solution is to remove the Lightweight Filter, but it's not enough to disable it, I have to remove it at all. After that I can use my internet access as normal, but unfortunately without your VPN client, of course. 6) If I uninstall and reinstall again I'm back at No. 1 above... The problem is dialup-only, if I skip steps 5 & 6 and use a wired connection in my office everything works fine, but I can't use the dialup connection then until I completely remove the Lightweight Filter. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #2 | iked.exe uses 100% of CPU on windows | ike daemon | Version 2.1.5 | defect | 12/06/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Sometimes out of the blue, the iked.exe process pegs the cpu at 100%. I wasn't even transferring any data over the tunnel. I'm using 2.14 / win. I do use hibernate. I've seen this sometimes after resuming from hibernation. Have to manually kill the process. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #3 | Multiple IPs assigned to a single virtual adapter | ike daemon | Version 2.1.5 | defect | 12/06/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I am having an ongoing problem with Shrew and my Fortigate. It now works with XAuth but often I need to try and connect multiple times until it really works. It shows that it is connected and a tunnel is enabled but nothing actually happens. I am running MR7 on my Fortigate, and Vista SP1 X32 on the PC. This problem has also been reported by Roland Steber when communicating with a Lancom router which does not use DHCP over IPsec. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #4 | DNS resolution issues after standby or hibernate | dns proxy daemon | Version 2.1.5 | defect | 12/06/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
After returning from standby mode, the Shrew DNS proxy prevents DNS requests. It doesn't matter if there's a VPN connection or not. I wonder if these two firewall rules are necessary for a proper functionality of the DNS proxy. The highlighted rules are not present, when I resume working after standby mode. Restarting the services doesn't have an impact on this issue. When I stop the dtpd service the DNS requests are working fine. After rebooting the PC, the problem is gone until the next occurrence. To Reproduce: - Connect to a VPN - Disconnect - Switch the computer to standby mode - Return from standby - Try ping à This works - Try nslookup à No response VPN Client Version = 2.1.4 Windows OS Version = Windows Vista Business SP1 Gateway Make/Model = LANCOM Gateway OS Version = ? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
