Elsinore

User Forum

www.screenconnect.com
Welcome Guest Search | Active Topics | Log In | Register

Tag as favorite
Windows server 2008
Options
Previous Topic Next Topic
pwskiold
#1 Posted : Tuesday, February 14, 2012 8:08:47 AM
Rank: Newbie
Joined: 1/31/2011
Posts: 8
Location: Denmark
I have some problems getting screenconnect to work on a windows server 2008. Then I read this post with the same problem:

_________________________________________________________
"Customer Question:

Quote:
We are currently having problems connecting via a 'Attended Session' or via a 'Unattended Session' using Screen Connect when trying to connect to a Windows 2008 R2 Domain Controller or Member Server in a Windows 2008 Domain.

The Screen Connect icon appears in the notification area, however it loops around saying 'Connecting...' and 'Waiting for Connection...' and never ever establishes a connection.

The Servers are all fully Windows Updated and are on the latest Service Pack, Screen Connect version is 2.3.2058.4321.


Support Response:
The above issue was addressed in a support session and turned out to be an issue with how ScreenConnect was handling an NTLM authentication rejection from the user's proxy. We hope to have a fix for this issue in the next v2.4 pre-release build."
___________________________________________________________

I'm not sure if my license is covered with version 2.4?? Is there a work around for this problem?
Back to top
WWW
Report?
Jake Morgan
#2 Posted : Tuesday, February 14, 2012 11:09:57 PM
Rank: Administration
Joined: 4/9/2010
Posts: 871
You should be covered for 2.4 if you purchased in the last year. Are you sure you're having this exact issue? I would guess it's very rare. What version are you using now? In 2.3 we preempted auth by sending an NTLM request on the first request. A proxy server that would have otherwise let us through anonymously instead started the NTLM challenge, and in this case, one machine was on a different untrusted domain than the proxy server, so the NTLM failed. Now we wait for a proxy 407 before starting the NTLM handshake. This situation is quite rare. Are you sure you're having this issue?
Back to top
Report?
pwskiold
#3 Posted : Wednesday, February 15, 2012 7:20:12 AM
Rank: Newbie
Joined: 1/31/2011
Posts: 8
Location: Denmark
I've found the problem. It was how firewall is handeling connections between DMZ and LAN. The problem only occured on pc within network. If I use extenal then it works so I need to do some firewall digging. Thank you for your quick reply and I must say that we are very satisfied with screenconnect :-)

(The client and host just show connecting and doesn't actually get further. The description above was closest to my problem. The version I'm using is 2.3.2058.4321. I have been running screen connect successfully on different servers with port 8040 and 8041. Due to firewall issues at customers I have seen that using port 80 and 443 have a bigger chance to work. So now I have the screen connect running on a 2008 server with ports 80 and 443 open (http://87.116.41.132/). I have used the port tool you provide successfully and I'm kind of stuck of what the problem could be. I also get a "web server check - fail")
Back to top
WWW
Report? | Edit by user
Users browsing this topic
Guest
Tag as favorite
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

SoClean Theme By Jaben Cargman (Tiny Gecko)
Powered by YAF | YAF © 2003-2009, Yet Another Forum.NET