Help! How do I add this Wireless AP to my desktop?

chortle

Standard Member
This is my setup

pcwlanquestion.png

By blacksnakeuploads at 2011-12-03

I get broadband from a box that plugs into a LAN card (call it LAN1) on my desktop. I added a wireless access point (not a router, just a box with a single ethernet port and a separate power supply) and connected it to LAN2.

I can connect to the wireless AP from the PC via ethernet (just http://192.168.1.253 to get there from a browser). The wireless AP accepts connections, checks the password, but sticks on trying to obtain an IP address.

So I'm doing something wrong or need something else. Anyone know how I can get this working?
 
What is LAN2 and what is this box that you get your internet from ? Is it locked to mac address maybe ? (your not a student by anychance are you, in halls of residence ?)
 

chortle

Standard Member
LAN1 and LAN2 are ethernet cards inside the desktop PC. Actually, LAN1 is built in. I don't think I get to the stage of connecting my android tablet to the internet as it chokes on getting an internet address, which should be assigned by the PC.

The internet box is a fiber optic connection. It snakes its way into the building and terminates in a small box, with flashing lights, and a single ethernet port. I string an ethernet cable between this box and LAN1. This has always worked. I'm connecting through this now.

I am in Bangladesh. I am trying to bring my house into the 21st century by allowing my mobile devices to connect to the net, and to play material from my desktop hard drive.
 

chortle

Standard Member
I used a different tablet, which allowed a static ip address to be set. I made the address of the tablet 192.168.1.3, so it is on the same net as the wireless AP and the ethernet card, on the PC, that leads to the AP. Got as far as connected. So half way there.

Do I need a proxy server or a router now? Any s/w which you use that works?
 

mickevh

Distinguished Member
It still won't work. As Mr Beerhunter advocates, you need to turn your PC into a "router" (preferably c/w DHCP Server and NAT translator.)

Have a Google about Windows "Internet Connection Sharing" (ICS) or whatever it's called in Windows 7. IIRC that does everything you need and is built in to Windows.
 
Last edited:

chortle

Standard Member
Internet Connection Sharing (ICS) changes the IP address of the *other* LAN card (not the shared one, which has internet) to 192.168.137.1.

I shared the connection before I posted here, hoping it would do the trick. I logged onto the Wireless Access point and changed it's IP address to 192.168.137.66 so that it was on the same network as the PC Lan card it was connected to.

Again I got the problem of my tablet trying to obtain an IP address, but never getting one. So I set the static IP address to 192.168.137.12 so it was on the same network again. This wasn't enough. I had to set the gateway to the IP of the LAN card 192.168.137.1. Now I get a connection to the AP, but internet doesn't work through it.

If I set the gateway for the android tablet to 122.x.y.z (my true internet address and gateway to the world) I don't even connect to the AP.

Windows leaves the gateway of the second LAN card (192.168.137.1) blank. I tried changing it to 122.x.y.z but that didn't make a difference.
I'm still missing something. I'm sure it is simple!!
 

mickevh

Distinguished Member
All good so far: Windows has create your internal subnet as 192.168.137.X and bound internal NIC 192.168.137.1 to it.

192.168.137.1 doesn't need (shouldn't have) a default gateway assigned, so leave it blank.

The default gateway of your Wi-Fi AP should be 192.168.137.1. Though in "normal" operation Wi-Fi AP's don't use IP - it's only there for use to access their configurations screens.

Personally I'd set the IP Address of your AP to 192.168.137.253 Netmask 255.255.255.0 dflt GW 192.168.137.1 as it's unlikely the DHCP Server ICS creates inside your PC will ever get as far along the IP range as to allocate that IP address in a SOHO LAN. (There is a way you can prevent it, but it involves a bit of registry hacking which gives a lot of people the willies.)

Sounds like you're still missing a DHCP Server. I thought ICS built one for you, but I'll have to do a bit of digging to check. There is some suggestion that the ICS DHCP Server doesn't play nice with non-Microsoft boxes, though I'm at a loss for why not. DHCP is a pretty simple process.

In the mean time, open up a CMD prompt (Start, run, CMD) on you ICS PC and type "IPCONFIG /ALL" and "ROUTE PRINT" and copy paste the results.

If you want to statically assign IP addresses on client devices, then set

IP 192.168.137.X (where X is unique on your internal LAN)
Mask 255.255.255.0
G/W 192.168.137.1
DNS 192.168.137.1

Strictly speaking you should choose "X" outside the DHCP range your ICS PC will provide, but if you choose a sufficiently high number (say 200) I think it'll be a long time before DHCP gets around to using it, but bear it in mind for the future. But as I said, DHCP should really be sorting all this out for you.
 
Last edited:

chortle

Standard Member
Thanks for looking. Here are the results. Could it be that I need to use a proxy because, perhaps, my ISP blocks all mac addresses but my main PC?

Windows IP Configuration

