colore

wifi?

33 posts in this topic

hello!

android has a so marvelous way to connect via wifi: you simple click a button, it scans for available networks and you choose to connect

while i consider myself pc advanced literate, i still cannot figure out how to do it in win7

maybe i expected it to be simple

any hint?

thanks!

0

Share this post


Link to post
Share on other sites

??? Look in the lower-right (AFAICR). It's there...

0

Share this post


Link to post
Share on other sites

Windows won't show you the wireless icon in the systray if you are already connected to a wired connection.

Here is a picture of the wireless icon:

http://ptgmedia.pearsoncmg.com/images/art_soper_win7wireless/elementLinks/soper_fig06.jpg

A = wireless connections available

B = connected to wireless network (shows signal strength)

When you click on it in the "A" state, you will see a list of available networks, including whether or not they are open or secured.

0

Share this post


Link to post
Share on other sites

Windows won't show you the wireless icon in the systray if you are already connected to a wired connection.

Here is a picture of the wireless icon:

http://ptgmedia.pearsoncmg.com/images/art_soper_win7wireless/elementLinks/soper_fig06.jpg

A = wireless connections available

B = connected to wireless network (shows signal strength)

When you click on it in the "A" state, you will see a list of available networks, including whether or not they are open or secured.

the problem is that somehow that icon doesnt appear in traybar (I probably disabled it)

isnt there any other way to bring up the window with the available wireless networks?

0

Share this post


Link to post
Share on other sites

Interesting... I see a "Active Network" that states "Public Network" of type "Local Area Connection". Are you connected by WIRED? Tripredacus specifically stated

Windows won't show you the wireless icon in the systray if you are already connected to a wired connection.
You will see HOW you are connected (at this time) by clicking "See Full Map". This will more than likely SPECIFICALLY show that you're connected via a WIRED NETWORK. Betcha! You will HAVE to disconnect the WIRE to use WIRELESS (see quote, dude)!
0

Share this post


Link to post
Share on other sites
You will HAVE to disconnect the WIRE to use WIRELESS (see quote, dude)!

indeed i am wired atm, but i still wanted to see other wireless networks! i should be able to also connect to some else wireless network, should I ?

or would like to see the available wireless connections, without having to unplug

okay, i understand i cant do it, i give up :/

Edited by colore
0

Share this post


Link to post
Share on other sites

Windows won't let you connect to a wireless network if you are connected to a wired one. The reason is because you cannot have 2 default gateways. You will need to find a third-party "site survey" software to see what networks are available. I have none to recommend, as I log into my router to use the built-in site survey function.

0

Share this post


Link to post
Share on other sites

Not true, as I found out today on my wife's laptop. (Win7 x64 as supplied straight from Dell and kept up to date from MU)

110y8ph.png

Both networks were connected simultaneously. Disconnect from either one and any internet activity continued on the other one.

