Help! Lost Network!

Hi,
I've been running an ad-hoc network between a Dlink pci card and a Dlink PC
card for months now, with no major problems--most of the time I could get
the network running when I needed it (usually by resetting the laptop's
card).

But I've just changed DSL modem and now all of a sudden I can't get the
network going again. The computers just don't see each other...the laptop
keeps getting a 169.xx etc address...

So, what might have gone wrong? Where are places to look to fix/reset this?

I don't use Dlink's configuration software--that was incompatible with the
system, I've always used the zero config utility. I remember having this
problem when I first got the network up, took a couple of days to resolve
it, but finally got it going--but I can't remember what I did.

Thanks for any help!

"SuperX" <(E-Mail Removed)> wrote in message
news:bjh3pa$st0$(E-Mail Removed)
>
> But I've just changed DSL modem and now all of a sudden I can't get
> the network going again. The computers just don't see each
> other...the laptop keeps getting a 169.xx etc address...

Do both PCs require access to the Internet? How do you have the systems
configured to do so? ICS?

Windows XP will assign a 169.x address when it can't find a DHCP server.
Both cards should use IP addresses in the same range (for example:
192.168.0.x). Try configuring both wireless cards to use a fixed IP address
where the first three numbers are the same. A good example is:

PC1 = 192.168.0.1
PC2 = 192.168.0.2

You may need to use PC1 as the Internet gateway if you don't use a router
(infrastructure mode).

--
John T
http://tknowlogy.com/tknoFlyer
__________

Took a good while, but I got my lil' network fixed...along the way,
including several system restores (to just before the last Windows update I
did), as well as trying to figure out why Windows 'lost' the wireless zero
configuration service (had to monkey with the registry for that)

> 192.168.0.x). Try configuring both wireless cards to use a fixed IP
address
> where the first three numbers are the same. A good example is:
>
> PC1 = 192.168.0.1
> PC2 = 192.168.0.2

> You may need to use PC1 as the Internet gateway if you don't use a router
> (infrastructure mode).

Indeed, it's an ad-hoc network. And I discovered some more interesting
tidbits--in order for the client to have access to the internet, it must be
set to receive its IP address automatically!

Not only that, but when Windows does the IP assigning for the host, it will
always give it 192.168.0.1 ...

So with that address in place (manually) on the host pc and the automatic IP
set on the client laptop, all is working smoothly again...whew!

well, until the next time...