Since you already have a wireless router, just plug the ethernet cable into the router. Why go computer to computer?
Since you already have a wireless router, just plug the ethernet cable into the router. Why go computer to computer?
Are you trying to go wireless with the second PC without the use of an adapter card in it? Thinking you can connect to the WRT54G through the first PC.
BILL P.
If the second computer is near the WRT54G, then plug it in directly. I'm guessing it is not.
You do NOT need to use ICS for this. Much too complicated.
Just bring up network properties. Select both the Wired and Wireless connections and right click.
Choose Bridge connections.
Plug a crossover cable between the two machines.
That's it.
Tom
At home I have a wireless network, the basis of which is a Linksys WRT54G router. I then have my PC (running Windows XP) with a wireless PCI card accessing the router. The PC also has an unused wired 10/100 Ethernet port. Is there any easy way to set things up so that the Ethernet port on my PC can be used by another wired computer for acessing the wireless router (and the rest of the network)? I assume I would link the computers via a crossover cable, but then what?
Thx
"Joe Jax" wrote in news:p3yLd.6330$ snipped-for-privacy@fe2.columbus.rr.com:
That's what a NAT router does that you have wired or wireless.
Of course, you'll have to configure the O/S on each machine to share resources on the LAN.
Yes. internet-local_net-Wireless-PC_one-"ICS"-wired-PC_two. On the "properties" page of PC_one's wireless card, go to the Advanced tab. check "Allow other network"...
PC_two is going to get a DHCP address of 192.168.0.something. For going to the internet you'll be fine as long as your local network isn't already
192.168.0.something. You have no control over the ICS address.Other PCs on the local_net will see accesses coming from PC_one and PC_two as coming from the same IP address, that of PC_one. You might be able to share files if you open the window from PC_two, but not from other PCs toward PC_two.
That would likely be much better in this case, if there are other computers on the existing network. Is bridging going to allow a flat network across the wired-wireless PC, so that all the addresses are in the same subnet?
Uh-oh. You can't run WinXP firewall on either one of the interfaces in the bridging PC. I always want to run Firewall on any PC on a wireless LAN.
You can run a firewall, including the SP2 firewall, on the wireless connection. The second machine sits 'behind' it, so it is OK.
The second machine can be any OS, even Win95. It doesn't know any different. Only the bridge machine has to be XP. It IS possible to do this in 2000, although more complicated, and it has been too long for me to remember the steps.
Tom
You Sir, are a genius! Thanks... and thanks to all the other responders.
That was introduced with WinXP, and isn't available for Win2000 or earlier, it would appear. If you are all WinXP, then the only remaining problem is the statement that you can't run a firewall on the interfaces involved.
After you get it working, I think you should try adding the WinXP firewall. It might require some setup, depending on what you want going through it, but I don't like a wireless PC running with no firewall.
I was thinking of setting this up at work, between my desktop and laptop, but I don't like running wihtout a firewall at work. Too many snooping systems, all, I'm sure, part of our proactive IT group checking for unpatched systems, but the probes certainly look malicious.
I was running ICS between the Win2000 laptop and WinXP desktop. Now my laptop is WinXP, so I could do the bridge, but I want the firewall.
If WinXP firewall doesn't work, try ZoneAlarm. Any PC on the wired or wireless network in a wireless subnet should have a software firewall, because any wireless intruder is on your side of the router firewall. You should also elect trusted servers very carefully in the configuration, and not allow the entire subnet, which is the default for WinXP firewall.
Ah, SP2 is better:
Some other online instructions hadn't been updated for SP2.
That was really bad pizza on my network at work. Using a small switch, or using ICS, my network port only sees one MAC in my office. Using a Bridge connection, I suspect that the Cisco Router could see both the desktop and the laptop MACs. It didn't like that at all, and shut down my port.
Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.