Idiots Guide to Wireless networking....

[tvradict]

Back to this old issue again, since I last posted about this, my router has sat on my desk idle, not plugged into anything.

So I need to get it up and running properly, now there is my way and then there is the right way.

I have a D Link Wireless ADSL Router and a D Link Wireless PCI Card. The card is in the PC Downstairs, the Router will eventually plug into the network card on my PC and into the DSL line.

So is there someone in PHland with a spare 5 minutes who could write a step by step guide to setting this all up so it works please. I know the basics but didn't pay attention in College to the wireless bit.

Theres a beer on it if I ever get to a pH meet

TIA
Stuart

[nubbin]

My advice is - if the router has network sockets, wire the computers together! Feckin' wireless networks are nothing but trouble IMHO

[tvradict]

Well the network is running, well at least, the two PCs can talk to the router. Not each other ATM which I'm slightly concerned about.

The problem back in September was the Router wouldn't allow net access.

Networks are a pain in the arse!

[thepassenger]

tvradict said:

Well the network is running, well at least, the two PCs can talk to the router. Not each other ATM which I'm slightly concerned about. Networks are a pain in the arse!

Ok, I'm assuming that all machines concerned are pulling valid IP addresses (either statically assigned or via DHCP), on Windows (should work for nasty8 upwards) click start > run and type command (NT4, 2000, XP type cmd) and click ok.

You'll be dropped off at the command shell, now type ipconfig, you'll see something remarkably like this appear

ipconfig said:

Ethernet adapter Wireless Network Connection: Connection-specific DNS Suffix . : shadowviel.org IP Address. . . . . . . . . . . . : 192.168.1.134 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected

Do this for all machines and jot down the IP Address each one is assigned, now in the command shell type ping {IP Address or remote computer} (so ping 192.168.1.134 as an example)
If the machines are talking to each other then you'll see something like this:

goodping said:

Pinging 192.168.1.1 with 32 bytes of data: Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

or this if they aren't.

badping said:

Pinging 192.168.0.1 with 32 bytes of data: Request timed out.

If your getting a ping response (and if you have no firewalls running you should) then your a-ok.
Now to get Windows to talk to each other, two or three ways to do this really (note from here on in this is XP Pro stuff, it kind of works in 2k as well but I don't have it to hand).

The simplest way, but hardly the most secure is to turn on the guest account on. Windows XP has another trick up its sleave that you'll need to work around. It will not (or at least gets cranky) when someone with a blank password tries to access a share over the network.
Open up Control Panel, then Administrative Tools, open Local Security Policy and then Local Policies and finally Security Options.
In here make sure that
"Accounts: Guest Account status" is enabled.
"Accounts: Limit localaccount use of blank passwords to console logon only" is disabled.

I think there is one more... not too sure. If that little lot works then your laughing temporarily.

[tvradict]

Thanks for the reply.

Both Machines have Valid IP's, Mine is on 192.168.1.2, The other is 192.168.1.3, Router is on 192.168.1.1.

I did the ipconfig and got this

Ethernet adapter Local Area Connection

Connection-Specific DNS Suffix :
IP Address : 192.168.1.2
Subnet Mask : 255.255.255.0
Default Gateway : 192.168.1.1

PPP adapter Pipex

Connection-Specific DNS Suffix :
IP Address : 81.86.82.70
Subnet Mask : 255.255.255.255
Default Gateway : 81.86.82.70

I then pinged the computer downstairs and realised mine is bloody firewalled. Turned off the firewall, works now

I don't want to turn off the Firewall completely while on the net, so I'll do the last bit later on. But thanks for your help.

The one remaining problem is why the Router wont allow internet access to either PC.

I ran some tests using the router software and got 2 failures so I need to find out what they are, I'm getting some info from the Pipex site, so hopefully, fingers crossed an all that, I might get it working.

Cheers