Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


fpb

fpb

8 posts

Wannabe Geek
Inactive user


#220 17-May-2003 11:57
Send private message

Hi,

I found a very annoying and strange problem. I have a Tecom 3030 USB dongle and I tried these 3 different versions of the Widcomm stack:

a) 1.2.2.13
b) 1.3.1 (from MSI)
c) 1.3.2.7

Everything works fine except lan access with 1.3.XX versions. I have switched the drivers back and forth and it is always the same: Can't get LAN access to work with 1.3.1 or 1.3.2.7

I am trying to connect with my Toshiba E740 (with internal Bluetooth) PPC. This is my setup:

Desktop machine connected to the internet via network card and Cable modem. ICS is enabled and Bluetooh Lan Access Server Driver has IP=192.168.0.1 and netmask=255.255.255.0. On the Toshiba E740 side, it works well with fixed IP=192.168.0.2 as long as the desktop has bluetooth stack 1.2.2.13 installed (1.2.2.16 also works).

From the logs on the E740 side I can see that while talking to the desktop the communication went to the point of receiving CONNECT 115200 as a response to the ATD command.
The trouble is that with the 1.3.XX versions The connection popup window never says Connected and stays as Connecting... forever!

If I go back to 1.2.2.13 on the desktop everything works fine and the popup says Connected in a blink of an eye...

Does anyone know what changed with the Network Access profile in Widcomm software from 1.2.X to 1.3.X? It seems that the PPP server on the Desktop never starts...

Thanks in advance...
Fernando Birra

Create new topic
freitasm
BDFL - Memuneh
79288 posts

Uber Geek

Administrator
ID Verified
Trusted
Geekzone
Lifetime subscriber

  #324 17-May-2003 12:41
Send private message

Fernando, have you checked this article for a checklist?




Please support Geekzone by subscribing, or using one of our referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies | Hatch | GoodSync 




fpb

fpb

8 posts

Wannabe Geek
Inactive user


  #325 17-May-2003 12:46
Send private message

I checked and everything is OK... I'm in doubt just in one thing... the DNS on the desktop for the bluetooth interface should also be 192.168.0.1 right?

I even tried running the welcome.exe on the pocketpc, but I think I have an uncommon problem since I can't get the pocket pc to acknowledge the connection... It says connecting forever...

Fernando Birra

David Hettel
73 posts

Master Geek


  #326 17-May-2003 14:34
Send private message

When you enable ICS on the desktop it will set everything on the Bluetooth connection, don't add or change anything. Other than perhaps enabling NetBIOS. The virtural bluetooth card will look to be setup wrong. Only IP and Net mask is listed. On your pocket pc you'll get an IP address (usually in the 192.168.0.1xx ramge) a net mask 255.255.255.0 and everything else will point to 192.168.0.1

David



freitasm
BDFL - Memuneh
79288 posts

Uber Geek

Administrator
ID Verified
Trusted
Geekzone
Lifetime subscriber

  #327 17-May-2003 15:51
Send private message

If you specify DNS on the Bluetooth adapter (the receiving side of ICS on the computer), then make sure it's the real DNS you have (you can find the number by doing Start | Run | CMD and then using ipconfig /all).

Only the IP for the Bluetooth should be 192.168.0.1.




Please support Geekzone by subscribing, or using one of our referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies | Hatch | GoodSync 


fpb

fpb

8 posts

Wannabe Geek
Inactive user


  #330 18-May-2003 12:50
Send private message

I tried all your suggestions and it doens't work with me. I never get the PPC to say Connected. The strange is that with the older drivers 1.2.X.X everything is OK...

This is really strange...


fpb

fpb

8 posts

Wannabe Geek
Inactive user


  #331 18-May-2003 13:25
Send private message

I finally solved the problem, but not the way I wanted...

I installed 1.3.2.7 drivers but I manually installed the Bluetooth Lan access server driver from 1.2.2.16.

Now everything works ok... and I needn't change anything...

I really think Widcomm changed something in their Lan access server driver from 1.2 to 1.3 releases.

BTonPDA
8 posts

Wannabe Geek


  #1509 22-Sep-2003 19:14
Send private message

TDK hotline told me, that it will be fixed with the next bluetooth stack verion v1.4.2.1.
It is not release yet.

Create new topic





News and reviews »

Air New Zealand Starts AI adoption with OpenAI
Posted 24-Jul-2025 16:00


eero Pro 7 Review
Posted 23-Jul-2025 12:07


BeeStation Plus Review
Posted 21-Jul-2025 14:21


eero Unveils New Wi-Fi 7 Products in New Zealand
Posted 21-Jul-2025 00:01


WiZ Introduces HDMI Sync Box and other Light Devices
Posted 20-Jul-2025 17:32


RedShield Enhances DDoS and Bot Attack Protection
Posted 20-Jul-2025 17:26


Seagate Ships 30TB Drives
Posted 17-Jul-2025 11:24


Oclean AirPump A10 Water Flosser Review
Posted 13-Jul-2025 11:05


Samsung Galaxy Z Fold7: Raising the Bar for Smartphones
Posted 10-Jul-2025 02:01


Samsung Galaxy Z Flip7 Brings New Edge-To-Edge FlexWindow
Posted 10-Jul-2025 02:01


Epson Launches New AM-C550Z WorkForce Enterprise printer
Posted 9-Jul-2025 18:22


Samsung Releases Smart Monitor M9
Posted 9-Jul-2025 17:46


Nearly Half of Older Kiwis Still Write their Passwords on Paper
Posted 9-Jul-2025 08:42


D-Link 4G+ Cat6 Wi-Fi 6 DWR-933M Mobile Hotspot Review
Posted 1-Jul-2025 11:34


Oppo A5 Series Launches With New Levels of Durability
Posted 30-Jun-2025 10:15









Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.