Wireless + Wired Network?!

[DeLeon]

I had the same issue with my home network. I installed a second NIC in my server, installed an RJ45 wall plate where I keep the server and another one close to my desk.(its eye level and arms reach when I'm sitting at the desk) I ran some CAT6 under the floor and basically have a direct connection with the NICs. I'm not sure about your situation, but I was just going across the room (closet to desk) and i think i paid around $15.00 for 50ft of cat6. It works great for me. It was a little confusing making the cables at first, but I think that was just me. Obviously you don't have to use the wall plates, a simple crossover cable between the two computers should work for a direct connection...no internet sharing required.

[SCone]

Originally Posted by ParkImaging

the wireless network gets dropped/ignored and I no longer have internet connectivity... but I do have a fast wired network... which I only need to xfer files back and forth between the PCs.

- Wil

You could set up a static address scheme for the wired network. Then add a route or simply use it as a mapped network drive.

There is more going on here for the wired to work & for the wireless to work independent of each other but not together.

How does the server obtain it's address? Does it access the internet? Where is your address scheme coming from? A DHCP server, where? Static, what is the scheme?

[DoctorWu]

Forget the switch.

Plug the laptop and the server into the wireless router.

Done.

[Dobick]

Originally Posted by DoctorWu

Forget the switch.

Plug the laptop and the server into the wireless router.

Done.

That is the way that I would go about accomplishing this, but if I was a betting man, I would bet that there is a specific reason that this wasn't done in the first place. The first thing that comes to mind would be that there is no ethernet drop going from the router to the server, and to add one would probably be more of a hassle than it is worth.

[Beezwax]

This is a simple home networking connection... user defined IP addresses should not be needed... simple networks will automatically define the IP and Subnet IP's on it's own. File sharing networks are as simple as pluging them all together, wired or wireless... doesn't matter and creating shortcuts to access the shared files on other machines connected to the network.

if the situation calls for 3 wireless PC's and 1 wired laptop, all the same rules apply.. the router... NOT SWITCH OR HUB will automatically link all the pooters together on the same IP.

Manually defining IP's is most usefull when "mapping" network drives together...this allows more access from one machine to another.

It's not recomended to use a operated machine as a file server to store ALL files...

it really is very simple....

[DoctorWu]

Just the other day I climbed up into the attic to drop a new line.....on second thought....do it the hard way.

[Dobick]

Originally Posted by DoctorWu

Just the other day I climbed up into the attic to drop a new line.....on second thought....do it the hard way.

Been there and done that!!!

[Beezwax]

[KdLaneJr]

I like, and have used, both methods that Ben and Cliff have laid out for you. My current setup has all the computers going to one switch and then the switch goes to the wireless router. When my laptop is not connected via ethernet it uses the wireless signal. When connected to the switch it still sees the internet via the switch and the router. Mapping your server will make your server visible to your laptop via wireless and ethernet.

This makes the wireless internet mute when connected to ethernet.

From what I read in the previous posts you have plenty of info here to help you out.

[3n-Out]

The route to the internet is totally dependant on it's capability to resolve DNS names. So, if you setup a static link and ommit the DNS Name and WINS. On the wired network on your laptop make your gateway the IP of the Server. NO DNS. Then connect to the server using the IP Address and not the WINS Name.

On the Wireless keep it as you have it.

Then again you could use IPS/SPX or another protocol like NETBEUI "Depending on your OS". But I ask the question, why use wireless when you can uwse wired? Wired is much fast, more secure and has a heck of a lot less overhead in errorant packets.

The trick to all this is setting up the correct IP Gateway, and Static IP's. The other simple solution which will cost a few dollars is to get another network card in you server and multihom it. Setup 2 differnt IP's and do the above.

Hopefully I explained that well enough, as I can't think striaght because I'm so freakin' congested I can hardly read the screen..