<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
 xmlns:admin="http://webns.net/mvcb/"
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns:content="http://purl.org/rss/1.0/modules/content/"
 xmlns:wfw="http://wellformedweb.org/CommentAPI/">
<channel><title>Blog In Progress | Comments</title><description>Notes/Domino, Small Business Computing and Life</description><link>http://bloginprogress.us/blog/BlogInPr.nsf/</link><language>en-us</language><lastBuildDate>Wed, 2 Jun 2010 11:49:53 PM -0400</lastBuildDate>
<item>
<title>Procomm rocks</title>
<pubDate>Wed, 2 Jun 2010 11:49:53 PM -0400</pubDate>
<dc:creator>Stephan H. Wissel</dc:creator>
<dc:subject>Unified Communications circa 1996</dc:subject>
<description><![CDATA[Scripted Procomm was like Magic. I wonder what happened to it.]]></description>
<content:encoded><![CDATA[Scripted Procomm was like Magic. I wonder what happened to it.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/procommplus.htm?opendocument&amp;comments#06022010114953PMRHS6HQ.htm</link>
</item>
<item>
<title>ProComm</title>
<pubDate>Wed, 2 Jun 2010 04:14:32 PM -0400</pubDate>
<dc:creator>Gregg Eldred</dc:creator>
<dc:subject>Unified Communications circa 1996</dc:subject>
<description><![CDATA[ProComm was my preferred communications software "back in the day." Ahh, choosing the proper file transfer protocol, scripting file transfers, it was a good time. Brings back some nice memories. Thanks for sharing.]]></description>
<content:encoded><![CDATA[ProComm was my preferred communications software "back in the day." Ahh, choosing the proper file transfer protocol, scripting file transfers, it was a good time. Brings back some nice memories. Thanks for sharing.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/procommplus.htm?opendocument&amp;comments#06022010041432PMRHSRR5.htm</link>
</item>
<item>
<title>Upgrade applied</title>
<pubDate>Sun, 30 May 2010 09:16:46 PM -0400</pubDate>
<dc:creator>David N Schaffer</dc:creator>
<dc:subject>Weird Blackberry Enterprise Server Domino issue</dc:subject>
<description><![CDATA[Downloaded and installed BES 4.1 SP7 from blackberry.com. Now running BES 4.1.7.17.<br /><br />The NBES.EXE task is using less memory than it was after a fresh start of 4.1.6 so we'll see if the usage grows or if the problem is resolved.]]></description>
<content:encoded><![CDATA[Downloaded and installed BES 4.1 SP7 from blackberry.com. Now running BES 4.1.7.17.<br /><br />The NBES.EXE task is using less memory than it was after a fresh start of 4.1.6 so we'll see if the usage grows or if the problem is resolved.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/BESmigration.htm?opendocument&amp;comments#05302010091646PMDNS3HH.htm</link>
</item>
<item>
<title>re: upgrade it</title>
<pubDate>Sun, 30 May 2010 09:02:42 AM -0400</pubDate>
<dc:creator>David N Schaffer</dc:creator>
<dc:subject>Weird Blackberry Enterprise Server Domino issue</dc:subject>
<description><![CDATA[It turns out we're a bit behind: Running 4.1.6.12, latest is 4.1.7.3. Also, 4.1.7 is supported on Domin on 8.5.1, although 8.5 is still recommended, but that gives me the option if I need to try that.]]></description>
<content:encoded><![CDATA[It turns out we're a bit behind: Running 4.1.6.12, latest is 4.1.7.3. Also, 4.1.7 is supported on Domin on 8.5.1, although 8.5 is still recommended, but that gives me the option if I need to try that.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/BESmigration.htm?opendocument&amp;comments#05302010090242AMDNSHAM.htm</link>
</item>
<item>
<title>upgrade it</title>
<pubDate>Sat, 29 May 2010 09:46:54 PM -0400</pubDate>
<dc:creator>keith Brooks</dc:creator>
<dc:subject>Weird Blackberry Enterprise Server Domino issue</dc:subject>
<description><![CDATA[get to the latest 416 bit of bes would be my suggestion.<br /><br />But also try to reinstall the last fix pack if you are already at latest.<br /><br />Sometimes the install does not go through properly.]]></description>
<content:encoded><![CDATA[get to the latest 416 bit of bes would be my suggestion.<br /><br />But also try to reinstall the last fix pack if you are already at latest.<br /><br />Sometimes the install does not go through properly.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/BESmigration.htm?opendocument&amp;comments#05292010094654PMRHS44V.htm</link>
</item>
<item>
<title>It&#8217;s been fine for me.</title>
<pubDate>Mon, 5 Apr 2010 08:15:43 AM -0400</pubDate>
<dc:creator>Denny Russell</dc:creator>
<dc:subject>LinkedIn for Blackberry</dc:subject>
<description><![CDATA[I've had it installed since last week when I downloaded and blogged about it. I've yet to have an issue with it and have been using it daily. I'm using it on an older Curve.]]></description>
<content:encoded><![CDATA[I've had it installed since last week when I downloaded and blogged about it. I've yet to have an issue with it and have been using it daily. I'm using it on an older Curve.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/linkedinforbb.htm?opendocument&amp;comments#04052010081543AMRHSGDV.htm</link>
</item>
<item>
<title>Update 1 on LinkedIn for Blackberry</title>
<pubDate>Sun, 4 Apr 2010 12:50:34 PM -0400</pubDate>
<dc:creator>David N Schaffer</dc:creator>
<dc:subject>LinkedIn for Blackberry</dc:subject>
<description><![CDATA[It's connecting and updating just fine on a Sunday afternoon from home (WiFi) so I suspect it's getting overwhelmed with volume during the business day.]]></description>
<content:encoded><![CDATA[It's connecting and updating just fine on a Sunday afternoon from home (WiFi) so I suspect it's getting overwhelmed with volume during the business day.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/linkedinforbb.htm?opendocument&amp;comments#04042010125034PMDNSMQU.htm</link>
</item>
<item>
<title>Switching Issue and home routers</title>
<pubDate>Thu, 18 Feb 2010 03:23:42 PM -0400</pubDate>
<dc:creator>David N Schaffer</dc:creator>
<dc:subject>IP Address Conflict on Server</dc:subject>
<description><![CDATA[It took me a long time to identify the user with the home router set to overlap the servers. Now we can change it.<br /><br />For what it's worth, Netgear's default is apparently to start assigning at 192.168.1.2.]]></description>
<content:encoded><![CDATA[It took me a long time to identify the user with the home router set to overlap the servers. Now we can change it.<br /><br />For what it's worth, Netgear's default is apparently to start assigning at 192.168.1.2.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/IPConflict.htm?opendocument&amp;comments#02182010032342PMDNSRWW.htm</link>
</item>
<item>
<title>Switching Issue</title>
<pubDate>Thu, 18 Feb 2010 12:11:17 PM -0400</pubDate>
<dc:creator>Reid Partlow</dc:creator>
<dc:subject>IP Address Conflict on Server</dc:subject>
<description><![CDATA[That's always the way of it. Things are hard to change, depending on your dhcp server, you can try looking at some of your bootp settings as well. Some adjustments there may help. You do however, know the offender's mac's, so you can just offer to have them bring in their home routers and you can do them (mostly you) a "favor" and reconfigure their devices for them.]]></description>
<content:encoded><![CDATA[That's always the way of it. Things are hard to change, depending on your dhcp server, you can try looking at some of your bootp settings as well. Some adjustments there may help. You do however, know the offender's mac's, so you can just offer to have them bring in their home routers and you can do them (mostly you) a "favor" and reconfigure their devices for them.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/IPConflict.htm?opendocument&amp;comments#02182010121117PMRHSN6L.htm</link>
</item>
<item>
<title>Switching Issue</title>
<pubDate>Wed, 17 Feb 2010 09:09:27 PM -0400</pubDate>
<dc:creator>David N Schaffer</dc:creator>
<dc:subject>IP Address Conflict on Server</dc:subject>
<description><![CDATA[Reid, thanks for the comments.<br /><br />Switching the server IP isn't much of an option; the numbering scheme is very long in the tooth and it would be hard to change it everywhere.<br /><br />Topography is servers connected to each other by a single switch which connects into the top of the switch stack; user machines connect lower down in the switch stack. I'll have to check where the DHCP connects; that might be a way to control to the timing.]]></description>
<content:encoded><![CDATA[Reid, thanks for the comments.<br /><br />Switching the server IP isn't much of an option; the numbering scheme is very long in the tooth and it would be hard to change it everywhere.<br /><br />Topography is servers connected to each other by a single switch which connects into the top of the switch stack; user machines connect lower down in the switch stack. I'll have to check where the DHCP connects; that might be a way to control to the timing.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/IPConflict.htm?opendocument&amp;comments#02172010090927PMDNS4K2.htm</link>
</item>
<item>
<title>Switching Issue</title>
<pubDate>Wed, 17 Feb 2010 07:39:42 PM -0400</pubDate>
<dc:creator>Reid Partlow</dc:creator>
<dc:subject>IP Address Conflict on Server</dc:subject>
<description><![CDATA[Your issue appears to be that your laptop user is poisoning your switch table. Your hopefully not still using a hub, if so, ditch it immediately as hubs don't even have mac / port forward tables. You'll see immediate performance gains. If you are using a switch, you have a couple of options to try:<br /><br />1) Change your server's IP address. Better yet, use a 10.xxx.xxx.xx IP scheme or a 172.16.xxx.xxx and never use a scheme from 192.168.xxx.xxx since they are the home network staples. Now your clients will come in and have an IP address that is nowhere near a similar address of any of your servers / services.<br /><br />2) Move you clients to a switch further away from the servers. Keep your DHCP and Domino servers on a primary switch and connect that to the router (gateway), and your clients on another switch connected to the same router (gateway). The gateway will be forwarding the request to the dhcp server and this may buy you the time you need to get a new ip out to your client without messing up the route tables in your switch.]]></description>
<content:encoded><![CDATA[Your issue appears to be that your laptop user is poisoning your switch table. Your hopefully not still using a hub, if so, ditch it immediately as hubs don't even have mac / port forward tables. You'll see immediate performance gains. If you are using a switch, you have a couple of options to try:<br /><br />1) Change your server's IP address. Better yet, use a 10.xxx.xxx.xx IP scheme or a 172.16.xxx.xxx and never use a scheme from 192.168.xxx.xxx since they are the home network staples. Now your clients will come in and have an IP address that is nowhere near a similar address of any of your servers / services.<br /><br />2) Move you clients to a switch further away from the servers. Keep your DHCP and Domino servers on a primary switch and connect that to the router (gateway), and your clients on another switch connected to the same router (gateway). The gateway will be forwarding the request to the dhcp server and this may buy you the time you need to get a new ip out to your client without messing up the route tables in your switch.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/IPConflict.htm?opendocument&amp;comments#02172010073942PMRHS2SV.htm</link>
</item>
<item>
<title>Thanks, but</title>
<pubDate>Sun, 17 Jan 2010 10:04:57 AM -0500</pubDate>
<dc:creator>David N Schaffer</dc:creator>
<dc:subject>Another Quickr usage dilemma</dc:subject>
<description><![CDATA[Thanks for the comments. I have no doubt that retrieving Quickr attachments on the BB is going to happen quickly. However my post was about a different issue; folks want to work with e-mail attachments on the plane, where they have been traditionally unable to access Quickr either from their laptop or their Blackberry. Until WiFi everywhere happens it's going to be a challenge.]]></description>
<content:encoded><![CDATA[Thanks for the comments. I have no doubt that retrieving Quickr attachments on the BB is going to happen quickly. However my post was about a different issue; folks want to work with e-mail attachments on the plane, where they have been traditionally unable to access Quickr either from their laptop or their Blackberry. Until WiFi everywhere happens it's going to be a challenge.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/airplanes.htm?opendocument&amp;comments#01172010100457AMDNSKPQ.htm</link>
</item>
<item>
<title>Sugegstion perhaps</title>
<pubDate>Thu, 14 Jan 2010 10:18:06 PM -0400</pubDate>
<dc:creator>Keith Brooks</dc:creator>
<dc:subject>Another Quickr usage dilemma</dc:subject>
<description><![CDATA[Yes, one may get a link from site #101 and you only synch 100, it happens.<br /><br />Use mobile connect to access the server directly from the phone would help I believe.]]></description>
<content:encoded><![CDATA[Yes, one may get a link from site #101 and you only synch 100, it happens.<br /><br />Use mobile connect to access the server directly from the phone would help I believe.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/airplanes.htm?opendocument&amp;comments#01142010101806PMRHS5VV.htm</link>
</item>
<item>
<title>Quickr client for blackberry</title>
<pubDate>Thu, 14 Jan 2010 06:05:50 PM -0400</pubDate>
<dc:creator>Scott Joyner</dc:creator>
<dc:subject>Another Quickr usage dilemma</dc:subject>
<description><![CDATA[There was an announcement for a blackberry client for Quickr. { <a href="http://twurl.nl/26y38c " target="_blank" title="Link: twurl.nl/26y38c ">Link</a> } I don't have any other details -hopefully all will be revealed at LS.]]></description>
<content:encoded><![CDATA[There was an announcement for a blackberry client for Quickr. { <a href="http://twurl.nl/26y38c " target="_blank" title="Link: twurl.nl/26y38c ">Link</a> } I don't have any other details -hopefully all will be revealed at LS.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/airplanes.htm?opendocument&amp;comments#01142010060550PMRHSV47.htm</link>
</item>
<item>
<title>Quickr 1.0 for Blackberry?</title>
<pubDate>Thu, 14 Jan 2010 03:50:10 PM -0400</pubDate>
<dc:creator>Oliver Schulze</dc:creator>
<dc:subject>Another Quickr usage dilemma</dc:subject>
<description><![CDATA[I just saw this link on the same page in planetlotus:<br /><br />{ <a href="http://www.ns-tech.com/blog/geldred.nsf/plinks/GELD-7ZNTZT" target="_blank" title="Link: www.ns-tech.com/blog/geldred.nsf/plinks/GELD-7ZNTZT">Link</a> }<br /><br />HTH<br /><br />Oliver<br /><br />{ <a href="http://tinymaillto.com/oliversl" target="_blank" title="Link: tinymaillto.com/oliversl">Link</a> }]]></description>
<content:encoded><![CDATA[I just saw this link on the same page in planetlotus:<br /><br />{ <a href="http://www.ns-tech.com/blog/geldred.nsf/plinks/GELD-7ZNTZT" target="_blank" title="Link: www.ns-tech.com/blog/geldred.nsf/plinks/GELD-7ZNTZT">Link</a> }<br /><br />HTH<br /><br />Oliver<br /><br />{ <a href="http://tinymaillto.com/oliversl" target="_blank" title="Link: tinymaillto.com/oliversl">Link</a> }]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/airplanes.htm?opendocument&amp;comments#14012010155010RHSSFE.htm</link>
</item>
<item>
<title>link</title>
<pubDate>Wed, 6 Jan 2010 12:31:53 PM -0400</pubDate>
<dc:creator>Rob</dc:creator>
<dc:subject>Why won&#8217;t they save to Quickr?</dc:subject>
<description><![CDATA[What if the recipients are both internal and external? You may be fighting a battle that is not worth fighting.]]></description>
<content:encoded><![CDATA[What if the recipients are both internal and external? You may be fighting a battle that is not worth fighting.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/saveandsendlinks.htm?opendocument&amp;comments#01062010123153PMRHSNKG.htm</link>
</item>
<item>
<title>re: Policy and policy</title>
<pubDate>Wed, 6 Jan 2010 09:36:17 AM -0400</pubDate>
<dc:creator>David N Schaffer</dc:creator>
<dc:subject>Why won&#8217;t they save to Quickr?</dc:subject>
<description><![CDATA[Yes. A larger issue than attachment size is recipient. Many (most?) attachments are being sent outside the organization and in most cases we want those sent with the e-mail since the recipient would not have access to our internal Quickr places. Unless there is some way to set the policy to apply to only internal recipients it's not an option in this organization.]]></description>
<content:encoded><![CDATA[Yes. A larger issue than attachment size is recipient. Many (most?) attachments are being sent outside the organization and in most cases we want those sent with the e-mail since the recipient would not have access to our internal Quickr places. Unless there is some way to set the policy to apply to only internal recipients it's not an option in this organization.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/saveandsendlinks.htm?opendocument&amp;comments#01062010093617AMDNSK5S.htm</link>
</item>
<item>
<title>Policy and policy</title>
<pubDate>Wed, 6 Jan 2010 08:55:15 AM -0400</pubDate>
<dc:creator>Jerry Carter</dc:creator>
<dc:subject>Why won&#8217;t they save to Quickr?</dc:subject>
<description><![CDATA[It seems then you have the beginnings of a proper Policy in terms of business rules and goals. It may be, for all the reasons noted, and as Kieth suggested, the best way to achieve it is with the proper policy - set it by default. If it's too much load on them to think about document management, no problem - take the decision away and make it the defacto option. <br /><br />What would be really nice is if there was some intelligence in the mail client to have a threshold for this, so only the large files default to being moved to Quickr and every day email attachments do not.]]></description>
<content:encoded><![CDATA[It seems then you have the beginnings of a proper Policy in terms of business rules and goals. It may be, for all the reasons noted, and as Kieth suggested, the best way to achieve it is with the proper policy - set it by default. If it's too much load on them to think about document management, no problem - take the decision away and make it the defacto option. <br /><br />What would be really nice is if there was some intelligence in the mail client to have a threshold for this, so only the large files default to being moved to Quickr and every day email attachments do not.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/saveandsendlinks.htm?opendocument&amp;comments#01062010085515AMRHSJC4.htm</link>
</item>
<item>
<title>Thanks for the comments</title>
<pubDate>Tue, 5 Jan 2010 11:21:52 PM -0400</pubDate>
<dc:creator>David N Schaffer</dc:creator>
<dc:subject>Why won&#8217;t they save to Quickr?</dc:subject>
<description><![CDATA[We do use DAOS. The back-end concerns are less with saving disk space on the server than with minimizing database sizes and bandwidth used by local replicas on the consultants' laptops.<br /><br />We're also trying to get everyone to use Quickr for document management. To the extent that we can capture documents into Quickr up front we minimize document management issues.<br /><br />The issue seems to be that, for most users, the benefits of using Quickr accrue to the entire organization but the effort (minimal to my way of thinking) falls on the individual who is tasked with helping his client or selling projects, not with document management. There are, of course, benefits to the individual user -- protection against potential data loss when "My Documents" is used instead of Quickr, searchability, documents are available to support staff or colleagues without having to e-mail them, faster replication, etc. But they're not intuitive or compelling to most non-technical users.]]></description>
<content:encoded><![CDATA[We do use DAOS. The back-end concerns are less with saving disk space on the server than with minimizing database sizes and bandwidth used by local replicas on the consultants' laptops.<br /><br />We're also trying to get everyone to use Quickr for document management. To the extent that we can capture documents into Quickr up front we minimize document management issues.<br /><br />The issue seems to be that, for most users, the benefits of using Quickr accrue to the entire organization but the effort (minimal to my way of thinking) falls on the individual who is tasked with helping his client or selling projects, not with document management. There are, of course, benefits to the individual user -- protection against potential data loss when "My Documents" is used instead of Quickr, searchability, documents are available to support staff or colleagues without having to e-mail them, faster replication, etc. But they're not intuitive or compelling to most non-technical users.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/saveandsendlinks.htm?opendocument&amp;comments#01052010112152PMDNS75S.htm</link>
</item>
<item>
<title>There must be a cost or a benefit</title>
<pubDate>Tue, 5 Jan 2010 05:57:31 PM -0400</pubDate>
<dc:creator>Scott Joyner</dc:creator>
<dc:subject>Why won&#8217;t they save to Quickr?</dc:subject>
<description><![CDATA[I agree with Daniel. The only way to change behavior is to exact a cost or provide a benefit. In this case, perhaps you could enforce more strict mail quotas which would encourage people to be more judicious in sending huge files to others. <br /><br />When your boss screams at you for sending a 14MB powerpoint file that blows his quota, then the cost becomes clear.]]></description>
<content:encoded><![CDATA[I agree with Daniel. The only way to change behavior is to exact a cost or provide a benefit. In this case, perhaps you could enforce more strict mail quotas which would encourage people to be more judicious in sending huge files to others. <br /><br />When your boss screams at you for sending a 14MB powerpoint file that blows his quota, then the cost becomes clear.]]></content:encoded>
<link>http://bloginprogress.us/blog/BlogInPr.nsf/dx/saveandsendlinks.htm?opendocument&amp;comments#01052010055731PMRHSUWZ.htm</link>
</item>

</channel></rss>
