none
Thin clients connection to Terminal server RRS feed

  • Question

  • Hi All

    All of our thin clients are connected to the Terminal server, but are showing a red X next to the network connection.

    This is the same for our Terminal server, with the red X on the connection. 

    It has 2 connections, one on .106 and another on .136.

    Although it is shown as having both connections on ipconfig /all, the IPv4 config properties is shown as being on DHCP and has been for a few days now. 

    Please can anyone help ?

    Kind Regards

    Dan Mulvenna


    • Edited by Danny-M98 Friday, November 18, 2016 12:59 PM
    Friday, November 18, 2016 12:59 PM

All replies

  • Hi Mulvenna,

    >>Although it is shown as having both connections on ipconfig /all, the IPv4 config properties is shown as being on DHCP and has been for a few days now. 

    Could you please post details of information about result command to here for further troubleshooting?

    >>All of our thin clients are connected to the Terminal server, but are showing a red X next to the network connection.

    All of them were used the same router? If yes, please check if switch or router configuration is correct.

    Please run tracert command to check which hop could not be arrived.

    Best Regards

    John


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

    Monday, November 21, 2016 5:52 AM
  • Hi J

    We have disabled the secondary LAN port, leaving just 192.168.0.136 as active.

    The red X is still there on the clients and terminal but the machines can connect to the outside world fine.

    It is not an issue with a switch or the router.

    Please see attached snip.

    Kind Regards

    Dan Mulvenna

    Tuesday, November 22, 2016 12:46 PM
  • Hi Mulvenna,

    >>The red X is still there on the clients and terminal but the machines can connect to the outside world fine.

    Could you please provide details of network topology to here for further troubleshooting?

    >>We have disabled the secondary LAN port, leaving just 192.168.0.136 as active.

    Did you mean that you disabled secondary LAN port on switch?

    Please run tracert outside IP address on client and post result to here.

    Best Regards

    John


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

    Wednesday, November 23, 2016 7:18 AM
  • Hi Lii

    Please find attached the tracert for 192.168.0.136.

    As for your question regarding network topology, do you mean how our entire net work is set up, or the clients connecting to the terminal ect..?

    And no, not on the switch. The terminal server itself has 4 LAN ports (4 nic's) we disabled the 2nd one and left the first one.

    Kind Regards


    • Edited by Danny-M98 Monday, November 28, 2016 4:34 PM
    Monday, November 28, 2016 9:52 AM