Registered: Nov 2001
Location: Merrick, NY
Posts: 34

Unfortunately it didn't fix the problem for me. I repowered the Linksys 3 or 4 times, still no response from any apps.

Thanks for trying.

Registered: Nov 2001
Location: Albuquerque
Posts: 24

I also am not getting anything from the Linksys wap.
Here is the details:
Hard coded ip address and dns numbers.
This works better than the dhcp numbers for some reason. no dns at all that way even when hard coded the dns numbers only.
so some kind of weirdness with dhcp.
When I attempt to connect via blazer 2.0 I can see packets being received by the linksys so some kind of communication is going on but the connection always times out. Once it times out the dns numbers disappear in the status page. very weird. also I am not getting any beacon received packets. only transmitted beacon packets. I don't know the exact details of how 802.11b works so it maynot be that bad. resetting the wap does nothing except change the ip number. I am pretty sure that the linksys and the belkin and the smc all use the same chipset. I could see the belkin and the linksys on the linksys software with similar firmware numbers. I am going to try one more thing and hard code the ip number on the linksys wap.
The linksys is ver 1.4f8.

Registered: Nov 2001
Location: Merrick, NY
Posts: 34

I just noticed that they've released PalmOS 4.01. for Visor. I'm wondering (well, hoping) that this may fix the application connection problems. Actual chances are probably in the 5% range. I'm going to install it tonight. I'll report the results here.

Hoping I haven't purchased a nice black paperweight. :-(

Registered: Nov 2001
Location: Albuquerque
Posts: 24

I have ordered a Cisco aironet 340 (dell labeled). I have no clue as to when I will get it. I was looking at the documentation and it has some kind of "compatability mode".

Registered: Nov 2001
Location: Merrick, NY
Posts: 34

Keep us updated. Good luck

Registered: Mar 2001
Location: Alabama, USA
Posts: 92

Firmware Upgrade for Linksys WAP11

Hello,

I just wanted to make everyone aware that there is a firmware upgrade for the WAP11. I don't know if it will help those with the Xircom Springport connect problems, but the docs seemed to indicate a problem I was having about the AP becoming unresponsive was fixed. So, it may help others...

To download it, go to: http://www.linksys.com
Then select Support/Firmware update and select the WAP11.

I hope this helps!

Driver Date : 11/12/2001
Drive File Size : Varies
--------------------------------------------------------------------------------
This Firmware is Version 1.4g.5.

Registered: Nov 2001
Location: Merrick, NY
Posts: 34

I'm actually using 1.4g.7 (from SMC, same chipset) but I suppose I could try going back to 1.4g.5 and see if it helps the problem at all. I'll check it out. Thanks

Registered: Nov 2001
Location: Merrick, NY
Posts: 34

Oh well. The upgrade to Palm Desktop 4.01 did nothing (as I thought it would) and the downgrade to 1.4g.5 from 1.4g.7 also did nothing.

A big :-(

Registered: Mar 2001
Location: Alabama, USA
Posts: 92

Some additional Info...

So you say you can't connect from you Xircom Springport to the LinkSys WAP11? I have both and am able to connect using my VisorPrism and my Xircom Springport 802.11b Module(yet, not without problems). The only problem I do experience is that after extended use (at least previously, I just updated the firmware) the WAP11 would "Hang" from time to time, requiring me to power off (pull the plug) the unit.

To help assist, I'll list the rev. of software I'm running on each and my base config:

Desktop Computer (not that it should matter):
Win98 SE
PII 400Mhz
512MB RAM
80GB HD
3Com 3c59x Ethernet card (PCI)

PDA:
VisorPrism
Xircom Springport (V1.10)

Access Point:
LinkSys WAP11 (1.4g.5)

Hub:
LinkSys Cable/DSL Router (4 Port) BEFSR41


Network config:
I use DHCP. My DHCP Server is the BEFSR41 and assigns IP Addresses in the range of 192.168.1.100... (on up). Subnet is 255.255.255.0.

The LinkSys Router/Hub is connected to a 10/100 Switch. All desktop computers are connected via the Switch. The Router/WAP11 are connected to the switch rather than utilizing the 4 ports on the router for client connections (I have about 5 laptop/desktop computers in my home).

I hope this configuration information is helpful... I know it's not much, but at least we're trying

Registered: Nov 2001
Location: Albuquerque
Posts: 24

Have any you tried to connect with encryption turned on?
I was thinking maybe more is better. Unlikely but what the hell.
I finally got a reply from intel support. Amazing. Not much help either. I think I want a new springport. Also unlikely.

Registered: Nov 2001
Location: Merrick, NY
Posts: 34

Tried it both on and off. No go.

What did mother Intel have to say? Take a hike? ;-)

Registered: Nov 2001
Location: Albuquerque
Posts: 24

Here are some things to check. Select SpringPort. Select Client Settings. Make sure your SSID is correct. The SSID information is case sensitive. If you are using Encryption, make sure it is enabled and that the settings are correct. The Encryption information is case sensitive. If not then reenter the information. Make sure that when you back out, on the Client Settings screen the Enable box for Encryption is highlighted. After you have verified the settings, then select Network Settings. Now select Preferences. Check your User Name and password to make sure the information is correct.

If you are using the Prism, Platinum and Visor Edge we need to see which Connection you have selected to use the SWE adapter. Select the Connection drop down arrow and make sure it is set to Direct USB/Serial. If you are using a DHCP server then you should not have to do anything else. If you use a static IP address then select Details and remove the check mark for IP Address Automatic and enter your IP address. If all of the information is correct then select SpringPort again and click on Status. That should connect you to the Access Point and log you in.