(It just so happened that I did not want this behavior. I wanted it set so that if the LAN was plugged in the wireless network was disconnected. I couldn't figure out how to do this automatically when I quickly looked, so I just disconnected the wireless network and left it to NOT automatically re-connect. If it's needed, I just have to select it and click "connect" so that's easy enough.)

Cheers and Regards

Edited by bphlpt
0

Share this post


Link to post
Share on other sites

Windows 8 will let you connect to as many networks as you have devices for, but it's only going to use one *long term*. It will disable any it isn't using within a short time, as connections that may be active on it get FIN'd (or some other disconnect, of course. There can be a decent amount of time where multiple connections are active, though.

0

Share this post


Link to post
Share on other sites
You will see HOW you are connected (at this time) by clicking "See Full Map". This will more than likely SPECIFICALLY show that you're connected via a WIRED NETWORK. Betcha! You will HAVE to disconnect the WIRE to use WIRELESS (see quote, dude)!

This was not true in my wife's laptop's case. The pic I showed above is the one that showed most clearly that she was indeed connected though both connections, LAN and wireless, at the same time. When I clicked the "See Full Map", it just showed one "leg" at a time, based on the pulldown box selection. But it did show that she was connected through both connections. That screen also had options to show other "legs" that she was not connected through, such as Bluetooth.

I think the reason the OP is having problems is because of something he disabled or removed:

the problem is that somehow that icon doesnt appear in traybar (I probably disabled it)

He probably disabled/removed more than just the icon in the traybar, probably something key in the wireless system itself. My desktop doesn't have that icon or the "Manage Wireless Networks" option, but my desktop doesn't have any wireless card or driver installed. The "See Full Map" option dropdown box might show the OP whether there is a wireless connection installed, just not active, available to be connected to, but I'm not sure.

@colore, assuming you have a wireless card and driver installed in your computer and a wireless router or whatever properly set up and the two appear to be talking to each other, (you sometimes have to set the wireless side of the router up through the wired connection), what happens when you click "Connect to a network" and try to establish a connection through that wireless card? And is this a home wireless connection you are trying to establish or at an Internet cafe or hotspot or something?

Cheers and Regards

Edited by bphlpt
0

Share this post


Link to post
Share on other sites

The pic I showed above is the one that showed most clearly that she was indeed connected though both connections, LAN and wireless, at the same time.

I wonder if your wireless software has something to do with it. I see those two Intel Wireless options in your picture as well. Even so, if you are able to connect to more than 1 network at a time, you only will get one default gateway, thus internet access can be used on only one and not the other. The only potential reason I can see why you would want to connect to more than one is to use the wireless for internet, and use the physical lan to connect to network shares in a private LAN. I figured it was possible using static IPs or with other wireless software, but I typically don't even install those things and let Windows manage the wireless connections.

0

Share this post


Link to post
Share on other sites

No special wireless hardware/software installed, that I know of. Just straight from Dell and updated with MU. I did not intend the two networks to both be active at the same time and I did nothing at all special to enable it. Both networks were set up with straight stock default settings, except network name and password, of course. (They are both using the same router to connect out to the internet, if that makes any difference, so the only difference, in my case, between the two networks is the route taken from the laptop to the router, either wireless or Ethernet.) Anyway, if I am connected to the Internet through the LAN connection and have a browser open to any site at all, then disconnect/unplug the LAN and connect/enable the wireless network and click any link at all on the already opened page it goes there with no hesitation and no page refreshing necessary at all. Then if I disconnect the wireless network and plug in the LAN and click any link at all, again it goes there with no hesitation and no page refreshing necessary at all. The next link selection is not made before I am connected to the network I want to use. It makes no difference if I have both networks connected at the same time before I disconnect from one of them, or if I disconnect first, so have no Internet connection at all for a bit, before connecting the other one. If I keep both networks connected simultaneously browsing works just fine as well, though I have no idea which network it actually uses at that time. I don't have multiple different physical connections (routers/LANs) to experiment with. I wasn't trying to set it up this way, but if you want me to tell you any particular settings just let me know.

Cheers and Regards

0

Share this post


Link to post
Share on other sites

When you have BOTH networks connected, can you run an

 IPCONFIG /ALL>C:\mynicconfig.txt

and post the result?

(edit/redact sensible data, obviously)

jaclaz

0

Share this post


Link to post
Share on other sites

No special wireless software installed, that I know of.

Sure, its right in your screenshot. You have the Intel PRO/Set software, as well as Intel My WiFi installed. :whistle:

I don't know what the My WiFi software does, I haven't used it before. Maybe if I get bored later I can try to connect to wireless and wired on a notebook with stock Windows (driver only, no additional software) to see if it is possible.

Oh, you can see what network you are using by running:

netstat -v

Your Local Address column will show you which IP your NIC is using to go out into the world, from there you can determine which NIC has the default gateway allowing for internet access.

Edited by Tripredacus
0

Share this post


Link to post
Share on other sites

No special wireless software installed, that I know of.

Sure, its right in your screenshot. You have the Intel PRO/Set software, as well as Intel My WiFi installed. :whistle:

None that I installed. That came straight from Dell and I'm not even sure what part either of those plays in this situation. I did nothing to set either of them up or change anything at all different from when it came straight from Dell. The laptop is now a year old and it has been running fine all this past year with only updates from WU. Other various software has been installed, but nothing at all that has anything to do with any kind of networking or Internet access besides browers, ftp clients, etc.

I'll post the data you and jaclaz asked for when I get home later this evening.

Cheers and Regards

Edited by bphlpt
0

Share this post


Link to post
Share on other sites

i lost the rest of the conversation

is there a solution to my original post?

0

Share this post


Link to post
Share on other sites

i lost the rest of the conversation

is there a solution to my original post?

Well you gave up :w00t: :

okay, i understand i cant do it, i give up :/

You need to pay double :ph34r: to enter the game again ;)

