Can't talk to Belkin AP??

Hi all, please be gentle i'm a total virgin to wireless until today...

Recently got a 54g capable lappy and wanted to let it talk to my 2 wired
desktops- bought a Belkin F5D7130 (54g).

Instructions say to fire up web browser and point to 192.168.2.1 to reach
the set up page.

Doing this however makes either desktop want to use the dial -up modem.
Allowing this to happen, or selecting "never dial a connection" just results
in a page not found.

I can't ping the AP in an MS dos window fine, so wot am i doing wrong?! Do i
need a cross over cable, or should i be linking to the uplink port on the
switch or wot??

TIA

Tim..

Tim (Remove NOSPAM. wrote:
> Hi all, please be gentle i'm a total virgin to wireless until today...
>
> Recently got a 54g capable lappy and wanted to let it talk to my 2 wired
> desktops- bought a Belkin F5D7130 (54g).
>
> Instructions say to fire up web browser and point to 192.168.2.1 to reach
> the set up page.

Wire one of your PC's to the access point.

Give the PC an address on the same subnet as the access point.

192.168.2.10 should do, subnet 255.255.255.0.

Connect to the AP at http://192.168.2.1.

Change the AP IP settings so they match that of your existing network.

ie, if you current IP's are 192.168.0.x, give your AP an address like
192.168.0.123, subnet mask 255.255.255.0. Change your PC settings back
and set the gateway address on the PC's to the AP's address.

HTH

"NoSpam" <(E-Mail Removed)> wrote in message
news:416c49d6$0$22869$(E-Mail Removed)...
> Tim (Remove NOSPAM. wrote:
> > Hi all, please be gentle i'm a total virgin to wireless until today...
> >
> > Recently got a 54g capable lappy and wanted to let it talk to my 2 wired
> > desktops- bought a Belkin F5D7130 (54g).
> >
> > Instructions say to fire up web browser and point to 192.168.2.1 to
reach
> > the set up page.
>
> Wire one of your PC's to the access point.
>
> Give the PC an address on the same subnet as the access point.
>
> 192.168.2.10 should do, subnet 255.255.255.0.
>
> Connect to the AP at http://192.168.2.1.
>
> Change the AP IP settings so they match that of your existing network.
>
> ie, if you current IP's are 192.168.0.x, give your AP an address like
> 192.168.0.123, subnet mask 255.255.255.0. Change your PC settings back
> and set the gateway address on the PC's to the AP's address.

Many thanks, i'll give that a try and see wot happens.

two questions:

1) Do i need a str8 thro or x-over cable to link the AP direct to a PC?

2) Why does the PC insist on trying to dial a connection to the net when
asking it to display http://192.168.2.1 ??

Tim..

>
> Many thanks, i'll give that a try and see wot happens.
>
> two questions:
>
> 1) Do i need a str8 thro or x-over cable to link the AP direct to a PC?
>
> 2) Why does the PC insist on trying to dial a connection to the net when
> asking it to display http://192.168.2.1 ??
>
> Tim..
>
>

You try connect via wire or wireless ?

If you try via wire you need Cross Over Cable, set at network card your
IP: 192.168.0.2 netmask: 255.255.255.0 and try to connect to AP.


If you try use wireless, set mode to Access Point - AD-HOC ( not
Point-To-Point ), find channel, set IP and netmask and try to connect.

best regards
Marcin

Tim (Remove NOSPAM. wrote:
>
> Many thanks, i'll give that a try and see wot happens.
>
> two questions:
>
> 1) Do i need a str8 thro or x-over cable to link the AP direct to a PC?

With most it won't matter, it'll auto-detect the cable and act as
appropriate.

If you have any problems, a straight through should be used.

X-over is only necessary if you're linking two NIC's directly to each other.

> 2) Why does the PC insist on trying to dial a connection to the net when
> asking it to display http://192.168.2.1 ??