If you are using the Visor or Visor Deluxe we need to make sure you have entered the phone number correctly for network connections. The number has to be 00, not OO (oh oh). If all of the information is correct then select SpringPort again and click on Status. That should connect you to the Access Point and log you in.

If that does not work then try disabling Power Management. Select SpringPort, Client Settings, Advanced. Select the drop down box and click power Mgmt. You should be able to disable it there.

If you still have a problem then wipe out all of your information and select from the SpringPort screen status. That should at least connect to the Access Point. You will not be able to login but you should connect.

Also we have new firmware for the SWE adapter. The version is 1.13. When you do a status and then select Advanced Status. Now select Software Information. You should now see SW Ver: and it should list 1.13. If not then you can download the firmware from the URL listed below. The file name is XWAPDATER113.PRC.

http://appsr.intel.com/scripts-df/f...ullName=Palm+OS*+4.0&submit=Go%21

Please let us know the results.


Regards,
Intel(R) Technical Support
Xircom, an Intel(R) Company

Registered: Nov 2001
Location: Albuquerque
Posts: 24

See what this guy has to say about our beloved device.

http://www.jc-news.com/index.cgi

Registered: Nov 2001
Location: Merrick, NY
Posts: 34

I just got the exact same reply. Boilerplate. Blah. Al things I've already done. I told them it's just the apps that can't connect, I can hotsynch and ping fine.

Jeeze.

Registered: Nov 2001
Location: Albuquerque
Posts: 24

It didn't. I had heard of this magically related cure some time ago.
I am trying the more expensive solution, a new cisco wap. the springport has a cisco radio in it so I figured it would be even money that it would work. I even took the dangerous step of upgrading the wap linksys to the h firmware.

I didn't know ping was working though. Ooh. Ping but not anything else. Weird.

Registered: Nov 2001
Location: Merrick, NY
Posts: 34

I checked out that jc-news guy. I disabled power management. The green light flashes a hell of a lot more. I was excited. But alas, same results. After blazer and eudora e-mail both timed out I immediately hotsynched over the wireless connection successfully. Seems to me if I can hotsynch I should be able to download some http, no?

Baffling.

Thanks for the updates. Keep 'em coming if you find any more. I'll do the same.

Registered: Nov 2001
Location: Merrick, NY
Posts: 34

Let me know if the Cisco box works. Can you insert a link to where you bought it? I'd like to have a look.

Is your ping working? Can you hotsynch over 802.11b with the WAP11?

Registered: Nov 2001
Location: Albuquerque
Posts: 24

Here is the reply from JC. We got our cisco wap from dell. the dell wap is a cisco relabeled.

Hehehe. You missed one of the threads at VC. It linked to a review that
went over these problems. Basically, it's twofold: The minor part is that
Blazer in particular gets snotty if you have less than, say, 25% power on
the module. The major bit is that the SpringPort's power management simply
doesn't work properly. Turning it off fixed almost every problem I had.

Only remaining problem that comes to mind is that I cannot VNC to my PC
(VNC is a multiplatform app that lets you take control of the screen of a
computer); however, I was able to use VNC when I brought the Springport and
WAP11 to my workplace, so it is possible that I simply need to reinstall
the vnc server on my pc. It is possible, though, that the triple
combination of Springport, WAP11, and LinkSys cable/dsl router might be
causing something strange to happen.

*EDIT*

I just noticed that the thread to which you linked seems to already suggest
doing the power management thing. Hmmm.

Incidentally, I don't think I can ping to the SpringPort. I may not have
actually tried since it started working properly, though. <g>
Does the SpringPort have a ping daemon or something equivalent? Is there a
ping app I can use to ping *from* the SpringPort?

Incidentally, disabling power management pretty much *doubles* effective
802.11b range of the device, in my experience. I was really disappointed
with the SWE (typing in "SpringPort" is getting annoying<g> ) until I
realized that.

Here's the rundown of my SWE settings:

_Client Settings_
Client Name: Xircom SWE
Profile: 1
Network ID: linksys
Encryption: Disable
IP Address: Dynamic
Establishment Period: Normal
Network Type: Infrastructure
Power Mgmt: Disable

_Network Prefs_
Service: Cholewa (arbitrary name)
User Name: jc (arbitrarary name)
Password: (not telling, but it's arbitrary, as well)
Connection: Direct USB/Serial
Connection Type: PPP
Idle Timeout: Power Off
Query DNS: Yup
IP Address: Automatic
Script: (nothing)

_Software Information_ (under _Status_)
Manuf: Xircom
Product: SWE
SW Ver.: 1.10
FW Ver.: 3.82
Country: North America (funny, I didn't know that North America was a
country!)
Palm OS: v.3.5.2H1.5
Net Lib: v.3.2.0.d000

_Blazer_
Version: 2.0b4: 9/13/01
Images: 256 Colours
Ask before establishing Internet connection: nope
Disconnect on Exit: nope
Cache size: 511K
Free memory: 940K
Accept cookies: Yup
Use Proxy: nope

My gut feeling is that you might have to set the IP address in two places
(in both NetPrefs and Client Settings) in order to not confuse the
device. And yell at Handspring for making a springboard specification so
loose that half the modules cause a fatal reset when you take them out.

Registered: Nov 2001
Location: Albuquerque
Posts: 24

Ok, here we go. I got Blazer to work by pinging my dhcp number from my desktop to the springport. Nothing else. No magic juju at all. I tried this at work without success. Here at home it works fine. All sorts of nasty words come to mind.
I don't know why yet but Blazer at least is working. Fast too. Mail is still broke. BTW my home wap is a Belkin something. Weird thing is that after I shutoff my handspring the dhcp server is still showing the connection. Very weird. Too damn many bugs.

Registered: Nov 2001
Location: Albuquerque
Posts: 24

Yes, it is for certain. All you (I anyway) need is ping. Very weird.