2 pcs - wireless internet plus cable lan

By rcd ·
I have 2 pcs each with a lan card and a wireless card and a wireless adsl modem.
Currently all my connections are wireless and work ok, but pc to pc data transfer is slow. I tried connecting the pcs with a cross over cable which gave me the cable lan connection I wanted but removed my internet connections, I think because each pc tries to get to the internet via the cable connections. Can someone tell me how to get the wireless internet plus cable lan to work sensibly ? Do I need to fiddle the IP submasks or can I specify a direct internet route from the shell ?

I have solved this problem myself with a little reading and experimentation, it was the ip addr not the submasks that I needed to change.

I gave the lan cards ip addresses that did not lead to the default gateway. This stops the ip router looking at these connections when it is try to resolve network addresses.
Specifically the default gateway is (the usual one) so I gave the cards static addresses beginning with 193. Both machines can ping each other and are accessible via windows networking.

!!! If anyone knows any reason why 193... shouldn't be used, or a simpler way of doing this please let me know.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

some thoughts....

by ---TK--- In reply to 2 pcs - wireless internet ...

First what OS are you running?

Wireless data transfers are never what they say they are... Example... Wireless g says it can transfer data up to 45 Megs per sec... yes it can on paper... If your transfer speed is around 3 to 4 Mbps your doing good, the bottle neck is the encryption. The stronger the encryption the lower your data transfer speed will be.

If you want the cable connection to work... Depending on your OS it might be a little different... If your WLAN is 192.168.0.x, I would recommend setting your Nic on PC1 to static,, subnet No gateway is needed, or DNS. On PC2 set the NIC to, subnet, no gateway, no DNS.

From PC1 to access PC2, go to run command type \\\ and you can then view the shares and transfer your data... From PC2 to PC1 > run command > type \\\ and view the shares...ect...

That should work... Best of luck!

Collapse -

Disable DHCP on wired

by cpubymike In reply to 2 pcs - wireless internet ...

Give them what ever addresses you feel like that are on the same network,

You could also use
1394a or b

that is if you have cables long enough.

also put the two machines in each others hosts file. Might help especially if they are not on the same net as your DNS

Collapse -

Thanks to ---TK--- and cpubymike

by rcd In reply to 2 pcs - wireless internet ...

I have used your suggestions and things are working really well.
Using the addresses has made the whole thing much 'cleaner' looking than my 193... addrs, it now obvious that someone has been in and done a manually setup.
I have tested the lan with some big files and it runs at about 8.9 MBytes/sec which is the best I have ever had over a 100mbps connection.
Thanks very much for the help.

Collapse -

no problem :)

by ---TK--- In reply to Thanks to ---TK--- and ...

8.9 MB/s is pretty good. The major bottle neck is now probably your HDD's and bus speeds, which there isn't much you can do about that, unless you upgrade your Motherboard and HDD's... but even then you only going to gain a little...

If you have a desktop, and you want to test the bottle neck of your HDD, add a second HDD, and transfer a large file between the HDD's. Example: I have two SATAII's, transfer a large file, I really only see about 30-35 Mb/s... eventhough SATAII says its 3Gb/s... Just something to think about :)

Collapse -

You're welcome

by cpubymike In reply to Thanks to ---TK--- and ...

8.9 is probably the best you will get most likely the 1.1 that is overhead

Don't underestimate your hosts file it is a very powerful tool most people overlook you can use it to block stuff that cannot be blocked on protocol or what not

you put the banned Ip in the hosts file and point it back to the local host address and the Node never goes out to the network looking for the information.

You could also point it to a webpage hosted by IIS or Apache and you could have the page say big brother is watching excetera.

Related Discussions

Related Forums