Justin said:
Well you got my pointed in the right direction, I ended up just clearing my
routing table (route -f) and that seems to have fixed the problem
After more investigation, I've discovered that this solution only works for
the first time I connect. I've discovered that I can force the connection by
manually entering the route and specifying the interface I want to use. I
could probably write this into a script, but it seems cumbersome for
something that should work. I can only assume that there are other people at
my University who use their machines in the same configuration and they can't
all be having problems. Perhaps I should add that this same symptom is
displayed no matter what wireless network I'm connected to.
What seems to happen is that Windows will try to find the correct interface
and adds that to the routing table, however since the ethernet is
disconnected, it cannot be added and therefore the connection fails. How does
Windows decide which interface to try? Perhaps it is because the ethernet
card has a lower interface number (i.e. 8 whereas the wireless card is 13).
BTW, I have an Intel 3945ABG card. I wonder what would happen if the roles
were reversed, any way to try this out?