none
Surface Pro 2s and 3s having trouble swapping between wired and wireless networks. RRS feed

  • Question

  • I am having a problem where a Surface Pro 2 or 3 device will be swapping from the wired to the wireless network. Associates take the Surface to meetings within the building. They unplug from the wired connection at their desk and automatically connect to the wireless network we have here. This will cause the PC to be none reachable across the network. When I ping the PC it attempts to resolve the other address. (If they are on the wireless network with the wireless IP scheme, and I attempt a ping, my PC attempts to ping the wired IP address instead of the wireless IP address.)

    There appears to be a problem where the DNS server isn't resolving the names. When I attempt to ping a device, the resolved IP address will be correct, but the targeted device wont be attached to that network. This results in non connectivity. then I can't WoL, can't reboot, can't scan, can't install updates, etc. The machines are coming out of compliance because management systems can't reach them. Apparently the DNS server is resolving the incorrect IP addresses when queried. 

    Tuesday, February 16, 2016 9:35 PM

Answers

  • Hi Bullet Catcher,

                 1.>>If they are on the wireless network with the wireless IP scheme

                 What is your wireless IP scheme, does the wireless IP and wired IP in the same subnet or not? Please post the text of an unedited ipconfig /allof wired and wireless.

                 2.>>I attempt a ping, my PC attempts to ping the wired IP address instead of the wireless IP address

                  Please try to run “Nslookup”, which IP be resolved to the Surface? Wirelss IP or Wired IP? When analyze a DNS issue,plsease use “Nslookup”,”PING” may use other name server.

                 3.>> There appears to be a problem where the DNS server isn't resolving the names.

                  When the Surface join the wireless network, and get IP settings , did it register in DNS server successfully? You could run “ipconfig /registerdns” on Surface to register manually.

                  Then run “ipconfig /flushdns” on your side,clear the cache on your computer,run “Nslookup” to resolve again.

                 4. If you are using secure DNS dynamic update, please check the settings,make sure they register the record promptly, here is a link for the guide,it will be helpful:

         How to Secure DNS Updates on Microsoft DNS Servers

     

                    

      Best Regards,

    Cartman


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, February 17, 2016 6:08 AM

