• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 127
  • Last Modified:

http://connect from W7 clent does not work on sbs2011 hosted on hyper-v host

Hi all you experts.

I have a tricky question for you.

My setup is as follows

Physical machine, Dell PE T6200  with  W2K8R2 with hyper-v that is hosting SBS2011 as a virtual machine. install worked fine, all latest patches installed as of yesterday.

Klient W7P connected to same network gets ip via DHPC OK, ping to  sbs2011 server works fine, dns on klient is set to SBS2011 server.
connecting to fileshares on SBS2011 works fine when logging on with domain account.

but http://connec does not work, laucher.exe from usb stick does not work, manually connecting to domain via member to workgroup or domain settings.

Please help me I dont have a clue what to try more right now.
0
Christopher_it-tude
Asked:
Christopher_it-tude
  • 9
  • 8
  • 4
1 Solution
 
smckeown777Commented:
Few questions if you can help...

1) Klient W7P connected to same network gets ip via DHPC OK - DHCP from where? The SBS server?

2) manually connecting to domain via member to workgroup or domain settings. - are you saying you can't connect to the domain manually here?

3) In reference to number 2 above - you then say 'connecting to fileshares on SBS2011 works fine when logging on with domain account.' - domain account from another machine? Or you mean a regular account logging into the server and accessing fileshares?

From client machine when you ping the sbs server - what IP does it return? IPv4 address or the IPv6?
If you ping 'connect' do you get the same IP returned?

Does http://connect work from the server itself?
0
 
Christopher_it-tudeAuthor Commented:
Hi,  answer to the questions are

1) W7P gets DHCP ip from SBS server, including  correct DNS IP to sbs server

2) Connecting manually I get the following error when typing in domain to connect to,:

a) sbsdomain ( without suffix .local)= popup for typing in admin account and password, then after 1 minute errormessage cannot find domain controller

b) sbsdomain.local =not even questionabout admin account and passord, only cannot find domain controller

3)Connecting with regular account , in this case domain admin account on sbs server, and then I can access fileshares and shared printers.

I will be onsite tomorrow morning to continue troubleshooting, and I will try to ping sbs server name, will be back with result then.

running http://connect  from server return message that this a sbs server and it cannot connect to  aothe sbs server, it looks like it is working as it should.
0
 
smckeown777Commented:
Cool, last thing, on the SBS Console on the server, in the Network section, Connectivity

Click on the 'Fix My Network' wizard - does it find any issues?

The stuff with the manual domain join says to me your DNS server(or in the DNS Console) isn't listening to the right network IP address, running the Fix My Network will show this problem and fix it
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
smckeown777Commented:
Last thing - the SBS itself - what have you set for the primary DNS server? Anything in the secondary?

Primary should be the IP of the sbs server
Secondary should be blank
0
 
Christopher_it-tudeAuthor Commented:
I will try the fix my network tomorrow

My own experience  when comparing sbs to normal server is that you should only use the wizards, manually changing settings as you normaly would on a nonsbs server only messes things up

Primary DNS  on sbs itself is set so sbs own IP, no secondary ip.
0
 
smckeown777Commented:
Yep I agree, just checking as not everyone follows those rules!!
Cool, try the fix wizard to see, and the results of the ping tests thanks...
0
 
Rob WilliamsCommented:
I have blogged the common reasons why http://connect  fails, you may find reviewing the article will help
http://blog.lan-tech.ca/2012/06/07/sbs-connect-connectcomputer-wizard-fails/
0
 
Christopher_it-tudeAuthor Commented:
I have some updates !!

as I described earlier I have windows 2008 r2 hyper-v server (hyperv) as host with two guest virtual machines on them-

One is sbs2011(sbs2011)  and one is windows server 2008R2( appsrv)

When testing to ping "sbs2011" from host server "hyperv"  I only get IPV6 answers
but when testing to ping "SBS2011" from "appsrv" I get ipv4 answer.

So my conclusion is that someting is not correct with routing to and from virtual to physical nics.

physical server dellT620 has two nics.
One nic has fixed ip dedicated to physical server
one nic is set up as virtual network for virtual machines.( uncheck allow management... box)

What am I missing ??
0
 
Rob WilliamsCommented:
>"When testing to ping "sbs2011" from host server "hyperv"  I only get IPV6 answers"
That is normal.
For an IPv4 ping try
ping -4  <address or name>

