David Hettel wrote:
> I've never tried this myself, personally I'd have used dynamic IP on the
> wireless, and static on the wired. Are you defining anything else for
> the wired in your static setup beside default IP address and subnet
> mask? It's possible if you go into the advance properties for you wired
> adapters and on the Wins tab enable NetBIOS over TCP/IP that it *might*
> help. Jack, Sooner Al, Lem do you guys have any thoughts? Thanks
>
This goes beyond my experience with networks, but I don't think metrics
are the answer to the OP's issue. As I understand metrics, they
represent the cost associated with using a particular network route.
Thus, given the choice of two routes to the same destination (e.g., a
wireless connection to the Internet gateway and a wired connection to
the Internet gateway), the route with the lowest metric is the one
that's used.
I've seen setting metrics suggested as a way to force the use of a wired
connection instead of a wireless connection when both are active.
OTOH, I don't think you can force a particular app (e.g., Windows
Explorer) to use a particular network connection.
OTOH, again, it seems to me as if the route to a particular IP is only
available over one NIC, a connection to that IP should go over that
route. As I said, however, this is beyond my knowledge of how networks
operate.
As to the intermittent operation, check the topology of the network
carefully. Is the hub connected to anything other than the NICs in the
two computers? Were you careful not to use the hub's uplink port?
I've cross-posted this to microsoft.public.windowsxp.network_web because
there are folks who spend more time there than here who know more about
networking.
--
Lem -- MS-MVP - Networking
To the moon and back with 64 Kbits of RAM and 512 Kbits of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer