Results 1 to 19 of 19
  1.    #1  
    Hello, recently my sprint biz connection desktop client has started disconnecting when I am away from my desk. I am fairly confident that it is not our Internet connection but in any case, I have no way of getting it to relogin without using a remote desktop connection. Does anyone have any system for forcing reconnects regardless of the reason for a disconnect.

    thanks,

    Greg

    Using T600
  2. #2  
    I had/have the same problem. Actually, my desktop client wont even connect. Worked fine last week. then friday, I had IT rebuild my pc. Came in Saturday and installed everything again but BizCon desktop client will not connect.

    I've spent about 3 hours (honestly) with Sprint support on the phone. They are completely clueless.

    As far as I know, nothing changed here at work over the weekend, firewall that is.

    Any help would be appreciated.

    mark
  3. #3  
    gregoryw - Do you know when that started happening as in the day? I've heard from some friends that there were some network issues around the weekend time frame.

    Also is this still happening? I had one disconnect and no reconnect from this weekend but it seems to be ok now.

    One key into looking at why the desktop is not re-connecting is to look at the following two log files:

    slingshot.log
    connector.log

    in your C:\Program Files\Sprint\PCS Business Connection directory. If you find the desktop server disconnected look at the last 10 lines or so from those logs and post them here if you see something that looks unusual like errors or disconnects etc.
  4. #4  
    I have been experiencing the same problem (and timeframe). Hopefully it all goes away.
  5. #5  
    jdk2man - Same story per my previous post....Take a look at the following two log files:

    slingshot.log
    connector.log

    in your C:\Program Files\Sprint\PCS Business Connection directory. If you find the desktop server disconnected look at the last 10 lines or so from those logs and post them here if you see something that looks unusual like errors or disconnects etc.
  6. #6  
    KRamsauer - Is it still occurring or was it a weekend thing?
  7. #7  
    As far as I know, It's still a problem. Ive spent about 3 hours on the phone to Sprint. Their only reply is to configure a port in the firewall. My company doesnt do any port blocking so I cant see the problem. I had the Sprint guy email me the memo they got. here it is:

    "The BCPE IP address recently changed because Sprint migrated the application from Santa Clara to Lee's Summit, MO. Typical PE installations use outbound port 443 connectivity to hit the BCPE server. If enterprises have custom firewall rules for BCPE then the enterprises will have to change these rules to reflect the new BCPE IP address, which is 68.28.20.146. "


    So, thats why the hiccup this last weekend. But they are still messed up. As far as I can tell. I still cant connect from my computer. Handheld (t600) is fine.

    here is the out put from the connector file:
    Thu Feb 19 15:57:00 MST 2004 (3324-3328): [Config file updated.]
    Fri Feb 20 08:48:04 MST 2004 (3324-3328): [Config file updated.]
    Fri Feb 20 08:48:04 MST 2004 (3324-3328): *** ConnectionManager.notifyConfigChanged
    Fri Feb 20 08:48:05 MST 2004 (3324-3328): Using proxy configuration for Microsoft Internet Explorer.
    Fri Feb 20 08:48:05 MST 2004 (3324-3328): Connecting to 68.28.20.146:443
    Fri Feb 20 08:48:06 MST 2004 (3324-3328): Switch to SSL server
    Fri Feb 20 08:48:06 MST 2004 (3324-3328): Connecting to 66.35.228.40:443
    Fri Feb 20 08:48:28 MST 2004 (3324-3328): Cannot connect to server. Not updating the cached proxies or version.
    Fri Feb 20 08:48:28 MST 2004 (3324-3328): [Config file updated.]
    -- Begin Logging --
    Fri Feb 20 08:54:12 MST 2004 (3520-3524): Slingshot Version: 6.0.6.111 (Build: 965)
    Fri Feb 20 08:54:12 MST 2004 (3520-3524): Microsoft Windows XP. Service Pack 1 (Build 2600).
    Fri Feb 20 08:54:12 MST 2004 (3520-3524): Outlook XP.
    Fri Feb 20 08:54:12 MST 2004 (3520-3524): Win 9x or XP detected.
    Fri Feb 20 08:54:12 MST 2004 (3520-3524): Windows startup folder: C:\Documents and Settings\All Users\Start Menu\Programs\Startup
    Fri Feb 20 08:54:13 MST 2004 (3520-3524): Using proxy configuration for Microsoft Internet Explorer.
    Fri Feb 20 08:54:13 MST 2004 (3520-3524): Connecting to 68.28.20.146:443
    Fri Feb 20 08:54:13 MST 2004 (3520-3524): Switch to SSL server
    Fri Feb 20 08:54:13 MST 2004 (3520-3524): Connecting to 66.35.228.40:443
    Fri Feb 20 08:54:35 MST 2004 (3520-3524): Cannot connect to server. Not updating the cached proxies or version.
    Fri Feb 20 08:54:35 MST 2004 (3520-3524): [Config file updated.]
    Fri Feb 20 08:55:15 MST 2004 (3520-3524): [Config file updated.]
    Fri Feb 20 08:55:15 MST 2004 (3520-3524): *** ConnectionManager.notifyConfigChanged
    Fri Feb 20 08:55:16 MST 2004 (3520-3524): Using proxy configuration for Microsoft Internet Explorer.
    Fri Feb 20 08:55:16 MST 2004 (3520-3524): Connecting to 68.28.20.146:443
    Fri Feb 20 08:55:16 MST 2004 (3520-3524): Switch to SSL server
    Fri Feb 20 08:55:16 MST 2004 (3520-3524): Connecting to 66.35.228.40:443
    Fri Feb 20 08:55:38 MST 2004 (3520-3524): Cannot connect to server. Not updating the cached proxies or version.
    Fri Feb 20 08:55:38 MST 2004 (3520-3524): [Config file updated.]
    Fri Feb 20 08:55:47 MST 2004 (3520-3524): [Config file updated.]
    Fri Feb 20 08:55:47 MST 2004 (3520-3524): *** ConnectionManager.notifyConfigChanged
    Fri Feb 20 08:55:48 MST 2004 (3520-3524): Using proxy configuration for Microsoft Internet Explorer.
    Fri Feb 20 08:55:48 MST 2004 (3520-3524): Connecting to 68.28.20.146:443
    Fri Feb 20 08:55:48 MST 2004 (3520-3524): Switch to SSL server
    Fri Feb 20 08:55:48 MST 2004 (3520-3524): Connecting to 66.35.228.40:443
    Fri Feb 20 08:56:10 MST 2004 (3520-3524): Cannot connect to server. Not updating the cached proxies or version.
    Fri Feb 20 08:56:10 MST 2004 (3520-3524): [Config file updated.]
    Fri Feb 20 08:57:10 MST 2004 (3520-3720): exiting status thread
    Fri Feb 20 08:57:10 MST 2004 (3520-3524): Quitting
    -- Begin Logging --
    Fri Feb 20 08:57:19 MST 2004 (3692-3700): Slingshot Version: 6.0.6.111 (Build: 965)
    Fri Feb 20 08:57:19 MST 2004 (3692-3700): Microsoft Windows XP. Service Pack 1 (Build 2600).
    Fri Feb 20 08:57:19 MST 2004 (3692-3700): Outlook XP.
    Fri Feb 20 08:57:19 MST 2004 (3692-3700): Win 9x or XP detected.
    Fri Feb 20 08:57:19 MST 2004 (3692-3700): Windows startup folder: C:\Documents and Settings\All Users\Start Menu\Programs\Startup
    Fri Feb 20 08:57:20 MST 2004 (3692-3700): Using proxy configuration for Microsoft Internet Explorer.
    Fri Feb 20 08:57:20 MST 2004 (3692-3700): Connecting to 68.28.20.146:443
    Fri Feb 20 08:57:23 MST 2004 (3692-3700): Switch to SSL server
    Fri Feb 20 08:57:23 MST 2004 (3692-3700): Connecting to 66.35.228.40:443
    Fri Feb 20 08:57:44 MST 2004 (3692-3700): Cannot connect to server. Not updating the cached proxies or version.
    Fri Feb 20 08:57:44 MST 2004 (3692-3700): [Config file updated.]


    here is the output of the slingshot file:
    Fri Feb 20 08:48:29 MST 2004 (3896-2528): *** No cached connection to try!
    Fri Feb 20 08:48:29 MST 2004 (3896-2528): Cannot connect to server.
    Fri Feb 20 08:48:31 MST 2004 (3896-2528): Waiting for slingshot thread to exit...
    Fri Feb 20 08:48:31 MST 2004 (3896-2528): Thread exited.
    Fri Feb 20 08:48:31 MST 2004 (3896-2528): slingshot is now shut down
    Fri Feb 20 08:48:31 MST 2004 (3896-2528): Exiting.
    -- Begin Logging --
    Fri Feb 20 08:55:38 MST 2004 (2576-2580): *** No cached connection to try!
    Fri Feb 20 08:55:38 MST 2004 (2576-2580): Cannot connect to server.
    Fri Feb 20 08:55:40 MST 2004 (2576-2580): Waiting for slingshot thread to exit...
    Fri Feb 20 08:55:40 MST 2004 (2576-2580): Thread exited.
    Fri Feb 20 08:55:40 MST 2004 (2576-2580): slingshot is now shut down
    Fri Feb 20 08:55:40 MST 2004 (2576-2580): Exiting.
    -- Begin Logging --
    Fri Feb 20 08:56:10 MST 2004 (3104-2968): *** No cached connection to try!
    Fri Feb 20 08:56:10 MST 2004 (3104-2968): Cannot connect to server.
    Fri Feb 20 08:56:12 MST 2004 (3104-2968): Waiting for slingshot thread to exit...
    Fri Feb 20 08:56:12 MST 2004 (3104-2968): Thread exited.
    Fri Feb 20 08:56:12 MST 2004 (3104-2968): slingshot is now shut down
    Fri Feb 20 08:56:12 MST 2004 (3104-2968): Exiting.


    and lastly, the slingshot.cf7 file:

    host=bcpe.sprintpcs.com
    port=443
    ssl_host=scs.sprintpcs.com
    ssl_hostip=66.35.228.40
    ssl_port=443
    web_host=https://bc.sprintpcs.com
    download_host=http://bc.sprintpcs.com
    smtp_charset=us-ascii
    smtp_encoding=7bit
    use_delegate=true
    hostip=68.28.20.146
    documents_enabled=false
    documents_path=
    proxy=auto
    proxy_user=
    mail_enabled=true
    mail_system=mapi
    nt_domain=<deleted>
    mail_user=<deleted>
    enterprise=subscriber
    user=<deleted>
    remember=true
    auto_start=true


    If anyone can help, that'd be great.

    Mark
  8. #8  
    jdk2man - It is good that Sprint acknowledged the migration... :-)and those log files show the problem..... the address of

    Connecting to 68.28.20.146:443

    is failing most likely and it appears to be going to a backup which is no longer working since it migrated which is the old pre-migration address indicated by:

    Connecting to 66.35.228.40:443

    I doubt whether corporations are going to have custom Firewall rules for BCPE as that is the beauty of it in that BCPE works seamless using known and well established ports like 443.

    Was there a section in your .cf7 that you did not post that has the folllowing:

    cached_proxy_type=direct
    cached_proxy_host=68.28.20.146
    cached_proxy_port=443
    cached_proxy_auth=-1

    or was that .cf7 the entire file... minus the sensitive parts you deleted?
  9. #9  
    thats the whole file.

    I noticed that the file gets filled the first time you connect. Since I never connect, thats it.

    Mark
  10. #10  
    jdk2man - Try the following:

    1. Add the lines I had you look for to the slingshot.cf7 file

    cached_proxy_type=direct
    cached_proxy_host=68.28.20.146
    cached_proxy_port=443
    cached_proxy_auth=-1

    2. Restart your desktop connector. If that does not fix it then switch the 146 to 147 and the restart the desktop.

    Report back on the results. :-)
  11. #11  
    Nope. still doesnt connect, then it rewrites the file without the addition.

    in other words, it takes out my changes.

    heres the output from the slingshot log file:
    Fri Feb 20 12:59:00 MST 2004 (1272-3504): *** No cached connection to try!
    Fri Feb 20 12:59:00 MST 2004 (1272-3504): Cannot connect to server.
    Fri Feb 20 12:59:02 MST 2004 (1272-3504): Waiting for slingshot thread to exit...
    Fri Feb 20 12:59:02 MST 2004 (1272-3504): Thread exited.
    Fri Feb 20 12:59:02 MST 2004 (1272-3504): slingshot is now shut down
    Fri Feb 20 12:59:02 MST 2004 (1272-3504): Exiting.

    and from the connector.log:
    Fri Feb 20 12:58:37 MST 2004 (2836-3212): [Config file updated.]
    Fri Feb 20 12:58:37 MST 2004 (2836-3212): *** ConnectionManager.notifyConfigChanged
    Fri Feb 20 12:58:38 MST 2004 (2836-3212): Using proxy configuration for Microsoft Internet Explorer.
    Fri Feb 20 12:58:38 MST 2004 (2836-3212): Connecting to 68.28.20.146:443
    Fri Feb 20 12:58:39 MST 2004 (2836-3212): Switch to SSL server
    Fri Feb 20 12:58:39 MST 2004 (2836-3212): Connecting to 66.35.228.40:443
    Fri Feb 20 12:59:00 MST 2004 (2836-3212): Cannot connect to server. Not updating the cached proxies or version.
    Fri Feb 20 12:59:00 MST 2004 (2836-3212): [Config file updated.]


    i did forward the sprint message to my corporate IT just incase they are blocking something.

    this is frustraiting. Dont know why they had to change it.
    If it aint broke......

    Mark
  12. #12  
    It almost sounding like a possible firewall issue if for some reason they had a rule for it or if they are doing stateful packet inspection since it uses AES over 443 and its fallback is SSL which is an incorrect IP that is burned into the desktop... the 66.x.x.x number. One other bit of information would be to do an nslookup from a DOS prompt. of scs.sprintpcs.com and see what that returns.

    Also from a DOS command try a

    telnet 68.28..20.146 443

    and

    telnet 68.28..20.147 443

    just to see if it responds to telnet by hanging there at least. You can't simulate AES 443 traffic but if you are getting timeouts then that could explain the primary problem of why it is not getting a connection.
  13. #13  
    the nslookup returns:
    > scs.sprintpcs.com
    Server: <work domain address>
    Address: <work ip>

    Non-authoritative answer:
    Name: scs.sprintpcs.com
    Address: 68.28.20.147


    when I do a telnet session, I just get a blank screen with a blinking underline that just sits there until I start typing or press enter. then it goes back to the command prompt.

    This help?

    Mark
  14. #14  
    jdk2man - Hmm.. I've tapped out my ideas at this point... as all "appears" normal. The telnet response seems normal. The nslookup is as expected. I forgot to ask earlier... are you going against Microsoft Exchange? It looks that way from the .cf7 file but just wanted to check.
  15. #15  
    I've been having the regular disconnect problem for a while now. I decided today to uninstall and reinstall the software since my log file mentioned something about a problem with connection.exe.

    Well, now the BE desktop software can't connect to the Sprint server at all. I'll worry about it again on Monday.

    Geoffrey
  16. #16  
    gmaugham - Interesting.... What do you log files say when it tries to connect? Are they the same as the messages that jdk2man provided earlier in the post?

    Also did you re-download the software from the web site and re-install or use a copy you had from before? It should not make any difference but might be a data point.
  17. #17  
    No, it was a different message, which, of course, I neglected to write down. It specifically mentioned a problem with connection.exe, but I don't remember what the problem was.

    I re-downloaded from the web. I'll provide more information when I take a look again on Monday.

    Geoffrey
  18. #18  
    Are any of u having memory leaks with connection.exe?
    I can't use it anymore cause of that.
    Woke up one morning and found it using over 1gb of ram and 100% cpu.
  19. #19  
    Had the problem since Monday and finally got around to troubleshooting this.

    In the slingshot.cf7 file I changed the ssl_hostip=66.35.228.40 to 68.28.20.147 and it finally works.

    YMMV


    Ed.
    Ed

Posting Permissions