lacaco

I have read the manual, and have netfront installed on my TG50/U , I am using a Ambicom Bluetooth wireless USB adapter. It recognizes the clie and the clie recognizes the computer, (so far so good), I went to network and edit connections, attempted to connect to local network and when it goes out and searches for a connection it says "none found" but if I put it back on computer than it will find the computer but do nothing. I attempted to ask Sony tech support but I might as well ask the wall because they didn't seem to know very much.
can someone PLEASE help me.


Thanks
Larry
Anchorage, Alaska

Andyvan

Did you try doing a search before you asked? This has been asked and answered several times.

-- Andyvan

Here's something I grabbed from one of the answers:

[QUOTE]
Bluetooth Internet Connection
It took forever, but I have the magical settings that will get a Windows 2000 PC connected to the Internet to share its connection over a Bluetooth-enabled Clie.

The following steps assume that:
1. You already have networking set up and can browse the Internet on your PC
2. You have installed all of the Bluetooth software for your USB dongle (I am using the DLink dongle)

Step 1: Ensure that both your LAN and Bluetooth connections are active (running).

Step 2: Enable connection sharing on your LAN card (the one hooked up to the Internet, NOT the Bluetooth one). This will give you a message about how the Bluetooth network address will be set to 192.168.0.1. This is fine. It doesn't matter if your home network is on 192.168.1.x. I am running this machine on DHCP right now, but my guess is that it doesn't make any difference if you are using static IPs. I'm going to try this at work tomorrow, so I'll post updates then.

Step 3: Configure your Bluetooth network. Make sure to specify the same DNS entries and gateway as your LAN network. This is the part that I kept messing up!

Step 4: Configure your Clie.
1. Make sure Bluetooth is enabled.
2. Make sure that your Clie is paired with the PC.
3. Now open up the Network settings and set the Service to Bluetooth, no user name or password, and the Connection is the Bluetooth Network.
4. Click on Details and set the Connection type to PPP, Idle timeout to whatever you want, and unselect DNS and IP Address.
5. Then enter 192.168.0.2 (or any other 192.168.0.x number other than 192.168.0.1, which is your PC) for the IP Address, and enter the same values for Primary and Secondary DNS as you set for both of your connections on your PC.
6. Click on Script and make sure that you have only one entry: End.

That's it! You may have to enable/disable the network connections on the PC and/or Clie before things get moving, but that is all there is to it.

Here is a Ping app for the Clie that was indispensible to me:
<http://www.searat.com/ping/ping_100d7.zip>

[\QUOTE]

lacaco

Yes, i read that reply previously, but if you look at my message I am using XP and after I tried this solution it didn't work, for me!!!

Larry

Andyvan

Ok. I think when I set this up on an XP system, I actually used bridging instead of Internet Connection Sharing. I bridged the desktop's Bluetooth connection to the desktop's LAN connection.

The thing to do is to figure out *where* the connection fails:

1) Can you pair the devices?
2) If so, can you ping the desktop PC's Bluetooth IP address? I believe the using either ICS or bridging will result in your desktop PC being given an IP address on the Bluetooth subnet. You can find out what it is by using the "ipconfig /all" command at a command prompt. Using the ping app, can you ping this numeric IP address?
3) If so, then try pinging your desktop's LAN IP address?
4) If so, can you ping your router's numeric IP address?
5) If so, can you ping "66.218.71.92"? This is "www.yahoo.com".
6) If so, can you ping "www.yahoo.com"?
7) If so, then your Internet connection is fine, any additional problems would be in your PDA web browser setup. If not, then the problem is with your DNS setup on your PDA.

If you follow this, we're taking this step by step, from the simplest connection, all the way out to the full-on Internet with name resolution. By figuring out where the chain first breaks, you get an idea of what to look at.

Sorry for assuming you hadn't read other posts. Usually that's a fair assumption when a guest posts about something that's been discussed to death!

-- Andyvan