Tripredacus Posted December 19, 2012 Posted December 19, 2012 Here are the 2 connections:LAN - connected to a network with a domain controller (DC), but this network has no internet access.WLAN - connected to wireless router with internet accessI guess I could use the probabilities of bhplt having a DC at home to make a few trips around the universe with the Heart of Gold. jaclazOf course. I merely mention it being there because I needed to see what kind of access I had on both networks while both connections were active. I could have just said it was another computer.@myselfdiemI had noticed that as well. Of course I was not entirely concerned with trying to figure out why I couldn't access the internet... I was wondering if this is either something to do with it being a wireless connection... or if it was because I had connected to wireless last in my chain of events.
bphlpt Posted December 19, 2012 Posted December 19, 2012 (edited) Like bphlpt said when we have multiple connections (wired and wireless activated) we can see all them but the wireless connection takes precedence!But wireless did not take precedence in my case.[...]I enabled/connected to both LAN/wireless networks, set the Wireless network to "Connect automatically" and to "Connect to a more preferred network if available" then restarted the laptop so it would pick which network it wanted to use.[...]As Trip has said, both LAN and wireless use the same Gateway (and DNS) addresses. The info shown here is consistent with that previously posted, showing simultaneous connection to both networks.I then opened up a Firefox page to QVC (my wife's home page) then:[...]Result [Not showing 127.0.0.1 type connections, etc]: (Both networks connected)Active Connections Proto Local Address Foreign Address State TCP 192.168.1.6:49165 165.254.27.107:http CLOSE_WAIT TCP 192.168.1.6:49177 v-client-3b:https CLOSE_WAIT TCP 192.168.1.6:49178 sjc-not19:http ESTABLISHED TCP 192.168.1.6:49189 download:http CLOSE_WAIT TCP 192.168.1.6:49190 downloads:http CLOSE_WAIT TCP 192.168.1.6:49210 a23-1-45-42:http ESTABLISHED TCP 192.168.1.6:49211 a23-1-45-42:http ESTABLISHED TCP 192.168.1.6:49212 a23-1-45-42:http ESTABLISHED TCP 192.168.1.6:49213 a23-1-45-42:http ESTABLISHED TCP 192.168.1.6:49214 a23-1-45-42:http ESTABLISHED TCP 192.168.1.6:49215 a23-1-45-42:http ESTABLISHED TCP 192.168.1.6:49216 65.121.209.8:http ESTABLISHED TCP 192.168.1.6:49217 65.121.209.8:http ESTABLISHED TCP 192.168.1.6:49218 65.121.209.8:http ESTABLISHED TCP 192.168.1.6:49219 65.121.209.8:http ESTABLISHED TCP 192.168.1.6:49220 65.121.209.8:http ESTABLISHED TCP 192.168.1.6:49221 65.121.209.8:http ESTABLISHED TCP 192.168.1.6:49222 204.141.87.97:http ESTABLISHED TCP 192.168.1.6:49223 a184-87-196-102:http TIME_WAIT TCP 192.168.1.6:49225 images-p:http TIME_WAIT TCP 192.168.1.6:49226 204:http ESTABLISHED TCP 192.168.1.6:49227 herndon-router-1:http TIME_WAIT TCP 192.168.1.6:49229 herndon-router-2:http TIME_WAIT TCP 192.168.1.6:49231 VIP03:http TIME_WAIT TCP 192.168.1.6:49232 204:http TIME_WAIT TCP 192.168.1.6:49233 204.141.87.81:http TIME_WAIT TCP 192.168.1.6:49238 TGV:http ESTABLISHED TCP 192.168.1.6:49239 TGV:http ESTABLISHED TCP 192.168.1.6:49240 TGV:http TIME_WAIT TCP 192.168.1.6:49241 a184-86-64-104:http ESTABLISHED TCP 192.168.1.6:49242 a184-86-64-104:http ESTABLISHED TCP 192.168.1.6:49243 yn-in-f95:http TIME_WAIT TCP 192.168.1.6:49244 a184-86-64-104:http ESTABLISHED TCP 192.168.1.6:49245 a184-86-64-104:http TIME_WAIT TCP 192.168.1.6:49246 a184-84-143-139:http ESTABLISHED TCP 192.168.1.6:49247 edge-star-ecmp-01-ash4:https ESTABLISHED TCP 192.168.1.6:49248 204.141.87.72:http TIME_WAIT TCP 192.168.1.6:49250 edge-star-ecmp-01-ash4:http ESTABLISHED TCP 192.168.1.6:49251 TGV:http ESTABLISHED TCP 192.168.1.6:49252 TGV:http TIME_WAIT TCP 192.168.1.6:49253 204.141.87.27:http TIME_WAIT TCP 192.168.1.6:49254 204.141.87.27:http TIME_WAIT TCP 192.168.1.6:49255 204.141.87.72:http TIME_WAIT TCP 192.168.1.6:49256 204.141.87.72:http TIME_WAIT TCP 192.168.1.6:49257 204.141.87.72:http TIME_WAIT TCP 192.168.1.6:49259 yh-in-f113:http ESTABLISHED TCP 192.168.1.6:49260 iad23s08-in-f14:http ESTABLISHEDThe LAN was obviously used for Internet connection..So, in this case, the LAN took precedence.Cheers and Regards Edited December 19, 2012 by bphlpt
myselfidem Posted December 20, 2012 Posted December 20, 2012 (edited) I cannot proceed further than the 1st step, because I cannot see the "Manage wireless networks". !!!screenshotbut i want an alternative way to bring the "available wireless networks" window, not via any traybar icon! Go to Control Panel. Select: Category. Click on Display Network near the Network icon!Or you can use: Start | Runexplorer shell:::{ED7BA470-8E54-465E-825C-99712043E01C} (God Mode) Edited December 20, 2012 by myselfidem
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now