jaclaz

0

Share this post


Link to post
Share on other sites
Sure, its right in your screenshot. You have the Intel PRO/Set software, as well as Intel My WiFi installed. :whistle:

It ends up that both of these were installed, but disabled, so they weren't doing anything.

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.

When you have BOTH networks connected, can you run an

 IPCONFIG /ALL>C:\mynicconfig.txt

and post the result?

(edit/redact sensible data, obviously)

jaclaz

Result:

Windows IP Configuration

Host Name . . . . . . . . . . . . : xxxxxxxxxxxxxx

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Broadcast

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

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

Wireless LAN adapter Wireless Network Connection 3:

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

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #2

Physical Address. . . . . . . . . : AC-72-89-E5-53-4F

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

Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection 2:

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

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter

Physical Address. . . . . . . . . : AC-72-89-E5-53-4F

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection:

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

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)

Physical Address. . . . . . . . . : AC-72-89-E5-53-52

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

Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel® Centrino® Wireless-N 1030

Physical Address. . . . . . . . . : AC-72-89-E5-53-4E

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

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : xxxxxxxxxxxxxxxxxxxxxxxxxxxx(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.1.9(Preferred)

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

Lease Obtained. . . . . . . . . . : Tuesday, December 18, 2012 6:11:36 PM

Lease Expires . . . . . . . . . . : Wednesday, December 19, 2012 6:11:39 PM

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DHCPv6 IAID . . . . . . . . . . . : xxxxxxxxxxxxxx

DHCPv6 Client DUID. . . . . . . . : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

DNS Servers . . . . . . . . . . . : 192.168.1.1

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek PCIe FE Family Controller

Physical Address. . . . . . . . . : 84-8F-69-AE-B2-22

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

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : xxxxxxxxxxxxxxxxxxxxxxx(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.1.6(Preferred)

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

Lease Obtained. . . . . . . . . . : Tuesday, December 18, 2012 6:11:25 PM

Lease Expires . . . . . . . . . . : Wednesday, December 19, 2012 6:11:24 PM

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DHCPv6 IAID . . . . . . . . . . . : xxxxxxxxxxxxxxxxxx

DHCPv6 Client DUID. . . . . . . . : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

DNS Servers . . . . . . . . . . . : 192.168.1.1

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

Tunnel adapter Local Area Connection* 15:

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

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft 6to4 Adapter

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{3F19DFB8-C95E-4A78-A1C2-DF7D1B323924}:

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

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

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

IPv6 Address. . . . . . . . . . . : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx(Preferred)

Link-local IPv6 Address . . . . . : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx(Preferred)

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

NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{5E049B58-0561-4EB0-981A-314E7A01EEFD}:

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

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{A97906ED-1A7A-4F94-9283-8FA8643676C2}:

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

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

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:

Oh, you can see what network you are using by running:

netstat -v

Your Local Address column will show you which IP your NIC is using to go out into the world, from there you can determine which NIC has the default gateway allowing for internet access.

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 ESTABLISHED

The LAN was obviously used for Internet connection..

I then unplugged the LAN, I did not refresh the browser page, and reran netstat -v

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:49226 204:http ESTABLISHED
TCP 192.168.1.6:49259 yh-in-f113:http TIME_WAIT
TCP 192.168.1.6:49260 iad23s08-in-f14:http TIME_WAIT
TCP 192.168.1.6:49268 192.168.1.1:1780 TIME_WAIT
TCP 192.168.1.9:49271 192.168.1.1:5000 TIME_WAIT
TCP 192.168.1.9:49273 192.168.1.1:5000 TIME_WAIT
TCP 192.168.1.9:49280 192.168.1.1:5000 FIN_WAIT_2
TCP 192.168.1.9:49281 192.168.1.1:5000 ESTABLISHED
TCP 192.168.1.9:49283 192.168.1.1:5000 ESTABLISHED

Wireless was used for internet connection, but the LAN still got some hits, though not unexpected..

I then replugged the LAN, I did not refresh the browser page, and reran netstat -v

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:49259 yh-in-f113:http TIME_WAIT
TCP 192.168.1.6:49260 iad23s08-in-f14:http TIME_WAIT
TCP 192.168.1.6:49292 192.168.1.1:5000 ESTABLISHED
TCP 192.168.1.6:49294
TCP 192.168.1.6:49296 192.168.1.1:5000 ESTABLISHED
TCP 192.168.1.6:49299
TCP 192.168.1.9:49271 192.168.1.1:5000 TIME_WAIT
TCP 192.168.1.9:49273 192.168.1.1:5000 TIME_WAIT
TCP 192.168.1.9:49280 192.168.1.1:5000 FIN_WAIT_2
TCP 192.168.1.9:49287 sjc-not19:http ESTABLISHED

From the greater number of hits by the router's wireless connection to the default gateway I'm guessing that it was still being used for Internet access?

I then refreshed the browser page then reran netstat -v

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:49189 download:http CLOSE_WAIT
TCP 192.168.1.6:49190 downloads:http CLOSE_WAIT
TCP 192.168.1.6:49310 shopathome:http ESTABLISHED
TCP 192.168.1.6:49311 74.63.145.142:http ESTABLISHED
TCP 192.168.1.6:49321 72.21.91.19:http TIME_WAIT
TCP 192.168.1.6:49322 72.21.91.19:http TIME_WAIT
TCP 192.168.1.6:49323 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.6:49324 a23-1-45-42:http TIME_WAIT
TCP 192.168.1.6:49325 yh-in-f101:http ESTABLISHED
TCP 192.168.1.6:49326 204.141.87.96:http ESTABLISHED
TCP 192.168.1.6:49327 a184-87-196-102:http TIME_WAIT
TCP 192.168.1.6:49328 65.121.209.8:http ESTABLISHED
TCP 192.168.1.6:49329 65.121.209.8:http ESTABLISHED
TCP 192.168.1.6:49330 199:http ESTABLISHED
TCP 192.168.1.6:49331 199:http TIME_WAIT
TCP 192.168.1.6:49332 65.121.209.8:http ESTABLISHED
TCP 192.168.1.6:49333 65.121.209.8:http ESTABLISHED
TCP 192.168.1.6:49334 65.121.209.8:http ESTABLISHED
TCP 192.168.1.6:49337 204.141.87.90:http TIME_WAIT
TCP 192.168.1.6:49340 ec2-107-23-111-131:http ESTABLISHED
TCP 192.168.1.6:49341 ec2-107-23-111-131:http TIME_WAIT
TCP 192.168.1.6:49342 65.121.209.8:http TIME_WAIT
TCP 192.168.1.6:49343 vb-in-f95:http TIME_WAIT
TCP 192.168.1.6:49344 a184-86-64-104:http TIME_WAIT
TCP 192.168.1.6:49345 a184-86-64-104:http TIME_WAIT
TCP 192.168.1.6:49346 a184-84-143-139:http TIME_WAIT
TCP 192.168.1.6:49348 edge-star-ecmp-01-ash4:https ESTABLISHED
TCP 192.168.1.6:49349 edge-star-ecmp-01-ash4:http ESTABLISHED
TCP 192.168.1.6:49351 204.141.87.120:http TIME_WAIT
TCP 192.168.1.6:49352 204.141.87.121:http TIME_WAIT
TCP 192.168.1.6:49353 204.141.87.121:http TIME_WAIT
TCP 192.168.1.9:49287 sjc-not19:http ESTABLISHED

Which seemed to make it use the LAN connection again.

I then unplugged the LAN, refreshed the browser page, and reran netstat -v

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:49189 download:http CLOSE_WAIT
TCP 192.168.1.6:49190 downloads:http CLOSE_WAIT
TCP 192.168.1.6:49311 74.63.145.142:http TIME_WAIT
TCP 192.168.1.6:49323 a23-1-45-42:http TIME_WAIT
TCP 192.168.1.6:49325 yh-in-f101:http TIME_WAIT
TCP 192.168.1.6:49326 204.141.87.96:http TIME_WAIT
TCP 192.168.1.6:49328 65.121.209.8:http TIME_WAIT
TCP 192.168.1.6:49329 65.121.209.8:http TIME_WAIT
TCP 192.168.1.6:49332 65.121.209.8:http TIME_WAIT
TCP 192.168.1.6:49333 65.121.209.8:http TIME_WAIT
TCP 192.168.1.6:49334 65.121.209.8:http TIME_WAIT
TCP 192.168.1.6:49349 edge-star-ecmp-01-ash4:http TIME_WAIT
TCP 192.168.1.9:49287 sjc-not19:http ESTABLISHED
TCP 192.168.1.9:49354 192.168.1.1:5000 TIME_WAIT
TCP 192.168.1.9:49356 192.168.1.1:5000 TIME_WAIT
TCP 192.168.1.9:49357 192.168.1.1:5000 FIN_WAIT_2
TCP 192.168.1.9:49366 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.9:49367 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.9:49368 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.9:49369 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.9:49370 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.9:49371 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.9:49372 204.141.87.96:http ESTABLISHED
TCP 192.168.1.9:49374 204.141.87.96:http ESTABLISHED
TCP 192.168.1.9:49375 a184-87-196-102:http TIME_WAIT
TCP 192.168.1.9:49376 65.121.209.8:http ESTABLISHED
TCP 192.168.1.9:49377 65.121.209.8:http ESTABLISHED
TCP 192.168.1.9:49378 65.121.209.8:http ESTABLISHED
TCP 192.168.1.9:49379 65.121.209.8:http ESTABLISHED
TCP 192.168.1.9:49380 65.121.209.8:http ESTABLISHED
TCP 192.168.1.9:49382 images-p:http TIME_WAIT
TCP 192.168.1.9:49384 199:http ESTABLISHED
TCP 192.168.1.9:49386 199:http TIME_WAIT
TCP 192.168.1.9:49387 VIP03:http ESTABLISHED
TCP 192.168.1.9:49388 VIP03:http TIME_WAIT
TCP 192.168.1.9:49389 65.121.209.8:http ESTABLISHED
TCP 192.168.1.9:49390 ec2-107-23-111-131:http ESTABLISHED
TCP 192.168.1.9:49391 204.141.87.90:http ESTABLISHED
TCP 192.168.1.9:49394 vb-in-f95:http TIME_WAIT
TCP 192.168.1.9:49395 a184-86-64-104:http ESTABLISHED
TCP 192.168.1.9:49396 a184-86-64-104:http ESTABLISHED
TCP 192.168.1.9:49397 a184-84-143-139:http TIME_WAIT
TCP 192.168.1.9:49398 204.141.87.121:http TIME_WAIT
TCP 192.168.1.9:49400 edge-star-ecmp-01-ash4:https ESTABLISHED
TCP 192.168.1.9:49401 edge-star-ecmp-01-ash4:http ESTABLISHED
TCP 192.168.1.9:49403 204.141.87.120:http TIME_WAIT
TCP 192.168.1.9:49404 204.141.87.122:http TIME_WAIT

Then I replugged the LAN, refreshed the browser page, then reran netstat -v

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:49189 download:http CLOSE_WAIT
TCP 192.168.1.6:49190 downloads:http CLOSE_WAIT
TCP 192.168.1.6:49407 192.168.1.1:5000 TIME_WAIT
TCP 192.168.1.6:49416 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.6:49418 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.6:49419 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.6:49420 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.6:49421 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.6:49422 a23-1-45-42:http ESTABLISHED
TCP 192.168.1.6:49423 65.121.209.8:http ESTABLISHED
TCP 192.168.1.6:49424 images-p:http LAST_ACK
TCP 192.168.1.6:49425 204.141.87.97:http ESTABLISHED
TCP 192.168.1.6:49426 204.141.87.97:http ESTABLISHED
TCP 192.168.1.6:49428 a184-87-196-102:http TIME_WAIT
TCP 192.168.1.6:49429 65.121.208.249:http ESTABLISHED
TCP 192.168.1.6:49430 65.121.208.249:http ESTABLISHED
TCP 192.168.1.6:49431 65.121.208.249:http ESTABLISHED
TCP 192.168.1.6:49432 65.121.208.249:http ESTABLISHED
TCP 192.168.1.6:49433 65.121.208.249:http ESTABLISHED
TCP 192.168.1.6:49434 VIP03:http ESTABLISHED
TCP 192.168.1.6:49435 data:http TIME_WAIT
TCP 192.168.1.6:49438 ec2-107-21-45-222:http ESTABLISHED
TCP 192.168.1.6:49439 204.141.87.88:http ESTABLISHED
TCP 192.168.1.6:49440 204.141.87.88:http TIME_WAIT
TCP 192.168.1.6:49443 vb-in-f95:http TIME_WAIT
TCP 192.168.1.6:49444 a184-86-64-104:http ESTABLISHED
TCP 192.168.1.6:49445 a184-86-64-104:http ESTABLISHED
TCP 192.168.1.6:49446 a184-84-143-139:http TIME_WAIT
TCP 192.168.1.6:49447 204.141.87.121:http TIME_WAIT
TCP 192.168.1.6:49449 edge-star-ecmp-01-ash4:https ESTABLISHED
TCP 192.168.1.6:49450 edge-star-ecmp-01-ash4:http ESTABLISHED
TCP 192.168.1.6:49452 edge-star-ecmp-01-ash4:http TIME_WAIT
TCP 192.168.1.6:49453 204.141.87.122:http TIME_WAIT
TCP 192.168.1.6:49454 204.141.87.122:http TIME_WAIT
TCP 192.168.1.6:49455 192.168.1.1:5000 TIME_WAIT
TCP 192.168.1.6:49456 192.168.1.1:5000 FIN_WAIT_2
TCP 192.168.1.6:49457 192.168.1.1:5000 ESTABLISHED
TCP 192.168.1.6:49458 192.168.1.1:5000 ESTABLISHED
TCP 192.168.1.9:49287 sjc-not19:http ESTABLISHED
TCP 192.168.1.9:49366 a23-1-45-42:http TIME_WAIT
TCP 192.168.1.9:49367 a23-1-45-42:http TIME_WAIT
TCP 192.168.1.9:49368 a23-1-45-42:http TIME_WAIT
TCP 192.168.1.9:49369 a23-1-45-42:http TIME_WAIT
TCP 192.168.1.9:49370 a23-1-45-42:http TIME_WAIT
TCP 192.168.1.9:49371 a23-1-45-42:http TIME_WAIT
TCP 192.168.1.9:49372 204.141.87.96:http TIME_WAIT
TCP 192.168.1.9:49374 204.141.87.96:http TIME_WAIT
TCP 192.168.1.9:49376 65.121.209.8:http TIME_WAIT
TCP 192.168.1.9:49377 65.121.209.8:http TIME_WAIT
TCP 192.168.1.9:49378 65.121.209.8:http TIME_WAIT
TCP 192.168.1.9:49379 65.121.209.8:http TIME_WAIT
TCP 192.168.1.9:49380 65.121.209.8:http TIME_WAIT
TCP 192.168.1.9:49384 199:http ESTABLISHED
TCP 192.168.1.9:49389 65.121.209.8:http TIME_WAIT
TCP 192.168.1.9:49391 204.141.87.90:http TIME_WAIT
TCP 192.168.1.9:49395 a184-86-64-104:http TIME_WAIT
TCP 192.168.1.9:49396 a184-86-64-104:http TIME_WAIT
TCP 192.168.1.9:49401 edge-star-ecmp-01-ash4:http TIME_WAIT

And I can't tell which network is being used more in this case.

Let me know if I can provide any further info for your edification.

Cheers and Regards

0

Share this post


Link to post
Share on other sites

Your wired and wireless networks are in the same subnet it appears. Either way you should have noticed the .6 and .9 addresses. But you should have tried looking at the ipconfig -all during that testing. You would have noticed a default gateway appeared on the active connection.

0

Share this post


Link to post
Share on other sites

Your wired and wireless networks are in the same subnet it appears. Either way you should have noticed the .6 and .9 addresses.

Yes I knew that, and saw that. And the point you are trying to make? I mean I had only butted into this thread when you said that you couldn't be connected to a wired and wireless network at the same time as a possible reason why colore was having problems, when my recent observations, backed up by cluberti's info re Win8, seemed to indicate that you could. Since then I've only been trying to provide requested data. :)

But you should have tried looking at the ipconfig -all during that testing. You would have noticed a default gateway appeared on the active connection.

True. Since I noticed that both networks had that when they were both connected when I did the original ipconfig -all as jaclaz suggested. That would have been easier. But then I was only following your suggestion: jaclaz.gif

Oh, you can see what network you are using by running:

netstat -v

Your Local Address column will show you which IP your NIC is using to go out into the world, from there you can determine which NIC has the default gateway allowing for internet access.

Would you like me to do any more testing and provide any more info? Did any of this give you any ideas as to what colore could do to solve his problem?

Cheers and Regards

0

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.