WindowsXp Home & WindowsXP (Pro)

[Sash]

[Systems Specs]

Pc = Laptop
HardDrive = 6GB
GFX = Trident40 meg of ram
Cdrom Drive =24x
Wireless card = U.S. Robotics 22 Mbps Wireless Pc Card
Mouse = Ms Intelie Explorer
Floppy Drive = 1.44mb

[System Numder 2 Specs]

Pc = Desktop Pc
Harddrive = 80GB
GFX NivdiaTNT Gefore2
CPU = 966Mhz
Cdrom =Rewriteable
Cdrom =24x
Floppy Drive = 1.44mb
Wireless = Us Robotics 22 Mbps Wireless Pci card

[Problem]

I am using ad-hoc mode with both pcs and both of them are on the same channel have the sam sidname. No wep enabled, setup windowsxp pro to use msnhome /not/ business. Not using windows either of them to use the wireless networking because it has its own software which is meant to be better, have tried allowing windows to use its own software but still no good. The Laptop which has windowsHome gets single from the other pc but can not connect to it in networking. THere are files shared!, The desktop pc which has Xppro dose not see any single at all.

Updated and downloaded upto date drivers but still out of luck!

Any help would be appreciated. Thanks.

[TripleRLtd]

Sash: sorry to say, but I am confus-ed!
What, exactly is the problem? Can't connect to the internet? Using a wireless AP? OK, now give us better details on the make of AP/Router and any error messages you might be receiving. Signal stats? Etc?

[Mayet]

The issue was stated

The Laptop which has windowsHome gets single from the other pc but can not connect to it in networking. THere are files shared!, The desktop pc which has Xppro dose not see any single at all.

[TripleRLtd]

The issue was stated

Alright, since you seem to understand what single means, what do you recommend?
Ah, signal...is that it??? My gosh, there's that aura again.
OK, so what next May?

[Matridom]

Make sure that the SSID on both systems are the same.. Rememeber CaSE DOes mattER. If you have an encryption key, make sure it matches on both sides.

For Ad-Hoc, i would recommend that you put in static IP addresses so that you know that different range is not the issue. Once these are done, your going to want to try to ping from one system to the other, Get that going before you even look at shares.

[NooNoo]

also start, run, ipconfig /all

If the ip address starts 169.x.x.x the tcp stack has got its knickers in a twist.