PDA

View Full Version : Small networking problem


Steadders
16th October 2004, 12:56
OK, I'm going to try and describe my "problem" the best i can.

My usual set up is a wireless adsl router, which my laptop is connected to via a wireless pcmcia card. This is stright forword enough, i can access the broadband, and when anyone else is wired into the router im conneceted to them.

Now what i want to do is to connect 2 other computers to my laptop using a hub i've got. So, i want to these 2 new computers have internet access as well from the laptop (using the laptops built in network card). however, i haven't been lucky so far. I can get my laptop networked to the other 2 computers in my room like a normal network would work, but they dont have internet access even though this laptop does.

What am i doing wrong? / What do i need to do

(or does this make no sence...)

Elbonio
16th October 2004, 12:59
im assuming you're running the network setup wizard

Steadders
16th October 2004, 13:01
yea, Ive tried a few different combinations of it, basicly just using commen sence (what i asumed would work with no problem)

but i dont have a great amount of experience with networks :rolleyes:

Elbonio
16th October 2004, 13:04
ok im assuming you've no idea what you're doing (even though you might have some idea) and i'll go from the ground up what needs to be doing what

Laptop has wireless and normal 10/100 network card.

Broadband should be running through the wireless connection, leaving the LAN connection for the normal net adapter. This should be set to connect directly to the internet.

On your other machines they should be "connecting to the internet through another computer or a gateway". This needs to be going through their network cards.

This *should* work.

Restart all machines and test.


report back.

m00
16th October 2004, 13:28
Basically, you need internet connection sharing running on the wireless adapter of your laptop. Once that's set up, all the other machines should 'just work'.

KingDaveRa
16th October 2004, 14:40
Can you NAT NAT?

I don't think you can.

If your PC is running as a NAT gateway, as well as the router, then its just not going to work.

m00
16th October 2004, 14:58
I don't see why not... Anyway, an alternative is to bridge the wired and wireless connections by selecting both of them and then right clicking and going bridge. This will effectively connect the wired and wireless networks together.

Buffy
16th October 2004, 15:27
all that needs doing to share the connection is to bridge the connecitons, after this run ipconfig/renew to get your self an IP address and it all good.

Steadders
16th October 2004, 16:20
Thank you very much for the help, and it all sounds good. It should also work, BUT IT DOESNT!

gah, you know when you get these problems that just never seem to work no matter what.

I've tried everything, and then some.

for a start you cant bridge a connection if it ahs an internet connection to it (dont ask me why, its just the error message i got)

Also, i would have just turned on the internet sharing on my main computers to let the others "just work" but they dont, because my router was taking 168.192.0.1 - that in itself wasnt a problem, i simply changed the my routers ip.

i thought i was in luck now, but still no joy. i went to my wireless connection to enable internet sharing and the option had disapeared.

http://img94.exs.cx/img94/1482/error3.jpg

I've had enough for one day, so im giving it a break, if anyone has any more ideas i would very much apriechate it!

GeeDee
16th October 2004, 16:29
Sorry, whats the problem exactly here? Why are you trying to use ICS when you've got a router?

Nivek
16th October 2004, 17:34
run a third party proxy like wingate on the laptop, one side points to the router the other to the other computers

jase
16th October 2004, 17:49
Does the router not have a RJ45 socket?

Connect your Hub to that.

Then the new machines to Hub.

Run DHCP from the router

Ip auto configure on all the machines.

Ipconfig /release/renew on all the machines.

Bobs your uncle.

KingDaveRa
16th October 2004, 19:54
To enable ICS the PC will force itself to 192.168.0.1 as a static IP, so it'd just get messy.

I'd do what Jase suggests. Or, go get a wireless bridge.

Steadders
16th October 2004, 23:17
Originally posted by GeeDee
Sorry, whats the problem exactly here? Why are you trying to use ICS when you've got a router?

i dont want wires going from downstairs to my room, the idea is i'm getting the internet connection via the wireless card, and then the 2 other computers get internet off this laptop.

RTO
17th October 2004, 00:41
Originally posted by KingDaveRa
Can you NAT NAT?


Yep you can :)

Er00
17th October 2004, 08:12
I hate these kinda problems, all I have to say is good luck! I had a problem like this with my wireless and ended up just cabling it all because it was just too much hassle to keep playing round with it month after month to try and get it working. The most annoying thing was, it claimed it was connected, yet clearly wasn;t :S

KingDaveRa
17th October 2004, 10:30
Originally posted by RTO
Yep you can :)

Didn't think you could. There must be a limit to how far you can go though?

I'd still go with the wireless bridge personally. Its by far the simplest and probably most reliable solution.

m00
17th October 2004, 10:39
I don't see why Dave, I mean, NAT is lying to everything so how should any other NAT know there's another NAT, and then why would it care and decide it doesn't want to NAT any more? :p:

RTO
17th October 2004, 12:08
The problem would come when you run out of ports on the NAT router/box...

KingDaveRa
17th October 2004, 14:30
Originally posted by m00
I don't see why Dave, I mean, NAT is lying to everything so how should any other NAT know there's another NAT, and then why would it care and decide it doesn't want to NAT any more? :p:

There was no reasoning for me not knowing tbh! I'd never tried, I just assumed it wouldn't do it.

I thought once a packet was mangled it was mangled for good, and you couldn't do it again, but if the NAT device is mangling both ways, it should be able to find a way back.

PS, some light reading from Cisco:

http://www.cisco.com/warp/public/556/nat-cisco.shtml