Customer seeks Host input re: ISP NAT issues

I've had an open ticket with NYI.net for 36 hours and counting. I'm not seeking help with that. I am curious, since I've been out of the Internet game for a few years, how many customers you think you lose due to NAT issues, with those customers' ISPs.

I searched here, and found only one thread about this. As it was from Jan '02, I thought I'd ask this. I am surprised. As IPv4 reaches its limits, more and more people (in particular broadband customers) are accessing their accounts from behind a NAT.

From where I sit, I have stupid, obnoxious, tedious little problems which crop up every week because I'm behind a NAT. Like this thing with NYI - all of a sudden I can no longer FTP. Between myself, my local ISP and New York Internet (which is also an ISP, and I'm almost a national ISP) we just can't get around this right now.

See, I can FTP to and from anywhere else no problem. And no other NYI customers are currently having ftp issues. Neither are any other customers of my local ISP having FTP issues. It ends up a 3-way finger-pointing fest.

The easiest thing for me to do, by far, is just switch hosts, but it won't be because of anything NYI.net did wrong. That s**** for everyone.

Questions:

-Isn't this a fairly common issue, and doesn't it cost you lost customers?

-Is there a good troubleshooting KB on any of this that anyone uses?

 

 

 

 

Top