Please help me correct this setting

Tommy B · 26 May 2006 at 10:14

I always have the problem of getting IP addresses signed to new computers on my network. It seems to work over the normal wired network OK, but any wireless computers need to be manually configured. For example, my builder wanted to use my wireless network to order some bits over the net. His laptop connected OK but the network refused to assign it an IP address.

My network consists of a ROUTER
(IP address 192.168.1.1)

but also a BT Talk (Internet Phone) service that sits between the router and my hub. For some reason, all the computers getting connected through that follow the IP address 192.168.192.x

Any ideas?

tolien · 26 May 2006 at 11:15

Sounds like the BT device is performing NAT.

Tommy B · 26 May 2006 at 11:32

Thing is the wireless devices connect to the Router and not through they BT Talk device. The router is also a BT Voyager btw. When I mnaually configure wireless devices, they will only work on 192.168.1.x.

Also, the DHCP lease IP address range starts at x.x.x.2 on both? Is this normal?

tolien · 26 May 2006 at 11:46

So the wireless devices get 192.168.1/24 IPs, but wired devices get 192.168.2/24 from the BT phone thing (sounds like an ATA crossed with a router, a la the Vonage box)?

It'll be normal if there's something taking 192.168.1.1 (the router) and 192.168.2.1 (the BT thing).

Tommy B · 26 May 2006 at 12:01

tolien said:
So the wireless devices get 192.168.1/24 IPs, but wired devices get 192.168.2/24 from the BT phone thing (sounds like an ATA crossed with a router, a la the Vonage box)?

It'll be normal if there's something taking 192.168.1.1 (the router) and 192.168.2.1 (the BT thing).

I know, but the devices connected via wireless aren't assigned an IP address.

The laptop's IP address (when left to auto mode) was something like 254.567.43.32

tolien · 26 May 2006 at 12:04

Is DHCP enabled on the router?

Tommy B · 26 May 2006 at 12:26

Yes. Starts from 192.168.1.1 (was 1.2) to 192.168.1.256

tolien · 26 May 2006 at 12:29

But the router's using 1.1?
192.168.1.256 is invalid too - should be 192.168.1.254.

Tommy B · 26 May 2006 at 12:38

tolien said:
But the router's using 1.1?
192.168.1.256 is invalid too - should be 192.168.1.254.

Ah right, so it should be 1.2

My bad, you're right, it is 254 - I was trying to remember it.

Any ideas then? I'll reset it back to 1.2 as the start.

tolien · 26 May 2006 at 12:40

Barring firewalls or some weirdness with the BT thing getting in the way (since it'll be running a DHCPd too), nothing comes to mind.

Installing something like Ethereal and looking at what's getting pushed back and forward with DHCP might be worthwhile though.

Tommy B · 26 May 2006 at 12:49

tolien said:
Barring firewalls or some weirdness with the BT thing getting in the way (since it'll be running a DHCPd too), nothing comes to mind.

Installing something like Ethereal and looking at what's getting pushed back and forward with DHCP might be worthwhile though.

How do I go about doing that. I've got the programme.