the wharf rat wrote:
> In article <>,
> Mr. Arnold <MR. > wrote:
>> Yes, you can do that, because the computer has lost the IP from the DHCP
>> server on the network, which should an IP that starts with 169 that has been
>
> Well, look, if he has a wired nic and a wireless nic and he gets
> an address on one it shouldn't mess with the route to the other.
>
Look, if you know anything about wireless, then you will know that you
can connect with a wire nic with no problem and get a valid IP from the
DHCP server on the router.
Then on the other hand with the same machine using wireless, it has
problems for whatever reason with the wireless and can loose the IP, not
obtain an IP from the DHCP server nor use a static IP on the router at
the drop of a hat, which the O/S will assign the 169 IP if the DHCP
server is in play, because the machine really has no valid connection to
the wireless side of the router, even with 100% signal strength between
the router and the wireless nic.
I have also seen the situation on more than a few occasions where two
Windows machines in ad-hoc mode will loose the connection and not be
able to communicate ever again with the setup.
If you have spent any time in a wireless NG to help posters, then you
would know how flaky a wireless situation can be, as opposed to a wire one.
I myself, I wouldn't be doing anything with Verizon when it comes to
computers and networking -- not with Vista.
Windows O/S any form of it has had problems with wireless over the years
and is a shoot from the hip in some cases. All you have to do is post to
a wireless NG and let them tell you.