Author Topic: &RQ and VPN Client  (Read 3492 times)

0 Members and 1 Guest are viewing this topic.

Rattlehead

  • Guest
&RQ and VPN Client
« on: July 08, 2003, 11:56:17 AM »
When I use my VPN Client - VSClient Universal 4.33, &RQ just hangs and I'm not able to close it or end it. I can run &RQ again but when trying to run IE wth both VPN and &RQ results in Windows 2000 crashing and requiring a reboot.
W2K doesn't crash when VPN and IE are running. Nor does it crash when &RQ and IE are running...only when VPN client is running, &RQ goes first, then Windows.
Because I use VPN for work, I need it running, but I was wondering if anyone knows why its crashing.
Thanks.

Offline rejetto

  • Administrator
  • Tireless poster
  • *
  • Posts: 12949
    • View Profile
&RQ and VPN Client
« Reply #1 on: July 08, 2003, 10:23:35 PM »
no idea
the crash happens only if you run &RQ, or with other software also?

Rattlehead

  • Guest
&RQ and VPN Client
« Reply #2 on: July 10, 2003, 06:58:21 AM »
Only crashes when the VPN client is running.
Without VPN running, it works fine.
I can use &RQ with every app running cept for VPN Client.
Well, it doesn't exactly crash - just freezes and I can't close it, even through task man.

Oh well...

Offline TC

  • Tireless poster
  • ****
  • Posts: 117
    • View Profile
&RQ and VPN Client
« Reply #3 on: July 10, 2003, 10:14:40 AM »
When you use VPN Client, only &RQ crash or other software (eg: outlook express, or others) also?
Have you a proxy in &RQ's preferences?

What's the exact event?
&RQ open
launch VPNClient
&RQ crash

or...

VPNClient open and connected
launch &RQ
&RQ crash

and...
&RQ works fine after you restart him?

another one: Your VPNClient changes windows gateway, right?
(tip: If you have Win2k, to see net config, start -> execute -> type "cmd" -> Ok -> Type "ipconfig" Enter)

With this tests maybe we can understand what's happen

I think that the VPNC change the windows def. gateway, then &RQ hangs current TCP connection with ICQ server (or proxy), and it crash.

Maybe...
Quando digitai in command.com la prima volta 'ls' invece di 'dir', capii cosa mi stava succendendo...

Rattlehead

  • Guest
&RQ and VPN Client
« Reply #4 on: July 14, 2003, 10:08:07 AM »
Hey...thanks for the reply.

Lets see...
&RQ hangs if VPN is loaded before or after. So regardless - &RQ hangs whens VPN is running.
It just hangs and I cannot close it down. I can run another &RQ session and it'll work fine, and eventually, it'll hang.
Task man cannot kill &RQ.
Also VPNClient does not change the windows gateway.
I have a proxy in the &RQ preferences.

Don't know if any of that helps...but if theres a way to force end &RQ, be good.

Thanks.

Offline rejetto

  • Administrator
  • Tireless poster
  • *
  • Posts: 12949
    • View Profile
&RQ and VPN Client
« Reply #5 on: July 14, 2003, 10:59:36 AM »
Quote from: "Rattlehead"
Task man cannot kill &RQ.

ask god :rotfl:


sorry, no idea, never used vpn

tc, what can he do?

Offline TC

  • Tireless poster
  • ****
  • Posts: 117
    • View Profile
&RQ and VPN Client
« Reply #6 on: July 14, 2003, 03:06:09 PM »
boh... I thought that the problem was more defined, on one or more cases. It's too generic.

I usually use Micorsoft Connection to make VPN... I don't know your client software. My &RQ -never- crash or hangs when I'm using VPN connection.

Maybe the problem isn't the connection...  I have no idea.
sorry...

PS: If I've some time, I can do some test with your software (if I find it).
Quando digitai in command.com la prima volta 'ls' invece di 'dir', capii cosa mi stava succendendo...

Rattlehead

  • Guest
&RQ and VPN Client
« Reply #7 on: July 15, 2003, 06:06:04 AM »
It's okay - has me stumped too.

but if you ever 'want' to test with the software I use. I've uploaded it here:
http://home.iprimus.com.au/tsdv/VSClient.zip

My workaround is to have VPN client closed when I use &RQ. And when I need VPN, I close &RQ til I'm done.

Offline TC

  • Tireless poster
  • ****
  • Posts: 117
    • View Profile
&RQ and VPN Client
« Reply #8 on: July 15, 2003, 07:46:24 AM »
I'm downloading it...
Quando digitai in command.com la prima volta 'ls' invece di 'dir', capii cosa mi stava succendendo...