That said, the process is actually pretty simple, and you don’t have a lot of reason to be afraid. If you screw your phone up, Palm provides a tool to recover it called WebOS Doctor which will reset and re-install the software on your phone back to new. Tethering really isn’t a problem either, just as long as you use it within reason and stay under the radar. Most providers don’t pay much attention to your traffic until you consume more than 5GB in a month on your 3G connection. There’s a homebrew utility for the Pre called Netstat that will help you keep an eye on this. Don’t do something stupid like download a bunch of large files as this will probably throw up red flags at your carrier. If you just use Hotspot for web browsing a few times a month for a few hours at a shot, you probably have little to nothing to be concerned about. And, if you follow these instructions, you should have no problem installing and using Hotspot, even if you’ve never done something like this before.
There are the several basic (but detailed) steps involved:
- Turn on developer mode on your Pre
From the main screen, as if you a searching for an application, type: webos20090606
A hidden application named “Developer Mode Enabler” will show up. Tap it. When the application opens, flip the mode switch to “On”. It will then ask you to restart. Go ahead and restart.
- Obtain and Install WebOS Quick Install Download WebOS Quick Install from the PreCentral forums. Once you’ve downloaded it, double-click on the file to run it. If in the unlikely event it doesn’t run, you may need to download and install Java. When it first runs, it will ask you to download the WebOS Doctor for your carrier and phone. Just select your option, and proceed. When it’s finished downloading, WebOS Quick Install will finish starting up. Now, with the USB cable that came with your phone, connect your phone to your computer. If windows indicates that it is installing new software, wait until it completes before proceeding. Now go to the Tools menu and select Device Management. After a pause of about 10-20 seconds, you should see a windows showing you details about your Pre. If you don’t see this window, you may need to re-install the phone driver. Only in this case, go to the File menu, select Options, and click “Attempt Novacom re-installation”. After this completes, unplug the USB cable and plug it back in to re-detect the phone.
- Install Preware
Close the Device Management window. Now that you are back on the main screen, click the blue down arrow. When the IPKG Repository Viewer opens, drop down the top combo box and select WebOS-Internals Feed (Pre). Then check the box in the list below next to Preware, and click Download. When it is finished downloading, click Close. Finally, click Install. When the installer finishes, you may proceed.
- Download and Install the FreeTetherd and and Mobile Hotspot ipk files Download the FreeTetherd and Mobile Hostspot ipk files from the PreCentral forums. You may need to register to download, but registration is free. Once downloaded, drag the files into the WebOS Quick Install window and click Install. Congratulations! Mobile Hotspot is installed and ready to be used!
- Configure Mobile Hostspot
When you first start Mobile Hotspot, it will welcome you with the usual statement about needing a plan from your carrier to support it. Refer to the statements made above, and feel free to continue. By default, the phone will automatically name the wireless network something like “webOS Network 3F:2E:1D”. You may click on the name and rename it whatever you wish, such as “Palm Pre Hotspot”, or you can leave it be as is. Tap Change Passphrase and enter your desired wireless password. This is the password that will keep others from using your hotspot, and allow you to connect to it with your laptop or other WiFi device. When you have clicked done, you are done configuring!
- Connect to your Hotspot!
When you are ready to use your hotspot feature, simply tap the “Off” switch to flip it on. Then just connect to your wireless network with your laptop and enter the password you previously specified. Once it connects, you’re ready to surf! Note that while the Hotspot is running, you can still multitask on your Pre (Listen to music, browse the web, check email, etc.). When you are finished using the Hotspot feature, turn it back off to conserve battery and restore the normal WiFi client connectivity. I should also mention that on non-GSM carriers (such as Verizon and Sprint), when a phone call is placed or received, it will pause your internet connection until the phone call is ended.
- (Optional) Install Netstat
On your phone, you now have an application installed called Preware. This application opens up a whole world of free modifications (patches) and homebrew software for your Pre that isn’t otherwise available in the App Catalog. In this case, we’re going to install Netstat, which allows you to tally up your data usage over the period of a month. This should help you keep an eye on how hard you are on your data plan. To install, launch Preware. After it has finished starting up, just start typing “netstat” and hit enter. Tap “Netstat” and then tap Install. If it asks you to install dependencies, proceed. When it has finished installing, you will probably be asked to restart Luna. Proceed with the restart. When the Pre interface comes back, launch Netstat. You will then see 3 counters: The first is WiFi, which is irrelevant our concern, then 3G/Wireless (looks like a pole with radiating blue lines) which is what we want to watch, and lastly Bluetooth which is irrelevant. As you use your Pre on a daily basis, and as a hotspot, your 3G usages will increase. After a month has passed, you can click on this value to see your historical usage. Make sure you don’t exceed or even come too close to 5Gig or your carrier might have a fit and give you an uncomfortable call.
Lastly, if you ever wish to return your phone, or bring your phone in because of problems following this, I would highly recommend using WebOS doctor to restore your phone to factory default software first. Nobody at your local wireless store likes to hear about device problems potentially created by unsupported software.
I thought I’d write up a little bit on my ongoing hassles with A2DP (Bluetooth Stereo Headphones) on Windows 7. I would say it’s a hassle only on Windows 7, but in all honestly, my experiences with A2DP on WinXP weren’t much better, just different.
To start out, a little background: My first success with A2DP was with my Dell D820 with WinXP and the Toshiba Bluetooth stack. This was far from stable, but I could at least get it to work consistently by following a routine involving disabling and re-enabling the Bluetooth adapter and rebooting my headphones. From here, I “upgraded” to Windows 7 RC 32-bit, which worked OK with the Vista drivers for the D820. Audio connectivity was finicky, especially after rebooting, but I could usually get it working again just by removing and re-pairing my headphones. Next was my upgrade to the full release of Windows 7 (32bit). The same problems pretty much stuck around. My biggest issue was with a Windows Update driver that seemed to break A2DP, so I’d have to keep backing it out if I accidentally installed it. Unrelated instability issues with Win7 on the D820 led me to a new PC, the Latitude E6500.
So here I am, with brand-spanking new Dell Latitude E6500 with Windows 7 64-bit and a Dell Wireless 370 Bluetooth mini-card inside. Aside from the topic at hand, this didn’t fix the stability issues, just FYI. The from-factory drivers for the Bluetooth adapter were version 6.2.1.100 A17, IIRC. When I look it up now, it shows up as Vista 64 driver. These drivers simply didn’t work. They would pair with my Insignia NS-BTHDP headphones, create all sorts of devices in Device Manager, but no audio device would show up in the Sound control panel. Needless to say, audio never routed out to my head.
Next I tried downgrading to the 6.2.0.9600 A01 drivers, listed on Dell’s support site as being for Win7 64bit. These would pair, work for an hour or so, then apparently crash. The Bluetooth icon would disappear from the taskbar, and audio would get re-routed to my hardwired desktop speakers. This happened multiple times, and re-installing the drivers didn’t seem to help.
Currently I’m using the v6.2.1.800_7a drivers from Gateway’s website (http://support.gateway.com/support/drivers/getFile.asp?id=24324&dscr=Broadcom%20Bluetooth%20Network%20Driver%20Version%206.2.1.800&uid=263953937). These seem to work OK, so far.I did notice today that I had to toggle the wireless switch to get the Bluetooth light to activate on my laptop. Once it lit up, it automatically re-connected to my headphones. I can live with this for now. Hopefully I don’t see any more driver crashes.
Note that when re-installing these drivers, you should follow this procedure. Failure to do so can lead to some odd results in Device Manager, and total lack of Bluetooth functionality.
- Delete any paired devices (if possible)
- Clear pairings from your BT device
- Turn off the Wifi/BT switch on your laptop
- From “Programs and Features” control panel, uninstall the WIDCOMM or Dell Bluetooth drivers
- Reboot (DON’T SKIP THIS)
- Run the install for the new Bluetooth driver (v6.2.1.800 is my recommendation)
- When asked, flip the WiFi/BT switch back on.
- Reboot (just to be sure that the new driver takes)
- Pair your headphones
If you reboot/hibernate/suspend and find that the BT light is out, toggle the WiFi/BT switch.
Good luck!
UPDATE 4/2: Grr. It’s still happening. Still looking for a solution…
I don’t know why this hasn’t already been posted all over the interwebs, so I thought I’d post it here. It’s amazing how some of the simplest answers never seem to make it into prominence in the Google search rankings.
Anyway, after cloning a VM today in Xen, I tried to start the DomU, and got this error:
Error: (12, 'Cannot allocate memory')
I assumed it had something to do with my Dom0 memory cache consuming nearly every last bit of free memory on my system, so I ran this to clear the cache:
echo 3 > /proc/sys/vm/drop_caches
I confirmed that that “free” reported that the cached memory dropped near zero. Great! Except it didn’t help. I then ran “xm info” to check the memory usage in Xen
total_memory : 16378
free_memory : 2
Odd. I checked the Dom0 status to see what’s up, and sure enough, my memory allocation on Dom0 is way high.
xm list Domain-0
Name ID Mem VCPUs State Time(s)
Domain-0 0 10482 4 r—– 3273110.4
But I still didn’t know how to shrink it. I knew it had something to do with memory ballooning. I also knew you could set the memory allocation of a DomU with “xm mem-set”, but I didn’t know anything about how to do it with the Dom0. A quick IRC message to my Xen guru, Jima, and I get this simple command (obvious really) in response:
xm mem-set Domain-0 512
This balloons the Dom0 host system (as well as any domain, really) memory usage down to 512MB. In my case, my Dom0 claimed to be using about 2 Gig already, so I ballooned down to 4G instead. Not sure if that was just due to some bad math or assumptions on my part, as I never run anything of significance in Dom0. After you run this, you should be able to start your DomU just fine.
The classic procedure for installing drivers to a printer shared via CUPS with a raw Samba frontend, usually is roughly something like this:
Create printer in CUPS
Open shared printer properties in Windows
Install drivers via Advanced tab
For me, this worked great, most of the time, assuming that the driver was either PS or PCL5(e). However, PCL6 drivers rarely loaded properly. They crashed upon upload, and the driver rarely ever worked, if point ‘n print even installed the driver. As I understand it, the root of the problem is that the drivers need a valid “form” database specific to the driver to be stored on the server in order to load, but valid form data can only be created by executing the driver. On Windows servers, this isn’t a problem, but Samba servers cannot execute the windows driver code in order to generate this form. PCL6 drivers are particularly finicky about this, and often times will refuse properly copy to the server.
The solution I’ve come up with is to load the driver entirely on a Windows PC first, and tell Samba to copy the drivers and related forms, ACLs, etc over. Some of the values I use here for the printer names, etc, are very generic and only specified to match the naming standards in my environment. Feel free to change your printer setup to suit your needs.
The Procedure
On a Windows PC:
Install the printer as you would normally for TCP/IP printing on a windows PC.
Rename the printer to the share name you will be using (i.e., CopierCP5000)
Open the printer properties
Share the printer using the same name (CopierCP5000)
Set the printer description to the printer name (i.e., Copier CP 5000)
Set the printer location to the office name and city (ACME Abu Dhabi)
Usually under the Accessories/Options tab, update/get information from the printer This ensures that we obtain all the correct hardware configuration information for the device (duplexer, trays, hole punch, stapler, etc)
Open the Advanced tab and click the “Printing Defaults” button
Click on each tab and allow the tab to load This ensures that the form values for each tab are created.
Still inside the Printing Defaults, change the page orientation to Landscape, hit apply, change the page orientation to Portrait, and hit apply. Click OK.
Close the printer properties by clicking OK
Next, on the server:
### Set up the printer in CUPS, i.e.:
lpadmin -p CopierCP5000 -L "ACME Abu Dhabi" -D "Copier CP 5000" -v lpd://192.168.xx.xx -m raw -E
smbcontrol smbd reload-config
### Copy the drivers, forms, ACLs, etc from the Windows PC
net rpc printer MIGRATE ALL CopierCP5000 -S mypcname -Uusername
Finally, test the driver in Windows:
Open the local Printers control panel (shortcut command below for Win7 users) rundll32 shell32.dll,SHHelpShortcuts_RunDLL PrintersFolder
Delete your shared printer
Right-click in the control panel window and select “Server Properties”
Open the Drivers tab
Select your driver and click “Remove”.
Proceed with removal and close the server properties window.
Open \\servername\
Double-click your printer
Print a test page If this fails, try restarting the local PC’s Print Spooler service
So far I’ve only tested this on a few of our known-problematic printers that have PCL6 drivers available, and it’s worked perfectly in each case. However it you notice this doesn’t work for you, post a comment and I’ll see what I can do to help.
I just got this email in my inbox this morning (BCC’d to me):
From: (My Boss)
To: (Our Company Sprint Rep)
Subject: Palm Pre
What are the chances of getting our hands on a couple of these when they are released?
(Other Palm User) from (Our Company) and (Muchtall) from my office are waiting patiently for these….
Thanks,
(My Boss)
Pretty awesome. Hopefully our Sprint rep can swipe us a couple before the masses clean the stores out.
Update 6/2: Just got an IM from my boss:
(11:17:23 AM) Boss: hey you available for lunch on Thur?
(11:17:32 AM) Muchtall: Sure
(11:17:43 AM) Boss: Im gonna get our Sprint reps to take us out
Sweet!
Update 6/8: So I was greeted by this email earlier this morning:
To: Boss (fwd'ed to Me)
From: Purchasing Dept
Subject: (Muchtall's) Phone
Just received call from Sprint, phone on backorder. Not sure when resupply fulfilled, will keep you in touch.
Which sucks. However, a few hours later, I get this email:
From: Corporate Sprint Rep
To: Purchasing Dept (fwd'ed to Me)
Subject: Pre
Inventory is expected tomorrow so you should have on Wednesday.
I had been using FeedDemon for a while, but it missed the second half of my toaster requirement. That and for whatever reason it seems to take days to get updates to feeds, even when I’d tell it to update sooner.
I recently switched to FeedReader, and I have to say, if you’re looking for a Windows-based RSS reader, you should make this the first client you try. It will probably be the last one you’ll need.
If you aren’t using an RSS reader, I highly recommend it. They make life so much easier when you are trying to keep up to date with your favorite news sites, and most sites offer an RSS feed nowadays. It’s nice to be able to just open FeedReader and see a list of what sites have updated articles, and even limit the stories to the topics you want. In my case, it’s made keeping up with all the latest Palm Pre news a snap. Instead of periodically refreshing 10-15 different sites in Firefox, I just listen for that chirp.
After having a SourceForge account for about 10 years, I’m canceling it for one reason and one reason alone: Spam. SourceForge has this “feature” where anyone can email you at yourusername@users.sourceforge.net, and they will happily forward it on to the email address you have on file with SF. That’s great, except, I don’t want spam bots emailing me. It would be great if you could either opt out of this behavior, or even specify a human-readable anti-spam address as the forwarding address, but SF doesn’t offer either of these options. It’s either you have an account and all the crap that comes with it, or you have nothing. So I choose nothing.
Thanks for nothing SourceForge.
So I guess if I actually want to use the SF site for forum activity, I’ll have to re-create my account each time.
Update: Ok I lied, sort of. Turns out that if you delete your SF account, you can’t come back and re-create it. This sucks because I like my persona, and should I come back, I’d like to re-use it. So now I’m willing to give feedback a chance. Vote for Solution 3!: SourceForge Spam Solution
Update 10/15/2009: You complained, and SF listened. I got a Tweet last week from @sourceforge informing me that they have added an option to allow you control over your alias behavior. You can find this setting at https://sourceforge.net/account/. Go there. Now! That is all.
Say you have an internet radio stream that you like to listen to. You like to actually get up from your computer once in a while and go outside, so you want to play it on your iPhone/Blackberry/G1/Treo/Centro/Pre/Whatever as you’re out and about. But wait! Due to poor decision making by your beloved stream provider, your favorite stream is only in Microsoft’s poorly-supported ASF streaming format. There’s no MP3 or OGG options! Many if not all of the phones I just mentioned may/will not play these streams, at least not natively. MP3 on the other hand, is ubiquitous (though, given, not truly as free as OGG). One option you may have, if you run your own Linux server, is to download the ASF stream, re-encode it to MP3, and re-stream it via your own Icecast server. Icecast is easy enough to set up, however information on setting up the VLC portion of this workaround online seems a little slim online, so I thought I’d make a post simplifying the setup.
First off, check to make sure your VLC has “Shout” Shoutcast/Icecast output support:
vlc --list | grep access_output_shout
You should see the following in the output:
access_output_shout IceCAST output
If not, you may need to either re-install with a version of VLC that supports shout output, or recompile it with shout support.
Then run the following command, altering the items in bold for your purposes (all on one line):
Assuming you have already properly set up your Icecast server, you should now have a mountpoint running the stream you have just created.
Note that VLC seems to have problems parsing some ASX playlist files. You may need to download the ASX file with wget to investigate what the actual stream URL is. For example, the stream above came from “http://minnesota.publicradio.org/tools/play/streams/classical.asx”, which had these contents:
<ASX version="3.0">
<ABSTRACT>The Windows Media Stream for MPR's Classical Music Service</ABSTRACT>
<TITLE>MPR Classical Windows Stream</TITLE>
<AUTHOR>Minnesota Public Radio</AUTHOR>
<COPYRIGHT>2009 Minnesota Public Radio</COPYRIGHT>
<MOREINFO HREF = "http://minnesota.publicradio.org" />
<ENTRY>
<TITLE>MPR Classical Windows Stream Underwriter</TITLE>
<COPYRIGHT>2009 Minnesota Public Radio</COPYRIGHT>
<REF HREF="http://ondemand2.publicradio.org/ondemand/joinnow.wma"/>
<BANNER HREF="http://www.publicradio.org/applications/underwriters/images/prepend/content/joinnow.gif">
<MOREINFO HREF = "https://contribute.publicradio.org/"></MOREINFO>
</BANNER>
</ENTRY>
<ENTRY>
<TITLE>MPR Classical Windows Stream</TITLE>
<COPYRIGHT>2009 Minnesota Public Radio</COPYRIGHT>
<REF HREF="http://classicalstream2.publicradio.org/classical"/>
<BANNER HREF="http://www.publicradio.org/applications/underwriters/images/prepend/content/joinnow.gif">
<MOREINFO HREF = "https://contribute.publicradio.org/"></MOREINFO>
</BANNER>
</ENTRY>
</ASX>
As you can see, the first item in the playlist is NPR’s obligatory call (**cough** commercial **cough**) for donations (http://ondemand2.publicradio.org/ondemand/joinnow.wma). The second is your actual stream URL (http://classicalstream2.publicradio.org/classical). You’ll want to use the stream URL in your VLC command.
Also, I have seen cases where VLC pukes on some ASF streams. Though I haven’t confirmed this, it appears to be a bug with downsampling/resampling (http://mailman.videolan.org/pipermail/vlc-devel/2009-February/056823.html). In these cases, you may need to look that the 1.0.0 prerelease versions, which may not be available on your distro release (Fedora, for example, doesn’t have it until 11). Good luck!
UPDATE 10/27/09: It would appear that the precompiled RPMs offered on the VLC site for 1.0 or higher do not contain support for shout output. Not a big deal. Just download the source RPM (e.g., from http://download1.rpmfusion.org/free/fedora/development/source/SRPMS/) install the sources (rpm -Uvh vlc-1.0.3-0.1_rc.fc12.src.rpm), and edit the vlc.spec file (usually found in ~/rpmbuild/SPECS/). Look for a line that says “–enable-realrtsp \” and add a line below it that says “–enable-shout \”. Save and close the file, then run “rpmbuild -ba vlc.spec”. After it recompiles, install the updated RPMs (cd ~/rpmbuild/RPMS/x86_64/ ; yum –nogpgcheck reinstall vlc-core-1.0.3-0.1_rc.fc11.x86_64.rpm vlc-1.0.3-0.1_rc.fc11.x86_64.rpm). Make sure to alter the above paths to reflect your architecture, Fedora release, and vlc version.
I’m taking a shot at yes. Here’s why it makes sense to me:
- Why else would you put up a countdown to zero (Doughnut, btw) to such an obscure holiday?
- As has been restated by Palm and Sprint repeatedly, the date falls in the first half of the year (albeit late).
- It’s a few weeks after the start of the just-announced Sprint vacation freeze
- It’s the weekend before WWDC, potentially stealing the iPhone 3.0 / next-gen iPhone thunder.
Now, my only skepticism of the date is how close it lands to WWDC. Either the Pre will be a massive hit, and the buzz will be loud enough going into the following week to drown out the potential iPhone announcement, OR the Pre buzz quickly loses steam following launch, drowned out by the well-established Apple fanboy crowd. The potential for loss on this toss of the dice is pretty great.
That’s why I’m making one additional prediction: Palm drops another bomb on release day. Probably some yet-unseen killer app that the iPhone doesn’t have. I’m guessing something that exploits the multitasking capabilities, and furthermore, can’t be done via push. Palm needs something more just after the release to keep the unique multitasking abilities of the Pre in the front of people’s minds right through the iPhone announcement.
If I’m right, you can say you heard it here first.
Not that I have a problem with this policy. I just think it’s funny how the mass of Obama supporters assumed that this was what “Change” meant. In reality, the only Change in store is more government control over you.
I’ve been drooling over this device since it was announced in January. Now that ads are actually starting to show up, the only thing left to see is a release date.
UPDATE: Adding new commercial clips as they come out.
Just making a quick post to help out any Googler’s out there looking for the solution to this problem. I had a Dell SC1425 pizza box server with an error/alarm light on it’s face recently. The alarm showed up when the server had been rebooted after a full lockup. I downloaded the Dell DSET utility and ran a report, which found this error:
PROC Machine Chk processor sensor transitioned to non-recoverable
Basically this means that the mainboard detected that the processor stopped responding (i.e., locked up), which of course we already knew.
To get rid of the alarm light, just run DSET again and tell it to clear the log. After you do so, your server lights should once again be a calming, cool blue.
Today I was troubleshooting a couple of network printers. One of them, I believed, had an incompatibility with “Standard TCP/IP” printing, via RAW communications. I tired other printer port options, including the HP TCP/IP port. I found out later on that the printer itself (a multifunction copier actually) did not have printing capability enabled. In the process of installing a printer driver later in the day, I ran into this error:
The instruction at “0×00000000″ referenced memory at “0×00000000″. The memory could not be “written”.
The error wouldn’t go away. Reboots did nothing. Clearing out all registry references of the printers and drivers that I had been troubleshooting did nothing. Deleting my printer drivers folder only made things worse (as you’ll read later) Even a reverting to an earlier System Restore point failed. Finally, after finding tidbits of information online here and there, nothing with a complete solution, I tried removing this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\HP Standard TCP IP port
I then restarted “Print Spooler” in the Services control panel (services.msc), and my Printer control panel finally displayed properly, without crash. Unfortunately for me, I then had to delete all my printers, as I had deleted all of my printer drivers and none of the installed printers were functional.
So if you run into this error, try deleting the key above before attempting anything else.
Now, I’m no fan of the American auto industry either, but for much different reasons than Obama. Obama sees the auto industry as a whole as evil greedy capitalist pollution profiteers, and clearly takes joy in overseeing their demise. He sees the collapse of the American auto industry as a success of his ideals.
I, on the other hand, dislike what the American automobile makers have allowed to have happen to their once prosperous industry. One has to ask the question: Why are the foreign owned, yet locally manufactured, automobiles doing just fine in today’s economy, yet the American manufacturers are struggling? The answer: Unions. The successful auto makers never bowed to union pressure. Foreign companies realized the hazard of giving up control of their own companies to socialist union thugs, pushing unsustainable pension plans and benefits. If the American auto industry had the spine to kick them out years ago, they’d be much better off now.
I’m finally taking the plunge into WordPress. I’ve moved all of the accounts (minus passwords), categories, stories, and comments over from the old PHPNuke site. I have yet to pretty up the theme, but I just couldn’t wait any longer. PHPNuke was just too difficult to maintain, and worse, was prone to spamming from bot-created accounts.
If you ever get into a situation where you can’t find the password used on your Qwest DSL account, and you have an Actiontec M1000 router (or similar), give this procedure a shot:
- You can find your account username on the Quick Setup page, listed as "PPP Username" - Set your router admin password if you have not already done so. Take note of the username and password you set. It’s important. - Go to Start –> Run and enter "telnet 192.168.0.1" - Login with your admin account and password, i.e., admin/admin - Run this command "cat /var/tmp/pppoe_password". The output is your account password. - Confirm your account credentials by logging in at at http://www.qwest.net
Though I still know my way around, it’s been a while since I messed with a Cisco router to any great degree. But today at work I had to configure a Cisco 1750 to reply to one of our offices. I like backing up configs before I blow away a router, just so that I have a copy of what was on there. I knew that I could TFTP it to my PC, assuming I set up a TFTP server. So I went and installed Tftpd32 to my PC, set up a secondary IP on the Cisco router on my local network, and fired up the following command on the Cisco console:
I then saw on Tftpd32 that the router connected, and created the file "cisco.txt", however the transfer failed and the resulting file was 0 bytes. This is the error I got on the console:
Clearly, the Cisco was connecting, it just wasn’t sending the content of the file. After running a standard FTP test, I noticed that the Cisco showed up to the server as the PRIMARY interface IP, not the secondary one. Once I re-assigned the primary IP address to the local IP range, the transfer succeeded.
So, long story short: If you see this error, check that the primary IP on the interface facing your network is in the same subnet as you (or the next hop), otherwise the Cisco might show up as coming from an unreachable IP.
