Hey guys, new to boards here and after hours of searching this seemed like a good site to post.

What im trying to do is share my internet connection on one of my machines running win2k3 with 3 nic's installed 2 ethernet and 1 wireless.

I have a wrt54gs running dd-wrt hard wired to the machine running win2k3 and the second hardwired nic I'm comming out of that into a buffalo wyr-54g wireless router.

The first nic is statically assigned from the wrt54gs

192.168.1.21
255.255.255.0
192.168.1.1

I bridged that and the second ethernet connection and tried the wan and one of the lan ports on the buffalo, but it seems as if the bridge will not pass internet service to the second nic.

I don't see any packets being sent or recieved on that nic.

My goal is to basically set the buffalo up as a WAP with service provided to it from my 2k3 machine. Any help, advice, suggetions are greatly appreciated!

ICS/Bridging is one to one not one to many. I am not sure if even RRAS, which is the more robust solution, can do this either.

Your first issue though is ip addressing. Each nic has to be in a different subnet.

The two you list are in the same subnet.

Imagine the power if you knew how to internet search

So ICS can only be used to share internet access to one other device? If so I would think that would still work in my case if I can get it to give this other router an IP on the wan port then it now would have internet access and a DHCP server as will.

I haven't even thought about nor have any experience with RRAS I'll give it a look though. Thanks for the reply.

I would also settle for if somehow I could turn this machine into a WAP with the internal wifi card. If someone had a useful link I've googled ridiculously and haven't been to lucky.

Most connect the 2nd router via a crossover cable from one of its lan ports to the main router. Disable dhcp on the 2nd router. No need to run it direct to the server via a nic card. Same connectivity you desire to the server via AP.

Are you ready for where Microsoft wants you to go today?

@ wanderer

Yea that does work, but what im trying to do is have 2 seperate subnets. I'd like to leave the DHCP server on in the second router and anything connected to that router I want to make sure it cannot see/access anything groing through the main router.

Seems soo impossible, but im sooo determined to make it work.

run that by me again?

so you want to run the wireless access thru the server to the internet? Yet not have anything that connects wirelessly connect to your server?

Are you ready for where Microsoft wants you to go today?

@ wanderer

No. What im trying to do is in my server I have 1 ethernet adapter that is hardwired to my wrt54gs (running dd-wrt)

I have a wireless nic in it and then my second ethernet adapter I want to ran a cable from that adapter to this second router I have (buffalo wyr-g54) and give this second router internet access with a different subnet.

The network on my wrt54gs is

192.168.1.100/150
255.255.255.0
192.168.1.1

On the buffalo by default it is

192.168.11.1

I would like to keep it as that or

192.168.2.1
192.168.0.1 etc.

This seems so impossible for some reason, I'm surprised I haven't ran across anyone else attempting this.

If I can't achieve this I would like to someway somehow setup my server as a WAP.

If not what im trying to do if I could somehow use the wireless nic I have in it as a WAP.

Lets see if I have this.

Wireless nic doesn't matter [it can never be a multiaccess AP].

You want internet connection to the internet via your wrt54gs. You want to have the buffalo act as a wireless ap in its own subnet.

All of your lan pcs will be connecting via wireless?

No problem. You can do ics between the two nics. ICS will want to assign 192.168.0.1 to the lan nic.
http://thoughtvector.com/docs/IPAdd...

The wrt54gs at 192.168.1.1 will be just fine. ICS should be able to bridge between 192.168.0.1 and 192.168.1.1

The buffalo has to have dhcp disabled on it since ICS will be passing dhcp thru it.

Diagram looks as follows;

internet<>wrt54gs<>wan nic<>server<>lan nic<>buffalo in AP mode<>wireless pcs

Comments:
If you can't put your buffalo into AP mode you will need to connect to the lan port not wan port [you may need a crossover cable].

In theory you may be able to bridge between your wireless nic and the wrt54gs if the dd-wrt hack includes setting up a ad-hoc bridge to the wireless care.

Are you ready for where Microsoft wants you to go today?

I've tried all that bridging. Using regular cat5 and crossover cables, the wan port and lan ports. For some reason the bridge doesn't seem to wanna pass anything through. It does assign the second nic 192.168.0.1 but no data comes through. Packets sent and received always stay at 0.

The buffalo sure doesn't support AP mode and I'm not sure if my wrt54gs supports ad hoc bridge although I don't think it does. I think it only supports

AP Mode
Client
Client Bridge
Ad Hoc

Let's just focus on ICS and getting traffic to 192.168.0.1

Hook a pc to the nic being used by the buffalo. Engage ICS. Can you access the internet from the pc? What is the pcs ip?

Imagine the power if you knew how to internet search

Okay I tried all that. 2nd. nic connect to one of the lan ports on the buffalo with ICS enabled. The second nic is assigned 192.168.0.1

Still no packets sent/received that nic. The PC gets the 169.154.?.? APIPA address.

The Buffalo is configurd as:

192.168.1.151 to log in to with DHCP disabled. If I assign the PC a static address I can access the buffalo, but not the linksys. Im assuming either because the second nic isn't passing traffic or because of the way the routers are setup.

Actually the router config shouldn't matter because the linksys address is set to start at 1.100 with a max of 50 users

and the buffalo is set to start at 1.152 - .200 (with dhcp diabled of course)

Thanks for being so patient with me and continuing to help me. Everyone else gave up on other forums i've posted on.

Lets start with just the pc connected to the server. I don't see any mention of a hub or switch. If this is the case you have to use a crossover cable from the pc's nic to the servers nic.

If you don't have a crossover you can use one of the routers. dhcp has to be disabled and it can't be assigned an ip that we are using. Then it becomes just a switch by plugging the server and pc in via the lan ports.

server nic would be assigned 192.168.1.1
pc nic would be assigned 192.168.1.2
subnet mask for both is 255.255.255.0
leave everything else blank

All we want to do is ping between the pc and the server then visa-versa.

Are you ready for where Microsoft wants you to go today?

I see what your saying. Yes staticly I can communicate with 2 pc's via a crossover and static addresses. My problem is with ICS enabled whether I connect a PC or a router to the second (shared) nic I get no access and an APIPA address.

I've tried both regular cat5 and crossover both from the shared nic to the pc and from the shared nic to the router (buffalo).

Is there any alternative method to what im wanting to do besides running a cat5 line out of my wrt54gs to this buffalo?

I'm basically just wanting an WAP using my exsisting internet connection, but I don't want anyone connecting to the WAP to have access to any of my network resources.

I read about a software that is suppose to use a wifi card as an AP that would be great if I could do that. It was called "Segue SoftAP" I believe made my PCTel, but got discontinued.

I was able to find a copy on eMule but my card isn't compatiable:(

The funny thing here... I've done Net+ a few others and currently working on MCSE and waaaaaayyyy before I knew what I know now I was able to get ICS working with 2 PC's in '02 before I even knew what ICS really was :(

"My problem is with ICS enabled whether I connect a PC or a router to the second (shared) nic I get no access and an APIPA address. "

I understand this. This is what we are trying to address. Slow down.

Nov 30th - guess we are done

Please do as I suggest in post 12. No ics. Nothing but nic to pc or nic to hub/switch and pc. Basic.

Are you ready for where Microsoft wants you to go today?

@ Wanderer,

Sorry been working like crazy lately and haven't had time.

As you suggested yes I can talk machine to machine via crossover, or machine to machine with a hub or switch.