Re: [WISPA] Outsourced Server and mail hosting

2014-03-05 Thread Jim Patient
Hey Josh, You were going to check with google back on 10/24/13 to see if they were interested in becoming a WISPA vendor member. Any update on this? Jim From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, March 04, 2014 5:26

Re: [WISPA] Outsourced Server and mail hosting

2014-03-05 Thread Josh Luthman
I talked with Ikano for this. They didn't really come back with an answer so I took it as a No thank you. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Mar 5, 2014 11:33 AM, Jim Patient jpati...@linktechs.net wrote: Hey Josh, You were

Re: [WISPA] Outsourced Server and mail hosting

2014-03-05 Thread Justin Wilson
Talk to Scott LePere at On Ramp Indiana. Justin -- Justin Wilson j...@mtin.net MTCNA ­ CCNA ­ MTCRE ­ MTCWE - COMTRAIN Aol Yahoo IM: j2sw http://www.mtin.net/blog ­ xISP News http://www.zigwireless.com ­ High Speed Internet Options http://www.thebrotherswisp.com ­ The Brothers Wisp From: Josh

Re: [WISPA] Outsourced Server and mail hosting

2014-03-05 Thread Matt
we started when it was in early beta so we are grandfathered into a free account. I think many eons ago I did too but never did much of anything after getting the confirmation email which I cannot find back. Does the free account still have advertising though? as josh pointed out there is an

[WISPA] remote employee

2014-03-05 Thread heith petersen
So, we finally got our former local tech set up at his office at his new home 3 hours away. He has tunnel access into our net, access to billing and his VoIP phone tied to our switch to make and receive calls on our local lines, just like he did when he sat 10 feet from me. So next is to fine

Re: [WISPA] remote employee

2014-03-05 Thread Hass, Douglas A.
If anyone on the list is in a similar situation, we should talk. This area is fraught with serious potential liability. Remember that you can’t simply designate someone as a “contractor,” even if they agree to do it. There are some detailed tests that both the IRS and Department of Labor

Re: [WISPA] remote employee

2014-03-05 Thread Steve Barnes
You need to consider talking to an Employment Lawyer. Consider Doug Haas. Timeclock is a NO NO. You setting his schedule is a NO NO. Contractor = Plumber You hire them for a job. He can bill you by the hour and you can agree on a time but you cannot control his time and you do not provide him

Re: [WISPA] remote employee

2014-03-05 Thread Matt Corcoran
Only 2 options as I understand it: If he is an employee you have to pay the taxes. If he is a private contractor you cannot dictate how he manages his time and conducts His business. You just pay him what he wants for his service to you. (Even if he is a private contractor, he must

Re: [WISPA] remote employee

2014-03-05 Thread Hass, Douglas A.
That’s a good way to look at it, Matt. One additional refinement to what you say below, though--even if your guy does other outside work for other clients, that’s not going to be enough on its own to make him a contractor. A person could be a contractor for some purposes and STILL be

Re: [WISPA] remote employee

2014-03-05 Thread Jim Patient
So in Heiths case, If the guy worked as a contractor on a per job basis for instance you create a helpdesk ticket and assign it to him. Then he works the ticket and puts his time worked on it. Then he sends an invoice to Heith for the time spent on the ticket, would he still be considered an

Re: [WISPA] remote employee

2014-03-05 Thread Hass, Douglas A.
We don’t have enough information to answer the question with only those facts, but someone who is working on a “per job” basis wouldn’t be billing for his time. That isn’t the only factor, but it would be one of the issues the IRS, DOL or a court would consider. The mechanics of actually

Re: [WISPA] remote employee

2014-03-05 Thread heith petersen
Didn’t think I would get into so much trouble, I just want to get as much work out of the guy and pay the least amount as possible. JK. From: heith petersen Sent: Wednesday, March 05, 2014 12:39 PM To: WISPA General List Subject: [WISPA] remote employee So, we finally got our former local

Re: [WISPA] Outsourced Server and mail hosting

2014-03-05 Thread Josh Bowsher
Thanks for all the input guys I really appreciate ittime to compare options and pricing :) Regards, Joshua S. Bowsher Director of Internet Services Midwaynet.net Midway Electronics NWIIS a division of MidwayNet, LLC 1250 N McKinley Ave Rensselaer, IN 47978 Office 219-866-7946 ext: 212 Cell

Re: [WISPA] remote employee

2014-03-05 Thread Justin Wilson
It¹s my understanding that contractors can¹t punch a time clock. Provided you have the legal stuff worked out have him use a ticket system which logs hours. If you don¹t have one fresh books is web based and pretty cheap. You can keep track of projects, open support tickets, bill based upon those