All replies

  • Is the wireless IP range NAT'd on the WAP?

    Depending on the WAP, you may be able to allow passthrough DHCP/DNS ip address allocation.

    Tuesday, February 16, 2016 10:00 PM
  • Hi Bullet Catcher,

                 1.>>If they are on the wireless network with the wireless IP scheme

                 What is your wireless IP scheme, does the wireless IP and wired IP in the same subnet or not? Please post the text of an unedited ipconfig /allof wired and wireless.

                 2.>>I attempt a ping, my PC attempts to ping the wired IP address instead of the wireless IP address

                  Please try to run “Nslookup”, which IP be resolved to the Surface? Wirelss IP or Wired IP? When analyze a DNS issue,plsease use “Nslookup”,”PING” may use other name server.

                 3.>> There appears to be a problem where the DNS server isn't resolving the names.

                  When the Surface join the wireless network, and get IP settings , did it register in DNS server successfully? You could run “ipconfig /registerdns” on Surface to register manually.

                  Then run “ipconfig /flushdns” on your side,clear the cache on your computer,run “Nslookup” to resolve again.

                 4. If you are using secure DNS dynamic update, please check the settings,make sure they register the record promptly, here is a link for the guide,it will be helpful:

         How to Secure DNS Updates on Microsoft DNS Servers

     

                    

      Best Regards,

    Cartman


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, February 17, 2016 6:08 AM
    1. What is your wireless IP scheme, does the wireless IP and wired IP in the same subnet or not? Please post the text of an unedited ipconfig /allof wired and wireless.

    My wired network is a 192.X.X.X/23; the wireless is 172.X.X.X/24.

    Wired ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : DHOLLAND

       Primary Dns Suffix  . . . . . . . : hix-domain.com

       Node Type . . . . . . . . . . . . : Hybrid

       IP Routing Enabled. . . . . . . . : No

       WINS Proxy Enabled. . . . . . . . : No

       DNS Suffix Search List. . . . . . : hix-domain.com

                                           hix-domain.com

                                           cinci.rr.com

    Ethernet adapter Ethernet 4:

       Connection-specific DNS Suffix  . : hix-domain.com

       Description . . . . . . . . . . . : dynadock Ethernet

       Physical Address. . . . . . . . . : 00-50-B6-68-7C-DB

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

       IPv4 Address. . . . . . . . . . . : 192.9.201.36(Preferred)

       Subnet Mask . . . . . . . . . . . : 255.255.254.0

       Lease Obtained. . . . . . . . . . : Tuesday, February 16, 2016 2:43:18 PM

       Lease Expires . . . . . . . . . . : Wednesday, February 24, 2016 2:43:17 PM

       Default Gateway . . . . . . . . . : 192.9.200.1

       DHCP Server . . . . . . . . . . . : 192.9.200.24

       DNS Servers . . . . . . . . . . . : 192.9.200.24

                                           192.9.200.18

       NetBIOS over Tcpip. . . . . . . . : Enabled

    Wireless LAN adapter Local Area Connection* 2:

       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter

       Physical Address. . . . . . . . . : B6-AE-2B-2A-05-D2

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

    Wireless LAN adapter Wi-Fi:

       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . : hix-domain.com

       Description . . . . . . . . . . . : Marvell AVASTAR Wireless-AC Network Controller

       Physical Address. . . . . . . . . : B4-AE-2B-2A-04-D3

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

    Wireless ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : DHOLLAND

       Primary Dns Suffix  . . . . . . . : hix-domain.com

       Node Type . . . . . . . . . . . . : Hybrid

       IP Routing Enabled. . . . . . . . : No

       WINS Proxy Enabled. . . . . . . . : No

       DNS Suffix Search List. . . . . . : hix-domain.com

                                           hix-domain.com

                                           cinci.rr.com

    Ethernet adapter Ethernet 4:

       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . : hix-domain.com

       Description . . . . . . . . . . . : dynadock Ethernet

       Physical Address. . . . . . . . . : 00-50-B6-68-7C-DB

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

    Wireless LAN adapter Local Area Connection* 2:

       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter

       Physical Address. . . . . . . . . : B6-AE-2B-2A-05-D2

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

    Wireless LAN adapter Wi-Fi:

       Connection-specific DNS Suffix  . : hix-domain.com

       Description . . . . . . . . . . . : Marvell AVASTAR Wireless-AC Network Controller

       Physical Address. . . . . . . . . : B4-AE-2B-2A-04-D3

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

       IPv4 Address. . . . . . . . . . . : 172.30.60.37(Preferred)

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Lease Obtained. . . . . . . . . . : Tuesday, February 16, 2016 8:25:39 AM

       Lease Expires . . . . . . . . . . : Friday, February 19, 2016 9:55:51 AM

       Default Gateway . . . . . . . . . : 172.30.60.1

       DHCP Server . . . . . . . . . . . : 192.9.200.18

       DNS Servers . . . . . . . . . . . : 192.9.200.18

                                           192.9.200.24

       NetBIOS over Tcpip. . . . . . . . : Enabled

    1. Please try to run “Nslookup”, which IP be resolved to the Surface? Wirelss IP or Wired IP?

    Nslookup Surface => DNS Server Name & IP Address (as expected)

    Address: 172.X.X.X wireless network

    192.X.X.X wired network

    Both IP addresses for each network is returned for an nslookup.

    1. When the Surface join the wireless network, and get IP settings , did it register in DNS server successfully? You could run “ipconfig /registerdns” on Surface to register manually.

    Yes, I can successfully add the Surface to the wireless network. An entry is created in the DNS server for the surface device with the wireless network’s IP address scheme.

    1. If you are using secure DNS dynamic update, please check the settings, make sure they register the record promptly, here is a link for the guide, it will be helpful:

    Additional Information

    When pining the Surface, I get consisit “Request Time Outs”

    P:\>nslookup surface2

    Server:  dcsrv01.hix-domain.com

    Address:  192.9.200.18

    Name:    surface2.hix-domain.com

    Address:  172.30.60.67

    P:\>ping surface2

    Pinging surface2.hix-domain.com [172.30.60.67] with 32 bytes of data:

    Request timed out.

    Reply from 172.30.60.67: bytes=32 time=510ms TTL=128

    Reply from 172.30.60.67: bytes=32 time=2ms TTL=128

    Reply from 172.30.60.67: bytes=32 time=2ms TTL=128

    Ping statistics for 172.30.60.67:

        Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 2ms, Maximum = 510ms, Average = 171ms

    P:\>ping -t surface2

    Pinging surface2.hix-domain.com [172.30.60.67] with 32 bytes of data:

    Reply from 172.30.60.67: bytes=32 time=2ms TTL=128

    Reply from 172.30.60.67: bytes=32 time=2ms TTL=128

    Request timed out.

    Reply from 172.30.60.67: bytes=32 time=3ms TTL=128

    Reply from 172.30.60.67: bytes=32 time=2ms TTL=128

    Reply from 172.30.60.67: bytes=32 time=3ms TTL=128

    Reply from 172.30.60.67: bytes=32 time=3ms TTL=128

    Reply from 172.30.60.67: bytes=32 time=2ms TTL=128

    Reply from 172.30.60.67: bytes=32 time=2ms TTL=128

    Reply from 172.30.60.67: bytes=32 time=2ms TTL=128

    Reply from 172.30.60.67: bytes=32 time=2ms TTL=128

    Reply from 172.30.60.67: bytes=32 time=2ms TTL=128

    Reply from 172.30.60.67: bytes=32 time=2ms TTL=128

    Request timed out.

    Ping statistics for 172.30.60.67:

        Packets: Sent = 14, Received = 12, Lost = 2 (14% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 2ms, Maximum = 3ms, Average = 2ms

    Control-C

    Attempting to ping another surface device that is connected to the wired network using a Microsoft Surface Pro 3 docking station.

    P:\>ping Surface

    Pinging Surface2.Org Domain Name [172.30.60.23] with 32 bytes of data:

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Ping statistics for 172.30.60.23:

        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    P:\>ping Surface2

    Pinging Surface2.Org Domain Name [172.30.60.23] with 32 bytes of data:

    Request timed out.

    Request timed out.

    Ping statistics for 172.30.60.23:

        Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),

    Control-C

    ^C

    P:\>nslookup Surface2

    Server:  Domain_Controller.Org Domain Name

    Address:  192.9.200.18

    Name:    Surface2.Org Domain Name

    Address:  192.9.201.14

    P:\>ping Surface2

    Pinging Surface2.Org Domain Name [172.30.60.23] with 32 bytes of data:

    Request timed out.

    Reply from 172.30.60.23: bytes=32 time=3976ms TTL=128

    Reply from 172.30.60.23: bytes=32 time=2ms TTL=128

    Request timed out.

    Ping statistics for 172.30.60.23:

        Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 2ms, Maximum = 3976ms, Average = 1989ms

    P:\>nslookup Surface2

    Server:  Domain_Controller.Org Domain Name

    Address:  192.9.200.18

    Name:    Surface2.Org Domain Name

    Address:  192.9.201.14

    A consistency I am noticing is when a Surface device goes from the wireless to the wired network, other devices are still attempting to resolve the hostname to the IP address for the wireless network. The Surface’s Wireless NIC is no longer active because now the wired Ethernet NIC is being used (through a docking station)

    Wednesday, February 17, 2016 4:28 PM
  • Hi Bullet Catcher,

    >>

    P:\>nslookup surface2

    Server:  dcsrv01.hix-domain.com

    Address:  192.9.200.18

    Name:    surface2.hix-domain.com

    Address:  172.30.60.67

    P:\>nslookup Surface2

    Server:  Domain_Controller.Org Domain Name

    Address:  192.9.200.18

    Name:    Surface2.Org Domain Name

    Address:  192.9.201.14

    P:\>ping Surface2

    Pinging Surface2.Org Domain Name [172.30.60.23] with 32 bytes of data:

    Request timed out.

    Reply from 172.30.60.23: bytes=32 time=3976ms TTL=128

    Reply from 172.30.60.23: bytes=32 time=2ms TTL=128

    Request timed out.

    Ping statistics for 172.30.60.23:

        Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

        It seems 'Surface2' have 2 IP address in wireless, since when 'Surface2' joined wired network,and it still could be ping by another IP address,it maybe another device named 'Surface2' on the network. Please check in DHCP server, if they are belongs to one device or two?

    Best Regards,

    Cartman


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Thursday, February 18, 2016 1:36 AM
  • Correct. Surface2 has 2 ip addresses. 1 IP for the wired network. 192.9.201.X and 1 for the Wireless Network. 172.30.60.X. 

    We use ACLs to allow traffic to pass through between the two subnets. 

    Thursday, February 18, 2016 4:00 PM
  • Hi Bullet Catcher,

                Do you mean the host 'Surface' usually get wireless IP ‘172.30.60.23’,and the host 'Surface2' usually get wireless IP ‘172.30.60.67’?           

          >>P:\>ping Surface

         Pinging Surface2.Org Domain Name [172.30.60.23] with 32 bytes of data:

                 

            P:\>ping Surface2

         Pinging Surface2.Org Domain Name [172.30.60.23] with 32 bytes of data:

                As you posted, no matter you ping Surface or Surface2,it always resolves to 'Surface2.Org Domain Name'.This could caused by other name sever or local cache when you run PING.

               1.Please clear the local cahe(ipconfig /flushdns),and check the local hosts file.

               2.If you have WINS server on your network,check the record about the problem host in the server.

               3.If you don't have WINS,clear the local NetBIOS cache(Nbtstat -r),and check local Lmhosts file.Or disable NetBIOS over TCP/IP,then test again.

    Best Regards,

    Cartman


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

                  

    Friday, February 19, 2016 1:22 AM
  • No device usually gets a specific IP address. We use DHCP. 

    The hosts file is empty after a ipconfig /flushdns. I don't think there should be anything in the host file. 

    No WINS server. 

    LMHosts file is also empty. 

    Another observation. 

    Given a SurfacePro3 named Surf3 attached to a Microsfot SP3 docking station, I ping from my PC, BCatcher. ping attempts to ping the wifi address of Surf3 (which I know is disabled because it is in the docking station) => Request timed out. 

    nslookup => Surf3 and addresses for 192.Wired.Network.X and 172.Wireless.network.X are returned, as expected. 

    BCatcher PC pings the literal IP address for Surf3 => Succesful ping

    BCatcher PC pings Surf3 => Request timed out. 

    It looks like there is a problem resolving the hostname when attempting to ping. I can ping the IP no problem, but the hostname must resolve to the wifi address, which is disabled. 

    Monday, February 22, 2016 6:35 PM
  • Hi Bullet Catcher,

              Have you tried disable NetBIOS over TCP/IP?

    Best Regards,

    Cartman


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Tuesday, February 23, 2016 1:00 AM