I
Interrogative
Well, for the info of anyone interested, I did find WHY though had run out
of time to stuff about properly with it all and DID get the wi-fi nics (set
up ad hoc) to talk to the wired network across the network bridge. If anyone
reading has the problem of wi-fi bridged and not talking to wired, check out
http://www.microsoft.com/windowsxp/using/networking/expert/crawford_02april22.mspx
in which my problem exists. My problem was Force Compatibility Mode and
though I haven't fixed it all as yet, I believe the above URL has one
crucial bit of missing info. I did do as it said to enforce compatibility
mode on the wi-fi NIC and suddenly the wi-fi network (after reboot of all
machines) was talking to the wired one. However, the wi-fi then lost it's
ICS connection handled on the machine that acts as the bridge to both
network. So, the wi-fi remote machine couldn't see Internet.
I BELIEVE, right now without proof, that the compatibility mode has to be
forced on both my wi-fi (done) and wired NICS on the machine acting as a
bridge.
However, I am unlikely ever to go further than I have. In attempting to get
it all working (and let's face it, the machine that would act as a bridge
talks to all networks anyway) I completely forgot that one of the machines
has no monitor or keyboard attached and is there purely to do SETI packets
and to back up some of my self employed tax data. In order to do anything at
all with that machine when it isn't playing up, I use PC Anywhere and
contact that machine via what has been a set IP number on the home network.
The damned program doesn't have a way to contact the other machine via the
network WITHOUT nominating an IP address.
So, that's the end of that. Interestingly, I will eventually WANT to set all
the networks up as an exercise one day but if anyone is having problems, the
above web site has all the answers minus that thing I think is missing.
of time to stuff about properly with it all and DID get the wi-fi nics (set
up ad hoc) to talk to the wired network across the network bridge. If anyone
reading has the problem of wi-fi bridged and not talking to wired, check out
http://www.microsoft.com/windowsxp/using/networking/expert/crawford_02april22.mspx
in which my problem exists. My problem was Force Compatibility Mode and
though I haven't fixed it all as yet, I believe the above URL has one
crucial bit of missing info. I did do as it said to enforce compatibility
mode on the wi-fi NIC and suddenly the wi-fi network (after reboot of all
machines) was talking to the wired one. However, the wi-fi then lost it's
ICS connection handled on the machine that acts as the bridge to both
network. So, the wi-fi remote machine couldn't see Internet.
I BELIEVE, right now without proof, that the compatibility mode has to be
forced on both my wi-fi (done) and wired NICS on the machine acting as a
bridge.
However, I am unlikely ever to go further than I have. In attempting to get
it all working (and let's face it, the machine that would act as a bridge
talks to all networks anyway) I completely forgot that one of the machines
has no monitor or keyboard attached and is there purely to do SETI packets
and to back up some of my self employed tax data. In order to do anything at
all with that machine when it isn't playing up, I use PC Anywhere and
contact that machine via what has been a set IP number on the home network.
The damned program doesn't have a way to contact the other machine via the
network WITHOUT nominating an IP address.
So, that's the end of that. Interestingly, I will eventually WANT to set all
the networks up as an exercise one day but if anyone is having problems, the
above web site has all the answers minus that thing I think is missing.