Small Business Server 2008 Connect Computer Progam Problem
I am deploying an SBS 2008 server and the Connect Computer Program is being a pain. I want to preface this thinking it MAY be a DNS issue (keep reading) but not really sure what it could be (I've seen and resolved dozens of issues in SBS03 with the same component, first one that has left me without a clue.
So, for starters, here are the errors:
"Http://Connect
Internet Explorer cannot display the webpage
"
IF I run the connect computer executables from a USB drive I get the following error:
"Connect Computer Program - Error
An error occured while downloading the Connect Computer application. Please run this application again."
From the server, the http://connect works fine, but from the workstations it does not work at all.
Server has IP4 and IP6 configured. Server IP is 192.168.1.6, DNS is the same.
Workstation are DHCP assigned by server, IP are 192.168.1.1xx, and DNS is 192.168.1.6.
They can PING server by name.
Interestingly, I can "PING CONNECT" on the server and get a response, but not from the workstations -- which makes me think I do have some sort of a DNS issue... but overall, everything else looks right. Overall, the DNS setup is similar to how I've done all the 03's, DNS is not showing any issues on the server, and IIS shows all the compnents. As I mentioned, they are accessible form the server itself.
So, if it is DNS, I am at a loss as to why... if its not DNS, then I was thinking security on IIS. I am able to get to https://server/remote , and also to OMA.
Thanks
So, for starters, here are the errors:
"Http://Connect
Internet Explorer cannot display the webpage
"
IF I run the connect computer executables from a USB drive I get the following error:
"Connect Computer Program - Error
An error occured while downloading the Connect Computer application. Please run this application again."
From the server, the http://connect works fine, but from the workstations it does not work at all.
Server has IP4 and IP6 configured. Server IP is 192.168.1.6, DNS is the same.
Workstation are DHCP assigned by server, IP are 192.168.1.1xx, and DNS is 192.168.1.6.
They can PING server by name.
Interestingly, I can "PING CONNECT" on the server and get a response, but not from the workstations -- which makes me think I do have some sort of a DNS issue... but overall, everything else looks right. Overall, the DNS setup is similar to how I've done all the 03's, DNS is not showing any issues on the server, and IIS shows all the compnents. As I mentioned, they are accessible form the server itself.
So, if it is DNS, I am at a loss as to why... if its not DNS, then I was thinking security on IIS. I am able to get to https://server/remote , and also to OMA.
Thanks
When you open your DHCP manager and go to Scope Options, do you see:
015 DNS Domain Name
Standard
mydomain.local
None
Philip
015 DNS Domain Name
Standard
mydomain.local
None
Philip
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I had the same problem - I was using Static IP for my workstations and i switched to DHCP and i was able to get to Http://connect and no error message using Launcher.exe
The above fix worked for me.
I had a similar issue. I had 2 NICs and when I disabled the unused one everything worked great. The DNS bindings were to the wrong NIC.
ASKER
If I dont update this, whoever finds this post, the last article was solution.