My PC has Wifi antennas on it and I'm able to remove one of them and to connect the Yagi WiFi antenna to it so that I can access WiFi signals at some distance.

I've found a University in the area from which I can obtain WiFi signal. This WiFi works on my Intense PC just fine.

What I want to do now is to run a CAT5 cable from the Intense PC's LAN port to the WRT54g, another CAT5 cable from my WRT54g to my Apple Mini MAC and then also have the WRT54g broadcast WiFi locally here in our apartment so that all my other devices can access the Internet via WiFi.

Note that none of my other wireless devices can use the University's signal because, without the Yagi, it is too weak.

And this is where I'm hung up. I cannot get the PC's Internet shared out via the PC's LAN port.

I've read about Bridges and ICS sharing.

I've read that creating a bridge on my PC between the WiFi and the LAN port is not a wise idea as it will make everything on my local LAN visible to folks out on the Internet. So, I've avoided that.

I'm thinking that ICS should do what I want but I can't get it to work. I'm not sure if my problem is with the ICS setup or with how I'm trying to use, or misuse, the WRT54g.

What I'm expecting the WRT54g to do is to share whatever comes in on the LAN port from the PC out onto its other three LAN ports and also out over the WiFi it is broadcasting.

To setup ICS, I go to the the PC's network connections, select the WiFi connection and go to the sharing tab and click on "Allow other network users to connect through this computer's Internet connection".

Then it tells me that ICS will make the IP address of the LAN port be 192.168.0.1. That's not a problem as I'd already set it manually to be 192.168.0.1.

Now, in the network connections, when I look at the WiFi connection, I see it is shared, it is a public network and it has Internet access. It's getting its IP and DNS stuff via DHCP.

When I look at the LAN connection, I see it is described as an unidentified network, has no Internet access and is described as a public network. It has an IP address of 192.168.0.1, mask of 255.255.255.0 and no gateway information (I read the gateway is suppose to be left blank). I've also entered in two DNS IP addresses that I know are valid.

The WRT54g is manually set to IP = 192.168.0.2 and the Mini MAC is IP = 192.168.0.3. I'm intending that the other devices will get their IPs from the WRT54g's DHCP.

My wireless devices (iPhone, iPad, etc.) are all finding the WRT54g OK. From the Mini MAC, I can ping the WRT54g and any of the wireless devices linked to the WRT54g.

But I cannot ping the PC @ 192.168.0.1 from the Mini MAC. Nor is Internet being shared to the Mini MAC nor any of the wireless devices linked to the WRT54g.

Not a bad idea, Tamas, but I'm in New Zealand an the cables I'd need to connect the Yagi to the TP-Link AP would need to be made and shipped from the USA. Expense and time say, 'no'. I'm looking for a way to share the WiFi the PC's got without more hardware.

> Then it tells me that ICS will make the IP address of the LAN port be 192.168.0.1

A CompuLab Intense-PC should have come with Win7 on it... Win7's ICS uses the 192.168.137.0 subnet, not 192.168.0.0.

I would set the LAN adapter to DHCP, disable the ICS, then enable it again to let the ICS setup change the adapter's IP address to what ICS wants. Then either set the WAN port in the Linksys to use automatic/DHCP and leave its LAN side using the default 192.168.1.0 subnet, or don't use its WAN port at all - just connect to one of its LAN ports instead and Disable the DD-WRT DHCP server on the Setup->Basic Setup tab (letting the ICS assign IP addresses). Then you can either not use the WAN port at all, or check the Assign WAN Port to Switch and turn it into a 5 port switch if you need the extra ethernet port.

Possibly you'll need to delete the bridge you made in ncpa.cpl before ICS will work, too.

The evolving cybersecurity landscape presents SMBs with a host of new threats to their clients, their data, and their bottom line. In part 2 of this blog series, learn three quick processes Webroot’s CISO, Gary Hayslip, recommends to help small businesses beat modern threats.

I've long since destroyed the bridge.
I've disabled the DHCP server over on the WRT54g.
I turned off sharing on the Intense PC's WiFi port.
I set the Intense PC's LAN port to get its address via DHCP.
I enabled Sharing on the Intense PC's WiFi port.

Disable ICS in the Wireless Network Connection's Properites on the Sharing tab.

Reboot the computer.
People have almost forgotten how, as recently as Win98me and Win2k, rebooting the computer was required whenever *any* change to network settings was made. ;-)

In the Wireless Network Connection's Properties, enable ICS on the Sharing tab, and choose the Local Area Connection (the LAN adapter) from the Select a private network connection picklist.

It's up to you whether you choose to enable the 2 options below that, though if you ever want to use remote desktop from outside your LAN you can check the box next to Remote Desktop under the Settings... button, which will make an extra hole in windows firewall so you can access remote desktop through that connection.

Now check to see if the Local Area Connection (LAN port) is getting the the proper 192.168.137.1 IP address in its "Internet Protocol Version 4 (TCP/IPv4)" Properties. If it's still not, check under the Advanced... button there (on the IP Settings tab), and also on the Alternate Configuration tab (for a 'user configured' IP address).

Darr247, I'm going to award you the points on this one because you knew what should happen.

So, I solved the problem but it was a bit different that you might think.

I have two copies of Win7 on my system; both boot-able. One came with the Intense PC and is Win7 Professional. The other was transferred over from my previous machine using the tools and tricks that Paragon Hard Disk Manager 12 knows how to do. It was Win7 Premium Home. Most of the time, I've been running the latter since most of my stuff is still resident there.

It was the latter that I was having such a lot of trouble with. Once I changed my focus over to the Win7 Professional, everything happened exactly as you said and the LAN port came up and 192.168.137.1 and we were off and sharing.

So, my suspicion is that when Paragon scrapes an OS off one machine and moves it over and rewired the drivers under it to conform to the new h/w, that there's a little something that gets lost along the way.

Ah, well, this is the incentive I needed to get my remaining stuff of the Home Premium version and over onto the Professional.

Featured Post

The Percona Live Open Source Database Conference Europe 2017 is the premier event for the diverse and active European open source database community, as well as businesses that develop and use open source database software.

DECT technology has become a popular standard for wireless voice communication. DECT devices are not likely to be affected by other electronic devices and signals because they operate in a separate frequency-band.

This paper addresses the security of Sennheiser DECT Contact Center and Office (CC&O) headsets. It describes the DECT security chain comprised of “Pairing”, “Per Call Authentication” and “Encryption”, which are all part of the standard DECT protocol.

NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…