Have you reviewed the list (link) I provided?  It can be multiple NIC's enabled on the client, incorrect DNS (i.e. multiple entries), DNS suffix missing, or more.
0
 
Christopher_it-tudeAuthor Commented:
ping -4 servername works fine, but not ping connect or ping -4 connect

I have tried all points in the link you provided, but still no luck.

Since I can use http://connect from the other virtual server on the same virtual network as sbs2011 I am sure it must be something wrong with DNS lookups not working as they should.
0
 
Rob WilliamsCommented:
Could you please post the results of ipconfig /all  from both the SBS and the problematic PC.
0
 
Christopher_it-tudeAuthor Commented:
C:\Users\admin>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : SBS2011
   Primary Dns Suffix  . . . . . . . : jambotours.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : jambotours.local

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada
pter
   Physical Address. . . . . . . . . : 00-15-5D-35-14-00
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::87e:2c49:faa:5948%10(Preferred)
   Link-local IPv6 Address . . . . . : fe80::ccdc:7856:e291:3071%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 172.31.53.21(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 172.31.53.1
   DHCPv6 IAID . . . . . . . . . . . : 234886493
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-CF-E5-C1-00-15-5D-35-14-00

   DNS Servers . . . . . . . . . . . : fe80::ccdc:7856:e291:3071%10
                                       172.31.53.21
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{2D3640A1-7991-44E4-99D3-D7C3B8560D4C}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\admin>


















C:\Users\test>ipconfig /all

IP-konfiguration för Windows

   Värddatornamn . . . . . . . . . . : Dator2
   Primärt DNS-suffix. . . . . . . . :
   Nodtyp. . . . . . . . . . . . . . : Hybrid
   IP-routning aktiverat . . . . . . : Nej
   WINS-proxy aktiverat. . . . . . . : Nej
   Söklista för DNS-suffix . . . . . : jambotours.local

Ethernet-anslutning Anslutning till lokalt nätverk:

   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connecti
on
   Fysisk adress . . . . . . . . . . : 18-03-73-20-BF-F7
   DHCP aktiverat. . . . . . . . . . : Nej
   Autokonfiguration aktiverat . . . : Ja
   Länklokal IPv6-adress . . . . . . : fe80::fcc0:e880:932d:bdb1%11(Standard)
   IPv4-adress . . . . . . . . . . . : 172.31.53.160(Standard)
   Nätmask . . . . . . . . . . . . . : 255.255.255.0
   Standard-gateway. . . . . . . . . : 172.31.53.1
   IAID för DHCPv6 . . . . . . . . . : 236454771
   DUID för DHCPv6-klient. . . . . . : 00-01-00-01-17-C7-AA-49-18-03-73-20-BF-F7

   DNS-servrar . . . . . . . . . . . : 172.31.53.21
   NetBIOS över TCP/IP . . . . . . . : Aktiverat

Tunnelanslutning: isatap.{B33BB466-AF7D-4135-8520-8E7A61D20993}:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Microsoft ISATAP Adapter
   Fysisk adress . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiverat. . . . . . . . . . : Nej
   Autokonfiguration aktiverat . . . : Ja

Tunnelanslutning: Anslutning till lokalt nätverk* 3:

   Tillstånd . . . . . . . . . . . . : Frånkopplad
   Anslutningsspecifika DNS-suffix . :
   Beskrivning . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Fysisk adress . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiverat. . . . . . . . . . : Nej
   Autokonfiguration aktiverat . . . : Ja

C:\Users\test>
0
 
Rob WilliamsCommented:
The only issue I see is the client is statically assigned an IP rather than using DHCP.  Though it should work, this has been known to be an issue in some cases.  The SBS should be the DHCP server.

Routing and your Hyper-V NIC configuration should be fine as you can ping at least the IP.

The other thought would be to disable the firewall on the SBS.  I have seen cases where one firewall rule may block a required port or service to complete the wizard.

Have you run the fix my network wizard as suggested by others?
0
 
Christopher_it-tudeAuthor Commented:
I have tried both with dhcp on or off on sbsserver  and client with dhcp assigned ip and with static ip, same error.

( On the same network there is an sbs2003 in production now, this one I am replacing, that I cannot disturb since it is an production environment.)

test case 1 DHCP is turned on  on the sbs server and client and server is  on isolated switch, no internet access

test case 2 DHCP is off on the sbsserver and client with static ipadress, wit domain suffix added manually.

I have symantec endpoint protection installed on sbsserver and on host server so it is controlling the firewall, but there is no difference if I disable antivirus SW.

 I have tried fix my network.
0
 
Rob WilliamsCommented:
You cannot have 2 SBS servers on the same network, after 21 days one will start shutting itself down, however the other issue is it causes all sorts of DNS problems.  Make sure they are on isolated switches as you described.

Since you are trying to repair and do this properly I would leave DHCP enabled on the SBS and have clients obtain an address using DHCP.

Symantec is notorious for playing havoc with the connect wizard both server and client side.

There is a log file created on the connecting PC which you can check, but I am doubtful you got far enough in the "connect" process for it to be generated:
C:\Program Files\Windows Small Business Server\Logs\ConnectComputer.log


If on the connecting PC you run nslookup you should receive replies similar to the following.  Is that the case?  If not, does it work from the other virtual server?

C:\>nslookup jambotours.local
Server:  SBS2011.jambotours.local
Address:  172.31.53.21
Name:    jambotours.local
Address:  172.31.53.21

C:\>nslookup SBS2011
Server:  SBS2011.jambotours.local
Address:  172.31.53.21
Name:    SBS2011.jambotours.local
Address:  172.31.53.21
0
 
Christopher_it-tudeAuthor Commented:
from other virtual  server "hyperv" I get

C:\Users\admin>nslookup connect
Server:  sbs2011.jambotours.local
Address:  172.31.53.21

Name:    connect.jambotours.local
Addresses:  fe80::ccdc:7856:e291:3071
          172.31.53.21


C:\Users\admin>nslookup jambotours.local
Server:  sbs2011.jambotours.local
Address:  172.31.53.21

Name:    jambotours.local
Address:  172.31.53.21


C:\Users\admin>nslookup sbs2011
Server:  sbs2011.jambotours.local
Address:  172.31.53.21

Name:    sbs2011.jambotours.local
Address:  172.31.53.21

Everything looks fine !!


from W7P client I get:

C:\Users\test>nslookup sbs2011
Server:  unknown
Address:  172.31.53.21


C:\Users\test>nslookup connect
no connection, error, etc etc ....



witch server will shut down after 21 days ?

How is the days counted ? Has it started already and cannot be stopped even if they are on seperate network from now on? please explain.

I wil try and remove symantec AV.

Many thanks for your help so far, you are a life saver :)))
0
 