It'll be a range outside your current subnet, so it thinks it has to
connect to an external network to make the connection. If for example
your current IP is in the range 192.168.0.x, and you have a subnet mask
of 255.255.255.0, you're effectively saying your LAN is
192.168.0.0-192.168.0.255. Windows will try and dial out for any other
address you enter.

Hope this gets you on the right track!

"NoSpam" <(E-Mail Removed)> wrote in message
news:416d1dad$0$22871$(E-Mail Removed)...
> Tim (Remove NOSPAM. wrote:
> >
> > Many thanks, i'll give that a try and see wot happens.
> >
> > two questions:
> >
> > 1) Do i need a str8 thro or x-over cable to link the AP direct to a PC?
>
> With most it won't matter, it'll auto-detect the cable and act as
> appropriate.
>
> If you have any problems, a straight through should be used.
>
> X-over is only necessary if you're linking two NIC's directly to each
other.
>
> > 2) Why does the PC insist on trying to dial a connection to the net when
> > asking it to display http://192.168.2.1 ??
>
> It'll be a range outside your current subnet, so it thinks it has to
> connect to an external network to make the connection. If for example
> your current IP is in the range 192.168.0.x, and you have a subnet mask
> of 255.255.255.0, you're effectively saying your LAN is
> 192.168.0.0-192.168.0.255. Windows will try and dial out for any other
> address you enter.
>
> Hope this gets you on the right track!

Hmmmmmmm. Me tink I need "networking for extreme dummies"!!

Tim..

" Tim (Remove NOSPAM." <(E-Mail Removed)> wrote in message
news:ckjmco$1lf$(E-Mail Removed)...

Ok guys, well the AP is now working, I can communicate via the wireless to
the wired network and all the other PC's are connectable just fine

However!

I still cannot communicate with the AP itself. Pinging 192.168.2.1 in a DOS
window results in nothing- all packets lost.

Subnet is set to 255.255.255.0 on all machines, as is the gateway of
192.168.2.1, and this works.

What am i doing wrong?

Tim..

is ICMP disabled on the AP - as ICMP is used for PINGing a device..


On Thu, 14 Oct 2004 12:38:36 +0000 (UTC), " Tim \(Remove NOSPAM."
<(E-Mail Removed)> wrote:

>
>" Tim (Remove NOSPAM." <(E-Mail Removed)> wrote in message
>news:ckjmco$1lf$(E-Mail Removed)...
>
>Ok guys, well the AP is now working, I can communicate via the wireless to
>the wired network and all the other PC's are connectable just fine
>
>However!
>
>I still cannot communicate with the AP itself. Pinging 192.168.2.1 in a DOS
>window results in nothing- all packets lost.
>
>Subnet is set to 255.255.255.0 on all machines, as is the gateway of
>192.168.2.1, and this works.
>
>What am i doing wrong?
>
>Tim..
>

"None" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> is ICMP disabled on the AP - as ICMP is used for PINGing a device..
>
>
Don't know!!

I've given up wanting to commmunicate with the AP, as it is now working "out
of the box" just fine, so i'll leave well alone!

tim.

" Tim (Remove NOSPAM." <(E-Mail Removed)> wrote in message
news:claskr$ejr$(E-Mail Removed)...
>
> "None" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> is ICMP disabled on the AP - as ICMP is used for PINGing a device..
>>
>>
> Don't know!!
>
> I've given up wanting to commmunicate with the AP, as it is now working
> "out
> of the box" just fine, so i'll leave well alone!
>
> tim.
>
>
I don't think the Belkin WAP responds to an ICMP ping. Just try
http://192.168.2.1 and you should get configuration page. With no
configuration anybody could connect to your network, at best using your
bandwidth to surf the net at worst using your setup for malicious purposes
and/or hacking your personal files and/or destroying your hard drives. Take
the time to set up at least a WEP key and set to allow only the MAC
addresses on your wireless devices.


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.778 / Virus Database: 525 - Release Date: 15/10/2004