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

quote:

---

Originally posted by dlopan
Ok, here we go. I got Blazer to work by pinging my dhcp number from my desktop to the springport.

---

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

:-(

The ping trick didn't work for me. Funny thing I noticed is when I'm trying to connect with Blazer, a lot of the ping packets are dropped. Once the Blazer connection attempt times out it responds to all the pings. It's definitely doing something.

Registered: Nov 2001
Location: Albuquerque
Posts: 24

I connected via the status page, then I started blazer using the default handspring page.
Then I pinged the SWE and that was it. I restart the connection from blazer and it worked.
Now for the bad news. It only worked last night not this morning.
Nothing changed as far as I can tell. More bad words come to mind.
At home I have a Belkin wap. Here at work I have a Linksys Wap11 and a SMC wap. The order for the Cisco (dell) wap was FINALLY placed yesterday so it will be a while before we get that in.

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

I was talking to a guy last night who has a Cisco WAP (not sure of the model, but he said he paid about $850) and has a Springport on order. I'm going to keep in touch with him to see if it works with that setup. Is this the WAP you got? Seems pretty expensive.

Registered: Nov 2001
Location: Albuquerque
Posts: 24

Yes, it is similar. Cisco equipment is expensive.

Registered: Nov 2001
Location: Albuquerque
Posts: 24

Heres another update. I put a "ping" on my handspring and tried it. No luck initally until I pinged from my desktop. Then it worked. Sort of. It messed somehow with the dhcp server and my desktop computer stopped doing network things. I rebooted the wap and the desktop and both started working again.
More bad words. This time in Russian. I don't have the Russian fonts installed on my desktop yet. Good thing.
Gori ty sinim plamenem.

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

Ouch! I wonder what the tranlation is for that?

This is what babelfish gives:

Gori you by dark-blue flame

haha. Babelfish is funny.

Registered: Nov 2001
Location: Albuquerque
Posts: 24

May you burn in a dark blue flame.
It was close. No cigar though.

Registered: Nov 2001
Location: Albuquerque
Posts: 24

Not you you of course. I was referring to the stupid swe.
More bad words.
Goret' mne v adu sinim plamenem

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

Babelfish:

It goret ' to me in hell by dark-blue flame


babelfish has trouble with goret'

Registered: Nov 2001
Location: Albuquerque
Posts: 24

Ok here we again, more fun with swe.

1. connect (always works at home, never at work, I don't think it likes linux dhcp servers)
2. blazer and timeout
3. hotsync to desktop (always worked fine) ooh.
4. ping using dnsname (not a ip number) from swe
5. worked ok
6. blazer now works.
7. opened default web site ok
8. opened large web site and crashed
9. blazer and swe be all v'ebat
10. soft reset

I bet babelfish won't even touch that one.

Registered: Nov 2001
Location: Chesapeake, VA, US
Posts: 10

Just tossing this out...

I use an Linksys BEFW11S4 (Router w/4 port switch, and WAP), and just today received my SWE1130. Plugged it into the visor, and cradled it to charge the battery, then followed the setup instructions in the manual, and it's worked just fine. Only problem I've had is making myself not hold the Prism the way I'm used to, so that I don't end up wrapping my hand around the module (all but kills the reception); otherwise it works perfectly.

I've used MultiMail to send and receive mail from my yahoo address, used Blazer, PalmVNC, YahooIM, and ICQ without any problems.

The SWE1130 is using the software it came with out of the box (since I've not been able to download the update from Intel):

SW v:1.10
FW v:3.82

Palm OS:3.5.2H1.5
Net Lib:3.2.0.d000

Not sure if maybe the router uses different software for wireless than the stand alone WAP, but the firmware version on the router is 1.39.2, Oct 09 2001

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

I sure wish I had the router instead of the WAP. I guess I chose the wrong piece of hardware :-(

Registered: Oct 1999
Location: Colorado Springs, CO USA
Posts: 10

I havn't been checking VC for a while, so I'm sorry I didn't see this thread earlier...

I was a very early SpringPort purchaser, and have seen some of the problems you've been describing.

My best diagnosis from network traces was that the SpringPort's use of DHCP was broken (it didn't follow the protocol correctly). I then went to a static configuration of both the IP address, and DNS address.

Since then (several months ago), the SpringPort has performed flawlessly, with all applications I've tried. That included Blazer V1.0, V2.0beta, and V2.0, EudoraWeb, the MM client, TopGun SSH, Hot Sync, and others I can't recall...

I don't think it mattered (since I've used it in several wireless environments) but my WAP at home was a D-Link DWL-1000, which is fairly inexpensive.

The SpringPort firmware version didn't matter with respect to connection reliability, but the update did help with power management wierdness, and connection setup speed.

I've got to get some stuff done for work now, but I'll try to put together a list of my configuration parameters later in the day. It didn't look like they were much different from those posted in previous replies.

__________________

-Paul

Last edited by TallPaul on 12-05-2001 at 03:50 PM

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

In my IP page (off the client page, I think) I do have a legitimate IP address and route (from the DHCP server). Are you saying that even though these look good, it still doesn't work correctly and if I try static IP's it might work? That sounds great, I can't wait to run home and try it. As usual, I'll report back here.

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

Boo Hoo. Sob Sob Sob. It didn't work.

Actually, I was pretty sure it wouldn't due to the fact that I AM able to ping even with DHCP. But I was holding a slim candle of hope.

Back to the drawing board. Thanks for the suggestion.

Registered: Oct 1999
Location: Colorado Springs, CO USA
Posts: 10

My Settings...

As promised, here are the settings I use, along with a couple of observations at the end...

[SpringPort] >> Client Settings
Client Name: visor
Profile [1]
Network ID (SSID): XXX
Encryption: [Enable]

[SpringPort] >> Client Settings >> Advanced
Property: [Network ID (SSID)]
XXX
Property: [IP Address]
[Static]
Default Gateway: www.xxx.yyy.zzz
Subnet Mask: 255.255.255.240
Property: [Network Type]
[Infrastructure]
Property: [Power Mgmt]
[Enable]
Connect at Power Up: [Smart]
Property: [Encryption]
[40Bit]

[Preferences] >> Network
Service: Home Wireless {I've created this service}
User Name: XXX
Password: -Assigned-
Connection: -Current-

[Preferences] >> Network >> Details
Connection type: [PPP]
Idle timeout: [Power Off]
Query DNS: [ ]
Primary DNS: www.xxx.yyy.zzz
Secondary DNS: www.xxx.yyy.zzz
IP Address: [ ]
www.xxx.yyy.zzz

[Preferences] >> Network >> Details >> Script
[End]

[Hot Sync]
[Modem] via [Home Wireless]

[Hot Sync] >> Modem Sync Preferences
[Network]

[Hot Sync] >> LANSync Preferences
[LANSync]

[Hot Sync] >> Connection Preferences
[Direct USB/Serial]

====================

Here's the environment it works in:

Visor Prism w/3.5.2H1.5
SpringPort Module SW 1.13 FW 3.82 North America
s/n 90099A502D47
WAP: D-Link DWL-1000
Gateway: Ascend Pipeline 75 ISDN modem
Static IP addresses, no NAT box being used

It appeared to me that the interface to the SpringPort somehow interacts with the built-in serial interface, in such a way that if I have a program that has changed the serial interface parameters, the SpringPort won't work.

In my case, the IR Library add-on that allows you to use the IR port for IrDA hot-sync, when set to use the IR port, causes the SpringPort to fail. Disabling the IR lib restores SpringPort capability. I also seem to remember some settings of the [Hot Sync] >> Connection Setup to use IR also interfered with SpringPort.

__________________

-Paul

Last edited by TallPaul on 12-06-2001 at 05:19 PM

Registered: Nov 2001
Location: Chesapeake, VA, US
Posts: 10

Couldn't leave well enough alone

I just had to mess things up, and install the software upgrade for the SWE1130, so now I'm running 1.13 instead of 1.10, and I'm having to jump through hoops to get a useable connection to my network. I get DHCP information without any problem, but more often than not I can't get ANYTHING to work past that.

Anyone happen to have an update file that updated TO v1.10? When I can get a connection it's no better than before, and when I can't... well...

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

Yours worked fine with 1.10?

What Access Point are you using?

Sorry, don't have a 1.10 downgrade file

Registered: Nov 2001
Location: Chesapeake, VA, US
Posts: 10

quote:

---

Originally posted by jlanka
Yours worked fine with 1.10?

What Access Point are you using?

Sorry, don't have a 1.10 downgrade file

---