Bluetooth Internet Sharing

Supplies:
1 Windows-based Laptop with Intel 3945 ABG + Bluetooth, and Ethernet Card
1 Mac-based Laptop with Airport card + Bluetooth, and Ethernet Card

Both of the computers have bluetooth and Ethernet ports. Since we only have one ethernet cable and we are not permitted to use routers/switches, I am trying to get one computer plugged in to the Ethernet and to "relay" the internet over bluetooth to the other computer. How would I do this? Can someone post a guide?

 

*Bump*
Please, someone help me!!

 

you don't want to connect via bluetooth, you want to connect via wifi cards. keep in mind it's a poor solution. what do you mean you are "not permitted to use switches or routers" ?

 

bluetooth was designed as a low speed solution to wireless connectivity of peripherals...so mainly connecting mobiles, pda's to sync/transfer small files to your pc etc...so sharing the internet over bluetooth wouldn't be viable if it can be done (i don't think it can)

 

it can but it is very slow

 

If it can be done via WiFi cards, I would really like to know how. I'm guessing that one of the wireless cards would have to act as an access point. I really don't care HOW it's done, I just need to know HOW EXACTLY TO DO IT. I do appreciate all the replies, but I really just need to know how.

 

I'm in the same boat as szabodabo. I've tried setting up an access point on my wired PC. The laptop picks up the access point network (very strong signal) but I've never been able to get it to share files or the internet connection. Have tried it with all firewalls off, etc. Using Zyxel wireless access point hardware/software and Zyxel wireless network card on the laptop.

I know an access point network can be done and there's some trick that I don't know/am missing. For folks who won't be using the network for gaming or running programs between the computers - only simple file sharing or www access, it should be possible and work fine. I'd appreciate any thoughts/ideas too.

In researching this, I've seen numerous options on resolving connectivity issues (setting the machines up on the same network, not setting them up on the same network, let wireless zero handle everything, don't let it handle everything, assign WAP/don't assing WAP, and on and on). So, it could just be some combination of everything that we may just have to stumble across. It's just not as simple as plug-and-play, which is how it's often advertised.

 

There's a perfect guide for what you want to do here. It's called an " Ad-Hoc" network and it's really not that hard to set up. This works over 802.11, not blutooth since that's not really what you want to do. Also, this relies on you using the PC with the cable and the Mac receiving the signal. Let me know if you need any extra help.

~ Brett

 

Thanks, Brett. That was the first article I found on it and one of the reasons I thought it would both fit my needs and be simple (I share a connection and can't add another router/gateway).

Somewhere in my research on this, I seem to recall something about ad hoc not working well if one PC is XP Pro and one is XP Home, which is the arrangement I have. I've adjusted to just unplugging from one and plugging it into the other one. I've read about RJ-45 splitters, too, but am not thrilled with extra wires running around the place.

Hopefully, ad hoc can work out with the OPs setup of a Mac and a Windows PC.

 

I can't see a good reason why XP, XP Pro or even Mac OS wouldn't work well together since the wireless works on 802.11 for all of them and (from what I understand) it's fairly standard. It takes about 30 seconds to setup with that guide so it might at least be worth a try.

P.S. - On second thought, I know it's possible to go ad-hoc between XP and XP Pro since I've done it. Where, exactly, do you run into the problem?

~ Brett

 

Brett,

Thanks for your feedback and offer for help. And guess what? I just realized something. I don't think I've actually connected to the wireless network!

I set up the ad hoc on the wired desktop, and it is detected by the laptop and shows a strong signal from 10 feet away. The step that I think I missed is to actually click on the network box on the notebook (in the list that pops up when I have it set to locate wireless networks) and connect, which I have never done (I really do need very specific info/steps sometimes).

So, the ad hoc network would appear network list (on the notebook), and I just assumed I was automatically connected since it was an open network (no encryption, no firewalls until connection is confirmed, then adding those steps for security later). So would try to share the internet connection or browse the shared folders but would not abe able to.

I'll have to try this again sometime this week and will post. Don't know how/why this even occurred to me. Talk about a DOH! moment.

From everything I've read, I believe you're right- OS should not make a difference as long as the computer itself is able to either send and/or receive the signal, the OS shouldn't matter and it should be easy to do.