Duane Arnold wrote:
> (E-Mail Removed) (JKJK) wrote in
> news:(E-Mail Removed) om:
>
>> Hi, I have a desktop pc and a tablet pc(just think laptop). Anyway I
>> brought the netgeat MA111 for the pc so I could network the two. At
>> first it went great, better than great it was perfect, I could surf
>> the net from bed, transfer files etc. But recently I have had some
>> serious problems. One day I spent a few hours trying to troubleshoot
>> them, and then suddenly it started to work and I could ping each
>> other and ICS was working. I woke up the next day, turned it all on
>> and it wasn't working.
>>
>> What make it extremely weird is that both say they are connected with
>> a strong signal strength. I can see the SSID I make on the pc on the
>> tablet and try to join it and it seems to work. But I can't even ping
>> each other. I have PAcketMon running and it detects the ip of the
>> tablet trying to do stuff, so there is definitely a connection, so I
>> think the problem is software...
>> I have tried to set the ips and subnet masks to 192.168.0.1/2 and
>> 255.255.255.0 and then try to ping each other, and I can see in
>> PacketMon one ip sending a packet to the other but I can't actually
>> ping each other. If I leave windows to set the ips and subnet, the
>> ips are 169.254.167.61 169.254.141.238, with a subnet mask of
>> 255.255.0.0( the uni network has the same subnet so I don't think
>> that is good). Anyway PacketMon picks up allot of packets, going
>> from an ip to some other ips, always with a 255 in them, i.e UDP
>> from 169.254.167.61:137 to 169.254.255.255:137 size 78... in the
>> netgear config thing, its also weird because under site survey it
>> has something with a mac of
>> 02.09.36.A0.86.D2 and it stays there even with the tablet pc off....
>>
>> I've tried to give you as much information as possible. Hopefully you
>> can help, Thanks in advance
>>
>> P.S. firewall off when testing
>>
>
> Bottom line here is that there is some issue with the machines
> getting a valid IP from a DHCP Server. Windows assigning a 169.xxx IP
> to a machine indicates that. I don't think that assigning a static IP
> is going to help either. The machines may be able to talk to each
> other and that's about it. This may be due to a mis-configuration
> somewhere, possibly the NIC's.
>
> Duane
Further, I would look at other startup applications like firewall or
antivirus standing in the way of making a connection. One possibility
is your modem. It frequently helps to power cycle the modem and the
router, then bring the computers up when you get only a LAN IP address.
If you continue to have problems, you can try turning off Wireless Zero
Configuration, enter the connection properties in the NIC properties
directly (or use the vendor's configuration utility). When all is well,
then turn on WZC and see if you can then invoke WEP, etc.
Q