(LINPUS) Ad-hoc (Adhoc) connection from XP to Linpus Aspire

I'm having real problems setting up an ad-hoc connection between my XP computer and my new Aspire One. I think this may well be a generic Windows -> Linux problem with my configuration, but I haven't been able to find any useful tutorials on the internet. Hopefully someone else has a similar setup and can help me out

Setup:
Laptop: Acer Extensa 5610 (Intel 3945ABG onboard wifi), Windows XP SP2
Netbook: Acer Aspire One 8GB Linpus Linux

Procedure:

Windows:
All 'preferred networks' deleted in Wireless Network Connection Properties. Wireless adapter is idle.

Linpus:
Run terminal (right-click desktop, select 'terminal')
su
(password)
sh adhoc.sh

Contents of adhoc.sh:

Code:

/etc/rc.d/init.d/NetworkManager stop
ifconfig ath0 down
wlanconfig ath0 destroy
wlanconfig ath0 create wlandev wifi0 wlanmode ad-hoc
iwconfig ath0 channel 10
iwconfig ath0 essid "ADHOC"
ifconfig ath0 up
dhclient ath0

Output of adhoc.sh:

Code:

Stopping NetworkManager daemon:                            [  OK  ]
ath0
Internet Systems Consortium DHCP Client V3.0.6-Fedora
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit [url]http://www.isc.org/sw/dhcp/[/url]
wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:22:68:c6:4f:70
Sending on   LPF/ath0/00:22:68:c6:4f:70
Sending on   Socket/fallback

(At this point, I start scanning for networks on the Windows PC)

Output of adhoc.sh continued:

Code:

DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3
receive_packet failed on ath0: Network is down
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
Trying recorded lease 192.168.2.3
PING 192.168.2.1 (192.168.2.1) from 192.168.2.3 ath0: 56(84) bytes of data.

--- 192.168.2.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2011ms
, pipe 3
No working leases in persistent database - sleeping.

Simultaneous output of ifconfig in seperate terminal window:

Code:

[user@localhost ~]$ iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wifi0     no wireless extensions.

ath0      IEEE 802.11g  ESSID:"dlink"  Nickname:"localhost"
          Mode:Ad-Hoc  Channel:0  Cell: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power:18 dBm   Sensitivity=1/3  
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=0/94  Signal level=161/162  Noise level=161/161
          Rx invalid nwid:2  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

(Why 'dlink'? My SSID was specified as 'ADHOC'! Really wierd!)

On the Windows PC: Scanning for networks as soon as the adhoc.sh script is executed on the Aspire reveals the 'dlink' connection. Clicking 'connect' either results in endless 'Waiting for network connection' or a jump back to the wireless connections list (without connecting)

The Windows TCP/IP config is all automatic. My only experience of Ad-hoc connections was Windows -> Windows, which was fairly straightforward and all hidden under the GUI, so I've no idea what's going on. Can anybody give me any suggestions?

TIA!