cortexodus
[H]ard|Gawd
- Joined
- Feb 20, 2009
- Messages
- 1,614
Here's the breakdown:
There is a notebook machine attached to a domain that is currently sitting in a docking station. That docking station is wired up with physical LAN. Also, the notebook is connected to a WiFi AP that reaches the same network. Basically, one machine, two network devices, both connecting to the same domain with a different IP for each device. Everything is peachy for that notebook as far as network/internet access goes.
I'm at a workstation also attached to the same domain. I can reach the admin share of the notebook system's HDD. I can remotely reach its registry as well.
I would like to RDP to that machine but, I am unable to. I also cannot ping it. The DNS only seems to want to resolve the physical LAN IP but, it acts like it's not "there". If I flush my local DNS cache and attempt to ping again, it pulls the same IP as before (the physical LAN link) and never responds.
Terminal services are enabled on the notebook and I have no issue at all reaching it for remote desktop if one or the other network connections is disabled. If both the LAN and the WiFi are active at the same time, I cannot RDP.
I would really like a way to RDP to that notebook with it remaining in that configuration and/or determine what the IP is for that machine for BOTH network links.
Theories?
There is a notebook machine attached to a domain that is currently sitting in a docking station. That docking station is wired up with physical LAN. Also, the notebook is connected to a WiFi AP that reaches the same network. Basically, one machine, two network devices, both connecting to the same domain with a different IP for each device. Everything is peachy for that notebook as far as network/internet access goes.
I'm at a workstation also attached to the same domain. I can reach the admin share of the notebook system's HDD. I can remotely reach its registry as well.
I would like to RDP to that machine but, I am unable to. I also cannot ping it. The DNS only seems to want to resolve the physical LAN IP but, it acts like it's not "there". If I flush my local DNS cache and attempt to ping again, it pulls the same IP as before (the physical LAN link) and never responds.
Terminal services are enabled on the notebook and I have no issue at all reaching it for remote desktop if one or the other network connections is disabled. If both the LAN and the WiFi are active at the same time, I cannot RDP.
I would really like a way to RDP to that notebook with it remaining in that configuration and/or determine what the IP is for that machine for BOTH network links.
Theories?