free log
CRM

Bozteck VNCScan Community

Community makes things happen
Welcome to Bozteck VNCScan Community Sign in | Join | Help
in
Home Forums

problem connecting to existing and new clients

Last post 10-24-2006, 12:06 PM by klashlee. 24 replies.
Page 1 of 2 (25 items)   1 2 Next >
Sort Posts: Previous Next
  •  10-18-2006, 12:45 PM 1004

    problem connecting to existing and new clients

    I have been using your program for a year or so with great results.

    Starting this week I have had major issues connecting and reconnecting to existing and new clients.

    was running Ultra 1.0.1  but have been upgrading to Ultra 1.0.2

    Downloaded and installed the newest console version.  2006.10.18.8

    try to connect to an existing client and nothing happens  or  I get the message;

    "cannot connect to server"

    Through the console...

    I can see the version of VNC installed

    I can ping the client

    I can access the MMC console

    When I look at the running services,  it shows winvnc running.

    I do a remote uninstall

    look at services again and it shows the service as ..

    winvnc    status=stopping      status type=disabled

    using PSKILL,  I kill the vnc service on the machine... 

    Reinstall the Ultra app and then I can connect to them machine...  however,  after several hours or the next day..    I cannot connect again and have to repeate the above process.

    Here is a partial on the install for a given machine...   (xxx = the remote machine name)

    Installing the default settings for VNC into the remote registry. Please wait.

    regini -m \\xxx.com "C:\fastpush\vnc7\common\machine.ini"

    Installing WinVNC to C:\Program Files\Orl\VNC

    [SC] CreateService SUCCESS

    Setting VNC Helper in HKLM\Software\microsoft\windows\currentversion\run to:

    WinVNC = "C:\Program Files\Orl\VNC\winvnc.exe" -servicehelper

    \registry\machine\software\microsoft\windows\currentversion\run

    WinVNC = "C:\Program Files\Orl\VNC\winvnc.exe" -servicehelper

    Attempting to start the service.....

    SERVICE_NAME: winvnc

    TYPE : 110 WIN32_OWN_PROCESS (interactive)

    STATE : 2 START_PENDING

    (NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)

    WIN32_EXIT_CODE : 0 (0x0)

    SERVICE_EXIT_CODE : 0 (0x0)

    CHECKPOINT : 0x0

    WAIT_HINT : 0x7d0

    Icons command excuted on remote machine xxx.com

    ------------------------------------------------------------

    Fastpush to xxx.com'.

    You want to install : /ultra

    Install Vncviewer program : yes

    Create Start Menu links : no

    ------------------------------------------------------------

    A subdirectory or file \\xxx.com\c$\temp already exists.

    BeyondExec V2.05 - Spawn Remote Processes on Windows NT/2000/XP WorkStations.

    Copyright(C) 2002-2003 Craig.Peacock@beyondlogic.org

    [xxx.com] Establishing Connection . . .

    [xxx.com] BeyondExec service already installed on remote machine.

    [xxx.com] Command Successfully Issued to xxx.com on Pipe 1.

    [xxx] Process started, ProcessID = 1748, ThreadID = 1480

    [xxx] Process terminated with exit code 0 after 00:00:01.360s

    1 file(s) copied.

    *** you may notice service errors below this point. They are normal and OK ***

    BeyondExec V2.05 - Spawn Remote Processes on Windows NT/2000/XP WorkStations.

    Copyright(C) 2002-2003 Craig.Peacock@beyondlogic.org

    [xxx.com] Establishing Connection . . .

    [xxx.com] BeyondExec service already installed on remote machine.

    [xxx.com] Command Successfully Issued to xxx.com on Pipe 1.

    [xxx] Process started, ProcessID = 1408, ThreadID = 1480

    C:\WINNT>net stop winvnc

    The WinVNC service is stopping..

    The WinVNC service was stopped successfully.

    C:\WINNT>net stop winvnc4

    System error 1060 has occurred.

    The specified service does not exist as an installed service.

    C:\WINNT>regedit /s c:\temp\custom.reg

    C:\WINNT>net start winvnc

    The WinVNC service is starting.

    The WinVNC service was started successfully.

    C:\WINNT>net start winvnc4

    The service name is invalid.

    More help is available by typing NET HELPMSG 2185.

    C:\WINNT>netsh.exe firewall set portopening tcp 5900 VNC enable all

    The following command was not found: firewall set portopening tcp 5900 VNC enable all.

    C:\WINNT>netsh.exe firewall set portopening tcp 5800 VNCHTTP enable all

    The following command was not found: firewall set portopening tcp 5800 VNCHTTP enable all.

    [xxx] Process terminated with exit code 1 after 00:00:06.187s

    Press any key to continue . . .

     

    Please help!   I count on your product everyday to do my job.... 

    thanks in advance

    Kevin Lashlee

     

     

     

     

  •  10-18-2006, 2:08 PM 1005 in reply to 1004

    Re: problem connecting to existing and new clients

    I've seen something like this happen before during a deployment.  It sometimes happens if winvnc.exe hangs while the script is trying to remove it as a service.

    The easy way to remedy this is to reboot the remote computer and then simply deploy VNC to it again. 

    Thank you,

    Steve Bostedor
  •  10-19-2006, 7:52 AM 1016 in reply to 1005

    Re: problem connecting to existing and new clients

    I too have had this problem...  I have tried your suggestion to reboot the remote computer and deploy VNC again.  This works for a few hours and then quits working again.  I have also tried to uninstall the program, reboot and reinstall it and still continue that have the same problem.
  •  10-19-2006, 8:01 AM 1017 in reply to 1016

    Re: problem connecting to existing and new clients

    So that I understand properly, if you deploy VNC to a computer, it will work for a while then, out of nowhere, it will no longer accept connections?

    Best Regards,

    Samuel E. Crane
    Senior Support Specialist
    support@vncscan.com
  •  10-19-2006, 9:05 AM 1026 in reply to 1017

    Re: problem connecting to existing and new clients

    That is correct!!
  •  10-19-2006, 9:12 AM 1028 in reply to 1026

    Re: problem connecting to existing and new clients

    Is this still happening or is it something that happened a while back and quit happening?

    If it happens again, can you please try stopping and starting the vnc service on the remote comptuer to see if that resolves it?

    What antivirus, anti-spyware, or other security software is running on the computer where the vnc service hangs?

    Best Regards,

    Samuel E. Crane
    Senior Support Specialist
    support@vncscan.com
  •  10-20-2006, 8:40 AM 1030 in reply to 1028

    Re: problem connecting to existing and new clients

    I am having the problem too. 

     

    Anyone think this might be an issue of a MS update/patch doing some damage?

     

     

     

  •  10-20-2006, 8:47 AM 1031 in reply to 1030

    Re: problem connecting to existing and new clients

    Hey guys,

    The next time that this happens to someone, can you please try connecting manually using the viewer at c:\fastpush\vnc7\ultra\vncviewer.exe?  I want to see if this is a VNCScan issue or a VNC server issue.



    Thank you,

    Steve Bostedor
  •  10-20-2006, 9:13 AM 1032 in reply to 1031

    Re: problem connecting to existing and new clients

    OK...

    Still having the same problem.

    Same as everyone else. 

    Uninstall, reinstall...  works for a little while but then quits working again.

    tried what you suggested using the viewer out of the fastpush\ultra folder.   Nothing - "Cannot connect to server"

    I have uninstalled and reinstalled several times.  Made sure there were no services hanging around from the old install...  deleted the Bozteck folder ect.  on client .

    New installs and it works for a while but then just won't connect.

    If I do the de/reinstall again , it will work for a little while

    Help,  I count on your program every day !

    thanks in advance

    Kevin Lashlee

     

     

  •  10-20-2006, 9:22 AM 1034 in reply to 1032

    Re: problem connecting to existing and new clients

    I do too!  Wink [;)] 

    It sounds like the winvnc service is falling victim to something.  I'm not sure what yet but the suggestion of an MS update causing this could be the best guess so far since it's happening to so many people so suddenly. 

    If you just stop and restart the VNC service on the remote computer as opposed to a reinstall, does it wake the service back up?  I'm trying to find a way to stop the bleeding while we find the root cause and if this works, I can get you a script as a before action that can be run to make sure that the server is responding.

    Thank you,

    Steve Bostedor
  •  10-20-2006, 9:39 AM 1035 in reply to 1034

    Re: problem connecting to existing and new clients

    Tried a Stop and Start service from the console.

    No Luck

     

  •  10-20-2006, 9:46 AM 1036 in reply to 1035

    Re: problem connecting to existing and new clients

    FYI

    After I did the Stop / Start service and could not connect ,  I tried to just do a reinstall over the top.

    That did not work.   I looked at the MMC through the console and the services on the client.

    The Winvnc service is now  showing

    Status= stopping

    Will have to us PSKill to kill the service and then  un/reinstall.

    Kevin

     

  •  10-20-2006, 9:51 AM 1037 in reply to 1036

    Re: problem connecting to existing and new clients

    On that computer where it was having a hard time stopping, what security software is installed?  For instance, what antivirus, anti-spam, etc?

    Thank you,

    Steve Bostedor
  •  10-20-2006, 9:57 AM 1038 in reply to 1037

    Re: problem connecting to existing and new clients

    Symantec Antivirus Corporate Edition Version 10x

    This has been running for several years with automatic def updates.

     

    Also,

    Just did the PSKill  and then just reinstalled over the top and it is now connecting.  Same as before,  after some period of time it quits accepting new connections.

    I have a couple of  other computers that are  constantly connected to that server.   As long as you do not close the  vnc connection, they keep working.   If you close and try to reconnect, they do not connect.

    Just trying to give you all I can to help you resolve the issue.

     

  •  10-20-2006, 10:05 AM 1039 in reply to 1038

    Re: problem connecting to existing and new clients

    As detailed info as possible is much appreciated.  I'm trying desperately to reproduce it here with no luck so far. 

    When did this start happening?  Is there anything in the application event log on the remote comptuer that shows clues? 

    If you deploy TightVNC or a different flavor of VNC to the server, does the same thing happen?

    Thank you,

    Steve Bostedor
Page 1 of 2 (25 items)   1 2 Next >
View as RSS news feed in XML
Powered by Community Server, by Telligent Systems