hey guys,
i have a hp g62-b31ee laptop that wont connect to any ad-hoc network
all the steps is absolutely right-as the book says :)-
the strange is it connects any non ad-hoc wireless connection and also
the wired connections works fine.
so anyone have any clues??
PS:if any one wants to know here is my laptop:
Network interface
Integrated 10/100BASE-T Ethernet LAN
Wireless technologies
802.11 b/g/n
Bluetooth® wireless networking
thanks
hatem
On 02/20/2011 05:06 PM, suseTOMA wrote:
>
> hey guys,
>
> i have a hp g62-b31ee laptop that wont connect to any ad-hoc network
> all the steps is absolutely right-as the book says :)-
>
> the strange is it connects any non ad-hoc wireless connection and also
> the wired connections works fine.
>
> so anyone have any clues??
>
> PS:if any one wants to know here is my laptop:
> Network interface
> Integrated 10/100BASE-T Ethernet LAN
> Wireless technologies
> 802.11 b/g/n
> Bluetooth® wireless networking
Not all wireless drivers support ad-hoc. As you do not say what driver yours
uses, we have no idea why it fails.
my driver is: rc3090 802.11
Any kind of Peer (Ad hoc) networking can be tricky and IMO is relatively rare compared to using an Access Point (Infrastructure) networks.
You didn’t describe your problem in detail so it’s not possible to know at what step authentication might be failing…
A starting point might be whether you’re experienced in wired (802.3) Peer Networking, commonly known as Workgroups (as opposed to Domains). Unlike Infrastructure wireless networks, getting your Workgroup authentication working is critical. Do you know how to setup Workgroup authenticaiton? Do you have a Share configured in the Workgroup (A common issue is that if you can’t connect to a resource, authentication will fail even if everything else is configured properly).
Tony
On 02/21/2011 08:36 AM, suseTOMA wrote:
>
> my driver is: rc3090 802.11
There is NO driver with this name in the kernel. If you compiled it yourself, we
cannot debug it. That is between you and the vendor.
If you gave us the name of your device, then please reply with the output of
/sbin/lspci -nnk
That is used if you have a PCI device. If USB, then the output of “lspci” is
what we need.