Rob WilliamsCommented:
>>"C:\Users\test>nslookup sbs2011
>>   Server:  unknown
>>   Address:  172.31.53.21 "


From the PC does
nslookup sbs2011.jambotours.local
resolve correctly?
Might help to isolate if IP or suffix issue.

Not 100% sure about all the 21 day limit scenarios, but SBS 2003 has a built-in "time bomb" which is triggered by having another Server which is authoritative for the same domain name (i.e. a DC) that is not a member of the SBS domain on the same network, or if you remove any of the FSMO roles from the SBS.  SBS 2003 will start after 7 days automatically shutting down about every hour.  This can be extended to 21 days with a hotfix, but no longer.  Though I have never tested SBS 2008/2011 they should have the same limitation but the default is 21 days instead of 7.  If you remove the second SBS server from the same network segment it should eliminate the problem, so long as you have not transfered any of the SBS roles.  If you remove the FSMO roles the counter starts and cannot be reversed.
0
 
Christopher_it-tudeAuthor Commented:
Could i be a problem with Large Send Offload ?I Will try it this afternoon.

About sbs shutting down after 21 days, since I am not doing a migration but setting up two different domains, domainA sbs2003, and domainB sbs2011, will the countdown start anyway
0
 
Rob WilliamsCommented:
Large send Offload can affect performance, depending on the NIC drivers, but I can see no way it would affect http://connect

You can have 2 SBS servers on the same network segment if they manage different domains, however it is strongly discouraged.  SBS should be the DHCP server for your domain, that is not possible with 2 SBS servers.  Also it can play havoc with DNS, which is your current problem already.

Did   nslookup sbs2011.jambotours.local
resolve correctly? as asked above?
0
 
Christopher_it-tudeAuthor Commented:
I have finally figured it out, after uninstalling Symantec endpoint  protection from the hostserver it started to work !! Have added four computers so far without any problem
0
 
Rob WilliamsCommented:
As mentioned earlier; "Symantec is notorious for playing havoc with the connect wizard"  :-)
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

  • 9
  • 8
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now