I purchased a NexLand ISB Pro 800 Turbo after reading some really nice reviews and hearing how good their supoprt is
All I can say is I have had nothing but problems with this router since day 1 I spoke to 1 tech who gave 100% effort and appologized for not being able to resolve the issue and had to bump the problem up the support line. After that zilch, zero, kaput.
Nexland completly dropped the ball even after multiple attempts to contact them over the last 2 weeks.
Guess I have to play the part of 1 very upset customer and call them again.
And no I am not running some weird far off configuration. My UGate-3200 has been flawless since day 1 and has not stopped being so for well over 1 year.
Sorry to hear about it, were you the one having SMTP issues?
I'd go for repeated calls....don't let it slide. I've only needed support once on a Nexland router, was fine for me. Got good feedback from the company otherwise over a year ago when dealing with management over trying to become a reseller.
Where are you in CT?
MORNING WOOD Lumber Company
Guinness for Strength!!!
Well I finaly received an e-mail from NexLand after I e-mailed everyone and anyone. Figured someone might pay attention and it is from the guy who I contacted originaly who was the next level of support. Claims he did not receive an e-mail nor knew I was still having problems.
Anyways, yes my issue is SMTP related. Behind the NexLand I can not send or receive any e-mail. I have tried placing the server in the DMZ, virtual server and opening ports. All I need is port 25. All the other ports that I need are working.
NEO960, what firmware are you running? I know for a fact that their latest available for download has a loop back issue which stopped my workstation from being able to view the server.
I have a beta version Z. If your interested e-mail me and I will send it to you. Maybe it fixes some other issues?
Another inersting problem is after a day or 2 the router now lights up like a Christmas tree with all the LEDs on the right side lighting up.
When I connect my PC directly to the cable modem, it runs with no disruptions at all. As soon as I conect the router, things go bad.
I have tried every possible solution as you can see, but nothing seems to work. Can you think of any other reasons why this could happen?
Thanks in advance.
This almost seems like a runt or packet flood of some sort. Maybe a bad NIC? Have you tried to unplug everything and then plug 1 machine in at a time? Then go back and do it again starting with another machine?
Originally posted by Steven This almost seems like a runt or packet flood of some sort. Maybe a bad NIC? Have you tried to unplug everything and then plug 1 machine in at a time? Then go back and do it again starting with another machine?
Yes, I have tried that too. It still happens. I have been fighting with this problem for two months now. Nexland engineers sent me their latest firmware for the old unit (Version 5Y) and it did not work. The new unit that was sent as a replacement has version 5T. I will try the 5Y version on the new unit today. BTW, 5Y is not available on their website. It was sent to me as a special effort to try to fix my particular problem.
If it is a NIC problem, then I am cooked, because my NIC is built into the motherboard on my new PC. The old PC has a PCI ethernet card. But then I cant imagine both ethernet cards on both PCs could have the same problem. But why doesn't it happen when I directly connect my PC to the cable modem?
The word "flood" that you used seems to describe what happens to my router. In layman's terms (I am a layman) It seems to get flooded with junk and chokes. When the power is recycled, it clears up.
Maybe my Karma dictates that I have to live without a router .
Ok, so you have setup your system with the extreme bare essentials not only in terms of software but hardware as well?
Modem, router & Win 2k Pro PC and nothing else attached. Are both systems Win 2kPro? Can you try Win98 or 98se or possibly XP?
I am wondering if it is a rouge setting that is coming up on your install for some odd reason or possibly a driver that is not working correctly with a piece of your hardware.
Dunno, really shooting from the hip with some ideas.
Steven for the life of me it doesn't sound like it the router .I have a nexland turbo also and love it.I have read all your posts and your problem is very odd.It sounds like your only using just one of the WAN port on the router.Have you try to set the router up with both Wan ports ? I run a set up like this: from the modem to a switch (netgear FS105) uplink port.from the switch two cat 6 crossover cable to the two wan ports on the router .Cat6 to all my computers .I pay $9.95 for the second IP .
Other things to look at is the duplex speed of the nic cards ,are they set to auto.When you plug your computers into the router do they show up as 10 t base or 10/100 on the router? Are all the cable cat5e or cat6 lines? Just thing I would look at!
My connection is a ADSL 1.5-6.0mb/384k connection. I have only tried using WAN1 of the NexLand. WAN2 is disabled.
My server is connected via a gigabit fiber and I run a transceiver in to my router. It is a rough life managing datacenters and being a network engineer
I have also tried both ports of the dual 10/100 PCI NIC I put in to the server. My cables are all certified CAT6 factory made and I have placed a network sniffer on the network and see nothing unusual coming from the server.
The server is running RedHat 7.2 There are no specific settings that I know of other then the NIC and DNS that the server gets configured with that would be specific to only the SMTP protocol over port 25. I could try reconfiguring it so SMTP runs on another port but I highly dought that will make any difference.
Yes the NIC on the server is set to auto and show up as 100M when plugged in. The server is also set with a static IP address of .50 The NexLand is set to handle DHCP up to .30 so there is no cross over. I have also made sure only the server and my workstation were the only things plugged in at the time.
I can say unless there is some specific SMTP setting on the server that I am unaware of that it is definatly the NexLand as all other server functions are working perfectly across their respective ports.
22/tcp open ssh
80/tcp open http
443/tcp open https
After e-mailing everyone and anyone at LexLand the guy Mat who was the person I was told to contact by their suport since the issue needed to get elevated, e-mailed me late last week asking me to call him direct. I wont go in to his reply of never getting my e-mail or NexLand support elevating the call to him.
I replied with a lengthy e-mail covering everything that was done so he would have as much information going in to this as possible and telling him I would call Monday.
Monday, I called, left a voice mail with my home number telling him who I was and requested him to call me at home.
Well it is Tuesday night and I have yet to hear anything and based on their history I do not think I will be holding my breath.
Also open a new issue in their active support site and get an issue number, if you haven't done so already. That is how I got them to provide tech support for me.
Hi Steven
I have read all your posts on the NEXLAND and unfortuneately, I have to agree with Bob Carrick, it doesn't seem to be a router problem.
Let me clarify here....I have a Pro400, was hooked up to ADSL with PPPoE, (no problems) changed over to router to Cable connection, still no problems.
May I suggest something...
-press the reset button to bring the Nexland to factory defaults, then setup the Nexland with the defaults (no DMZ, just the PPPoE screen setup, nothing else) and plug in one PC. Then run the tests to get to the Internet and Email. For ADSL (as far as I know) the MAC address is not important....what is important is that the NEXLAND has a specific setting for MTU, (I think this is located in the "Expert Level" screen) which must correspond with the MTU of your NIC card.
Let us know if this works.
A man with a watch knows what time it is. A man with two watches is never sure.
MTU on my server is typical as any PPoE DSL conection and is set at 1490 which is below the MTU for a ADSL connection of 1492. This should have absolutly no bearing on port 25 which is the only port that seems to be having a problem.
Version "Z" of the NexLand BIOS which was given to me by NexLand support due to a loop back issue with their version "T" bios, 2-3 days gives me nothing buyt a Christmas tree on all the LEDs on the right hand side of the router. Pressing the reset button does absolutly nothing. I have to power the router off then on to reset.
As for their online active support, been there done that and still no response I am begining to think I have a nothing more then a $400 purple door stop
I have even configured a way out of scope port 6000 under tcp/ip running a filtered x11 without any problems.
If I was not a seasoned network engineer/managed datacenters for over a decade (specializing in NT, Netware, Linux) I might be hesitant to agree that it is possibly my server or configuration but not only myself but a Linux specialist (who I hired as an independent consultant) has confirmed my setup as being nothing short of perfect and should pose no reason for the Nexland router to have issues. Remember my Maxgate UGate-3200 router is and has worked for well over a year with my current server.
Originally posted by Steven If I was not a seasoned network engineer/managed datacenters for over a decade (specializing in NT, Netware, Linux) I might be hesitant to agree that it is possibly my server or configuration
Sorry Steven, we were not trying to insult your knowledge skill set, or question your expertise...just trying to help, if at all possible.
I do understand your frustration when it doesn't work as it should (I get that way sometimes), and I get peeved.
Bob Carrick has tested these routers (or most of them) and he helped me when I had some user (ME) problems (no flaming intended).
I will use your settings and see if I can duplicate your annomally and maybe Bob can inject his wisdom here also.
I am not implying that NEXLAND is perfect, however, I do find this situation strange.
I will try to look closer into this...thanks
A man with a watch knows what time it is. A man with two watches is never sure.
No, no company is perfect but we know hosting works, there are tones and tones of people who host their own websites, mail servers etc all using Nexland routers. I'm pretty sure it's a simple problem you just don't see.
Originally posted by Bob Carrick Except the MTU in your Nexland is 1472.
My DSL connection's MTU is actualy 1492 which is the maximum MTU recommended for internet PPPoE implementations. This leaves a 8 byte PPoE wrapper.
After testing I had found out that a setting of 1490 seemed to work the best with my current configuration.
I would like to play with this and see if the NexLand is a bit pickier but on top of everything the router died. It powers up but I can not access it any more through the web interface.
Bonus points to NexLand who e-mailed me this morning and is issueing an RMA as they wanted it back anyways.
I'm sorry but your MTU is not 1492 or even 1490. The Nexland does your PPPoE and it has a maximum MTU of 1472. I'm starting to think you haven't looked in your nexland much.
I think you are cunfusing my servers configuration and that of the Nexland settings.
My servers MTU is set at 1490 which is 2 bytes smaller then my ISPs PPoE MTU setting of 1492 as I seem to get better performance this way out of my current configuration.
As long as the servers/PPoE device MTU settings do not exceed that of the ISPs PPoE connection you are fine.
My UGate-3200 has no MTU settings available to it that I am aware of and has not skipped a beat with these server settings.
The NexLand seems to be locked with a maximum MTU of 1472 which makes me wonder why since this is not the maximum supported by PPoE.
Being NEW to this router I admit but when NexLand support links up to the router themselves and can not figure out why all ports except for 25 are working it makes me wonder. What was really even more comfusing was even with the server set at 1490 and the router at its largest support MTU 1472 there was no packet fragmentation coming from the server.
Unfortunatly my router is dead and now I am waiting for a replacement. I think it is a combination of a defective unit as well as mis-matched MTUs. To bad NexLand nor myself thought of that up front but I would have also thought the product such as this would support PPoE's maximum allowable settings as well.
Just because you think PPPoE maximum setting should be 1492 does not mean that it should. Why is EnterNet 1454? Why is Windows XP PPPoE 1480? Why is Nexland 1472? Each of these companies has their idea for which MTU is the best, which one causes the least amount of problems with the most PPPoE connections. Why do you think Linksys has so many friggin PPPoE problems?
Anyway the Max MTU is 1472 and I'm glad they set it at 1472 to start. And yes your PCs MTUs should match that, each one of them.
Originally posted by Bob Carrick Anyway the Max MTU is 1472 and I'm glad they set it at 1472 to start. And yes your PCs MTUs should match that, each one of them.
correct
P4 2.4ghz 512ram XP pro ATI 9600pro
P4 2.0ghz 256ram Win2000 Geforce2 MX 400
P4 1.6ghz 512ram XP Home Geforce4 Ti4200
P3 866mhz 320ram ME & XP pro TNT2
All thru HotBrick 600
P3 1.1ghz 260ram Win2000 laptop
SNET (Southern NewEngland Telephone) who's DSL is now operated by Yahoo has a MTU setting of 1492 on their network for their PPoE customers. Not only does their website specify this but I have spoken to their system's engineers (not normal tech support) to verify their MTU settings.
As long as one's MTU settings are below that of the provider you will be ok. Anything higher will result in packet fragmentation.
So the NexLand MTU of 1472 will work since it is below that of my ISP but it is still not allowing me to utilize the maximum allowed. Although I have no idea what the difference of 20 would/could make.
Originally posted by JackMDS Try between 147x – 149x and see what works best in your system.
Sorry but I miss your point. Nexland currently limits the MTU in their router for pppoe to 1472.
Therefore if he sets his above that all the packets will have to be fragmented.
P4 2.4ghz 512ram XP pro ATI 9600pro
P4 2.0ghz 256ram Win2000 Geforce2 MX 400
P4 1.6ghz 512ram XP Home Geforce4 Ti4200
P3 866mhz 320ram ME & XP pro TNT2
All thru HotBrick 600
P3 1.1ghz 260ram Win2000 laptop
Steve but your MTU is not 1472, you are screweing it up by having your server higher then the MTU on your router, so packets are hitting the router bigger then they are going out after the router. So guess what they are being split and every second one is being dropped. Stop arguing and start listening.
Originally posted by Bob Carrick Steve but your MTU is not 1472, you are screweing it up by having your server higher then the MTU on your router, so packets are hitting the router bigger then they are going out after the router. So guess what they are being split and every second one is being dropped. Stop arguing and start listening.
Bob, based on your post I take it we are agreeing? Sounds like it to me.
P4 2.4ghz 512ram XP pro ATI 9600pro
P4 2.0ghz 256ram Win2000 Geforce2 MX 400
P4 1.6ghz 512ram XP Home Geforce4 Ti4200
P3 866mhz 320ram ME & XP pro TNT2
All thru HotBrick 600
P3 1.1ghz 260ram Win2000 laptop
Originally posted by Bob Carrick Steve but your MTU is not 1472, you are screweing it up by having your server higher then the MTU on your router, so packets are hitting the router bigger then they are going out after the router. So guess what they are being split and every second one is being dropped. Stop arguing and start listening.
I am not arguing, I think you are not understanding or confusing my current configuration which is working vs what I had experienced with my NexLand and what I tried to use as a configuration.
SNET is pretty specific about 1492 as being the correct MTU setting for their network. Under Google look up "snet mtu settings" First hit - http://www.dslreports.com/faq/snet?text=1
See item #2
I do not negate that setting the server at 1472 will undoubtly work with the NexLand but question why no other ports fragmented other then that of 25 since all in and outbound SMTP traffic came to a standstill with the setting. Or why the other ports were working without any fragmentation when all things considered they should have also fragmented. And Why NexLand does not support the higher PPoE supported settings.
I have e-mailed them asking this very same question. If all they say is we have found it to be the best setting for our router that is fine since I will then understand the logic behind it.
Sorry, I am just trying to understand the entire picture as opposed to well it is working so be it.
I spoke to 1 tech who gave 100% effort and appologized for not being able to resolve the issue and had to bump the problem up the support line. After that zilch, zero, kaput. 
and it is from the guy who I contacted originaly who was the next level of support. Claims he did not receive an e-mail nor knew I was still having problems.