Host Name . . . . . . . . . . . . : Home
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ether
NIC
Physical Address. . . . . . . . . : 00-00-1C-D9-15-9A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.137.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 122.152.52.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8102E/RTL8103E Family PCI-E
st Ethernet NIC (NDIS 6.20)
Physical Address. . . . . . . . . : 00-24-1D-3E-E9-C8
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 122.152.52.49(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.192
Default Gateway . . . . . . . . . : 122.152.52.1
DNS Servers . . . . . . . . . . . : 122.152.52.2
4.2.2.2
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{8CB8EAC4-6518-4154-86CA-D7F5E9FA3AEB}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter 6TO4 Adapter:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{59F0A447-1E85-4DA1-A90E-B74CA2743369}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Reusable Microsoft 6To4 Adapter:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 13:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\neil>route print
===========================================================================
Interface List
16...00 00 1c d9 15 9a ......Realtek RTL8139/810x Family Fast Ethernet NIC
11...00 24 1d 3e e9 c8 ......Realtek RTL8102E/RTL8103E Family PCI-E Fast Eth
et NIC (NDIS 6.20)
1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
17...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter
15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
18...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #2
19...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #3
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 122.152.52.1 122.152.52.49 21
0.0.0.0 0.0.0.0 122.152.52.1 192.168.137.1 286
122.152.52.0 255.255.255.192 On-link 122.152.52.49 276
122.152.52.49 255.255.255.255 On-link 122.152.52.49 276
122.152.52.63 255.255.255.255 On-link 122.152.52.49 276
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.137.0 255.255.255.0 On-link 192.168.137.1 286
192.168.137.1 255.255.255.255 On-link 192.168.137.1 286
192.168.137.255 255.255.255.255 On-link 192.168.137.1 286
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 122.152.52.49 276
224.0.0.0 240.0.0.0 On-link 192.168.137.1 286
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 122.152.52.49 276
255.255.255.255 255.255.255.255 On-link 192.168.137.1 286
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 122.152.52.1 1
0.0.0.0 0.0.0.0 122.152.52.1 Default
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
1 306 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
 

mickevh

Distinguished Member
MAC addresses are irrelavent as you're trying to create a routing, NAT translating device and all the frames egressing your PC towards the ISP will be using the MAC of "Ethernet adapter Local Area Connection."

MAC addressing will only be an issues if you "bridge" your two NIC's together (turn the PC into an ethernet switch) instead of using ICS (turn the PC into a router.)


I can see these problems at the moment:

This...

IP Routing Enabled. . . . . . . . : No

...is telling us that ICS isn't doing it's thing properly. Try un ICS'ing and re-ICS'ing your Internet connected NIC.

Since ICS isn't working properly, it may also explain why it's not issuing DHCP leases.


On "Ethernet adapter Local Area Connection 3:"

you have....

Default Gateway . . . . . . . . . : 122.152.52.1

...which is wrong. It doesn't need a default gateway at all, so remove it. The routing metrics are such that it'll probably never use that g/w, but best to be tidy.

On "Ethernet adapter Local Area Connection:" I see that DHCP is disabled. Presumably the settings used on that interface were supplied by your ISP...?


Of course, you could always forego all this hassle and buy yourself a SOHO router to do the job (or contact your ISP and see what they recommned.) Then you wouldn't need you PC turner on to use the Internet. However, since you have all the kit you need, that would be extra money. To get what you have working you just need to persuade ICS to work properly.
 
Last edited:

neilball

Well-known Member
As the last post confirms, it would be easier to get a wifi router. This would allow you to plug your internet modem directly into the WAN port of the new router using the ethernet cable that currently connects the the first LAN card of your PC. You then connect your PC to one of the LAN ports using a second ethernet cable. Other deivces could then either connect hardwired the other LAN ports on the router (they usually have 4 LAN ports as standard) or by wifi once configured.

The advantage of this is that you do not need the PC to be switched on to get internet access on your other deivces and also means you don't have to spend lots of time trying to get internet sharing working via your PC.
 

chortle

Standard Member
Thanks, Mick. I tried

1. turning ICS off, then on again. Disabling both ethernet adapters and then enabling them, and then turning ICS off and on again. ipconfig again showed routing was not enabled. Wierd!

2. Default Gateway . . . . . . . . . : 122.152.52.1 - I removed this before I tested 1.

DHCP disabled - don't know where that came from. I can't find a spot to turn it on.

Neil - I would buy a wireless router but you can't get them where I live in Bangladesh. The wireless AP, which I have, came from a trip to the Philippines.

BTW, I changed my setup a bit since I checked all the above. I actually have an 8 port ethernet hub (not wireless). The wireless AP now connects to the hub, not the PC, and the PC connects to the hub. I can connect to the AP by ethernet through the hub no problem. So I don't think it impacts anything.
 

The latest video from AVForums

Podcast: Large Screen HDR TV or Projector For Home Cinema + Best of the Month
Support AVForums with Patreon

Top Bottom