[WISPA] rDNS for customer IPs

2014-03-05 Thread Chris Fabien
Is it customary to provide rDNS for all customer public IP addresses? We just had a complaint of one particular website running very slow, our customer contacted the website owner who said it was because we needed to fix our rDNS. The website acts like it must be doing a rDNS lookup and waiting

Re: [WISPA] rDNS for customer IPs

2014-03-05 Thread Mark Spring
We do a standard reverse record for all ip's so just come up with a generic entry that includes the ip. We ran into this on rare occasions and found this to be standard on our feelers. Mark On Wednesday, March 5, 2014, Chris Fabien ch...@lakenetmi.com wrote: Is it customary to provide rDNS for

Re: [WISPA] remote employee

2014-03-05 Thread Hass, Douglas A.
To clarify, contractors can punch a time clock. There’s no black and white rule against this. The key is WHY are they punching a time clock? For instance, there might be situations where you require the contractor to track hours so you can bill a customer or keep statistics on service calls

Re: [WISPA] remote employee

2014-03-05 Thread Forrest Christian (List Account)
One other to really think about how to make the distinction is this: Are you hiring an individual or a business? If you're paying an individual to do work for you, there's a good chance that they're NOT an independent contractor. If you're paying a business then they probably are. And to

Re: [WISPA] rDNS for customer IPs

2014-03-05 Thread Kristian Hoffmann
It helps to include the word static in the PTR record. At least one RBL uses this as a litmus test for whether or not IPs are static vs. dynamic, and will add your addresses en masse to their dynamic address block lists. That is, if your give static IP addresses. -Kristian On 03/05/2014

Re: [WISPA] remote employee

2014-03-05 Thread Forrest Christian (List Account)
Directly on point for you: http://dlr.sd.gov/ui/publications/independent_vs_employee_fact_sheet.pdf South Dakota Codified Law 61-1-11 states to be considered an independent contractor, a worker must be both free from direction and control and have an independently established business. Since

Re: [WISPA] remote employee

2014-03-05 Thread Clay Stewart
When all of this came into being, the law killing independent contractors in Dec 1986... oh I remember so well... the purpose was to get a lot of missing taxes from people with 'companies' that were not paying taxes, hidden under layers of subcontracting 'contracts'. At the time the law came out I

Re: [WISPA] remote employee

2014-03-05 Thread Hass, Douglas A.
It’s important to note, too, that the DOL’s independent contractor enforcement has shifted from “getting withholding taxes from companies” to “making sure employees aren’t getting screwed out of worker’s comp, Social Security earnings, overtime, and unemployment benefits.” It’s that latter

Re: [WISPA] remote employee

2014-03-05 Thread Clay Stewart
Almost funny: A 1991 Treasury Department study found that tax compliance for technology professionals was among the highest of all self-employed workers and that Section 1706 would raise no additional tax revenue and could possibly result in losses as self-employed workers did not receive as many

Re: [WISPA] remote employee

2014-03-05 Thread Mike Hammett
I'm assuming that's all out the window if you're paying an LLC, Corp, etc. and not an individual? - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: Douglas A. Hass d...@franczek.com To: WISPA General List wireless@wispa.org

Re: [WISPA] remote employee

2014-03-05 Thread Hass, Douglas A.
Unfortunately, no, you can’t assume that. The existence of a business entity is only one of many factors. As I said a little earlier, there’s no magic test. “He has a business. He sends me an invoice from that business. He does other work, too. He’s a contractor.” is probably the most

Re: [WISPA] remote employee

2014-03-05 Thread Sam Tetherow
And to pick on law makers, if you have to already be in the business to be considered a contractor, then how the heck do you get your first client? On 03/05/2014 04:07 PM, Forrest Christian (List Account) wrote: Directly on point for you:

Re: [WISPA] remote employee

2014-03-05 Thread Hass, Douglas A.
Easy! There is no requirement that you have multiple clients in order to be considered a contractor. When I say that there is no magic test to determine who are contractors, it does work both ways. It is certainly possible to be an independent contractor if you have only one client. There is no

[WISPA] finally usage polling

2014-03-05 Thread heith petersen
So, since we finally fired up authentication, I have more toys to play with. I have a rancher, whose spoiled kid sent me an email telling me how crappy my service was, complain again about how slow his speeds are. I pulled up his usage from last month, which we currently do not cap, and he used

Re: [WISPA] rDNS for customer IPs

2014-03-05 Thread Andrew Smith
When you say the website acts like it's doing a RDNS lookup and waiting for a timeout, that sounds like key information. Even if you don't have PTR records for your customer IPs, you should be very quickly returning an NXDOMAIN for those queries. Do these PTR queries from the outside have a