QUATECH ThinkQ QSE-100D-BA 4 Port RS-232 Serial Server (CHEAP!)

[sdeens]

"sdeens, we'll have to agree to disgree then. You aren't getting what I am saying."

That has nothing to do with it at all, your setup is LOCAL and ours is stricktly remote. apples--oranges

Gary Mull please contact me directly via PM at this forum, and we can debug these "sequence of events" for configuration of it jointly; since it appears you and I are the only two trying to test its remote management capabalities outside the local primary Gateway using unrecognized 3rd party routers.

I will try tech support tomorow to clarify its native remote control functionality, especially with UDP.

 

[Sacarino]

"sdeens, we'll have to agree to disgree then. You aren't getting what I am saying."

That has nothing to do with it at all, your setup is LOCAL and ours is stricktly remote. apples--oranges

I do believe you just proved his point, sir.

I'm going to give this one shot and I'm out.

You seem stuck on this concept of 'marrying' the Quatech hardware to a particular machine, like it was a bluetooth device or something. It's just a box that listens for signals coming in on the ethernet port - it doesn't need to be 'married' to anything to work. All it does it listen for a signal that it understands and respond accordingly - no marriage license required. When you load the drivers on your computer, you're allowing the computer to utilize the hardware by allowing it to send signals the Quatech is looking for - nothing more exotic than that. Think of the Quatech like a web server... because that's really what it is. You don't establish some trusted two-way pairing when you pull up Google, you just send a request that it knows how to answer. This is the same thing, you're just sending a request using their drivers instead of with a browser.

do a hard 30 second HARD reset using the paperclip-pin in the back of QUATECH at the REMOTE location only and do it twice forgood measure until all LEDs flash rapidly and you may lose that original REMOTE negotiation to it.

Perhaps you don't realize it, but what you're doing is a factory reset to defaults... which would explain why you can't reconnect to the box after you 'hard reset' it. Don't take me at my word, check page 15 of the manual where it clearly states "To restore the SDS to the factory default configuration, push in and hold the Reset button."

I am able to connect to my remote serial ports at home from within my corporate environment - that means going out through at least 3 switches and 2 routers just to get to their fiber provider who utilizes a good 3 hops through routers to get me down to my local ISP where I go through yet another router before it make it into my trusty linksys. It works, I promise you... as long as you have your router setup to allow the connections in and your ISP isn't blocking inbound connections on your selected port, then Bob's your uncle. Obviously, you want to create a secure link as Dan has outlined if you're doing this on a more permanent basis.

Good luck.

 

[mdonovan]

:hesaid:

I have not commented because I don't claim to know that much about networking, but calling someones observations "meaningless" is a bit harsh, especially for a new member. Those of us that know and support Dan for many years know he is seldom wrong about network issues and even if he were, doesn't deserve that kind of tone, especially for how hard he works for this community.

If this were open for bets, I'd put all my chips on electron

:rockon:

I would agree 100%. Giving someone an attitude when they are trying very hard to help you does not inspire anyone to help you. Especially when you just sign up to ask, then before you have even posted 10 responses you are already complaining that someone's advice is meaningless. (and especially when you are complaining at the guy that runs this web site and very generously offers his help.)

Matt

 

[jgary]

"sdeens, we'll have to agree to disgree then. You aren't getting what I am saying."

That has nothing to do with it at all, your setup is LOCAL and ours is stricktly remote. apples--oranges

I do believe you just proved his point, sir.

I'm going to give this one shot and I'm out.

You seem stuck on this concept of 'marrying' the Quatech hardware to a particular machine, like it was a bluetooth device or something. It's just a box that listens for signals coming in on the ethernet port - it doesn't need to be 'married' to anything to work. All it does it listen for a signal that it understands and respond accordingly - no marriage license required. When you load the drivers on your computer, you're allowing the computer to utilize the hardware by allowing it to send signals the Quatech is looking for - nothing more exotic than that. Think of the Quatech like a web server... because that's really what it is. You don't establish some trusted two-way pairing when you pull up Google, you just send a request that it knows how to answer. This is the same thing, you're just sending a request using their drivers instead of with a browser.

do a hard 30 second HARD reset using the paperclip-pin in the back of QUATECH at the REMOTE location only and do it twice forgood measure until all LEDs flash rapidly and you may lose that original REMOTE negotiation to it.

Perhaps you don't realize it, but what you're doing is a factory reset to defaults... which would explain why you can't reconnect to the box after you 'hard reset' it. Don't take me at my word, check page 15 of the manual where it clearly states "To restore the SDS to the factory default configuration, push in and hold the Reset button."

I am able to connect to my remote serial ports at home from within my corporate environment - that means going out through at least 3 switches and 2 routers just to get to their fiber provider who utilizes a good 3 hops through routers to get me down to my local ISP where I go through yet another router before it make it into my trusty linksys. It works, I promise you... as long as you have your router setup to allow the connections in and your ISP isn't blocking inbound connections on your selected port, then Bob's your uncle. Obviously, you want to create a secure link as Dan has outlined if you're doing this on a more permanent basis.

Good luck.

You In Fact Do have to Marry a specific Quatech Unit to a PC. I erased the driver for the Quatech on the PC to my remote house, so I used my local Quatech to create a new driver for the PC. Thinking that driver would work for the other remote house machine if I just changed the IP address etc. It would not work so I contacted support, and got the bad news. You have to configure the actual Quatech hardware to to specific PC you will use. You can not simply add the driver and expect it work. I wish I had the note I recieved from tech support, but I erased it I was so pissed that I would have to haul the damn pc back 120 miles up and back to the remote house.

Not sure why we can not connect. We both received the same message, so I don't feel like the lone ranger. I will be interested in what support says. Gary

 

[sdeens]

now you understand why the hard reset is so critical to isolating the remote access problem;

This is an Adminstratative issue and its EXACTLY as I analyzed it.

Its a major administrative problem with these units since they do NOT support true remote RE-configuration and especially after HARD RESETS and keep in mind its NVRAM can be easily damaged by electrical power surges etc...a good power spike or failure and the memory may be erased by "DEFAULT" via firmware trigger...just like in some of those old routers and thus you wont be able to remarry it unless you drive 120 miles back and reinstall drivers etc..and remarry the unit to the orignal local Gateway. Also don't use a DSL provider as your source for the original Gateway. I will explain later.

thus in your case Gary a 120 miles distance and in my case (90 miles) make these units extremely impractical for our purposes..you can still use them remotely, but you have to know in advance what can cause the loss of remote access and the only way to restore it is to return to the orginal local gateway 120 miles away for configuration. that's a major problem that makes long distance remote use of this item impractical.

They did that deliberatly probably as an added security feature...

We are NOT just concerned about seeing it remotely we are also and EQUALLY concerned about its abilty to be RE-configured and modified REMOTELY which in Garys case and mine is extremely vital.

If you go back and read my first post on this matter..I was telling you guys there is a "marriage" involved here and its creates a REMOTE access RE-configuration problem and thus one must the US Postal mail to ship these things around when re-configuration is being tested.

Tech support has confirmed now, EXACTLY what I had diagnosed originally and this may become an administrative problem for anythign that is trying to RUN REMOTE APPLICATIONS thru it that require frequent changes.

thank you Gary, at least someone bothered to contact tech support and get the true lowdown on this thing, rather than just speculating or posting their local observations.

This is why you read the manuals, it warned us in advance about this issue, but is rather vague about it and ONLY warns against power failures and HARD RESETS being the trigger for lost remote RE-configuration access.

Also, if you change your router (new MAC #) or if the DNS host changes the IPs (like DSL IPs are often changed daily) that may become another problem for this thing since it may trigger a new RE-marriage scenario. So if you test one of these things fortotal REMOTE access outside the Gateway, then a real business STATIC IP binding address may become essential..at the server's end at least. Also, If you unplug a ROADRUNNER based cable modem for 30 minutes (this is what TIME WARNER cable uses in our area) it will trigger a new dynamic IP address from their DNS host and thus your router may reject the packet from the remote Quatech. I am going to test that soon.

I have NOT tested that scenario yet, but I would not be surrpised if these things do NOT work well remotely at locations fed FROM a dynamically changing IP enviroment like DSL providers or ROADRUNNER base dynamic DNS hosts that change them after power failures automatically.

 

[electron]

"sdeens, we'll have to agree to disgree then. You aren't getting what I am saying."

That has nothing to do with it at all, your setup is LOCAL and ours is stricktly remote. apples--oranges

I do believe you just proved his point, sir.

I'm going to give this one shot and I'm out.

You seem stuck on this concept of 'marrying' the Quatech hardware to a particular machine, like it was a bluetooth device or something. It's just a box that listens for signals coming in on the ethernet port - it doesn't need to be 'married' to anything to work. All it does it listen for a signal that it understands and respond accordingly - no marriage license required. When you load the drivers on your computer, you're allowing the computer to utilize the hardware by allowing it to send signals the Quatech is looking for - nothing more exotic than that. Think of the Quatech like a web server... because that's really what it is. You don't establish some trusted two-way pairing when you pull up Google, you just send a request that it knows how to answer. This is the same thing, you're just sending a request using their drivers instead of with a browser.

do a hard 30 second HARD reset using the paperclip-pin in the back of QUATECH at the REMOTE location only and do it twice forgood measure until all LEDs flash rapidly and you may lose that original REMOTE negotiation to it.

Perhaps you don't realize it, but what you're doing is a factory reset to defaults... which would explain why you can't reconnect to the box after you 'hard reset' it. Don't take me at my word, check page 15 of the manual where it clearly states "To restore the SDS to the factory default configuration, push in and hold the Reset button."

I am able to connect to my remote serial ports at home from within my corporate environment - that means going out through at least 3 switches and 2 routers just to get to their fiber provider who utilizes a good 3 hops through routers to get me down to my local ISP where I go through yet another router before it make it into my trusty linksys. It works, I promise you... as long as you have your router setup to allow the connections in and your ISP isn't blocking inbound connections on your selected port, then Bob's your uncle. Obviously, you want to create a secure link as Dan has outlined if you're doing this on a more permanent basis.

Good luck.

You In Fact Do have to Marry a specific Quatech Unit to a PC. I erased the driver for the Quatech on the PC to my remote house, so I used my local Quatech to create a new driver for the PC. Thinking that driver would work for the other remote house machine if I just changed the IP address etc. It would not work so I contacted support, and got the bad news. You have to configure the actual Quatech hardware to to specific PC you will use. You can not simply add the driver and expect it work. I wish I had the note I recieved from tech support, but I erased it I was so pissed that I would have to haul the damn pc back 120 miles up and back to the remote house.

Not sure why we can not connect. We both received the same message, so I don't feel like the lone ranger. I will be interested in what support says. Gary

Ok, I really didn't want to post about this anymore, because there are so many issues with these last few posts, but unless I am missing something here (I'm sure 'someone' will confirm I am), you made a mistake. When you removed the drivers, you should NOT have tried to point it to a local unit and change the IP address. Instead, you should have reinstalled these drivers, and use the 'scan remote subnet' feature in order to reconnect the unit (meaning you have to forward the port I mentioned earlier). I have done this plenty of times, and this works just fine. I offered to help you via PM, but you haven't responded, so I can only assume this is a lost cause. I posted this message in order to benefit others.

PS: anyone want to buy 4 defective QSE-100 units?

 

[sic0048]

PS: anyone want to buy 4 defective QSE-100 units?

????

Are you really looking at selling yours?

 

[Steve]

thank you Gary, at least someone bothered to contact tech support and get the true lowdown on this thing, rather than just speculating or posting their local observations.

You know, you may be a great guy, but you post like a true jackass. Instead of criticizing others, why don't you take your own advice and call support yourself? In fact, my best suggestion is to just remove your account and go insult people someplace else. We really don't need this kind of attitude here. It's obvious we are all idiots and can't help you. And I can guarantee with an attitude like you portray nobody here will even attempt to help you with anything in the future.

EDIT: After thinking about this for a while, I just wanted to take a moment to apologize to the community for the very negative tone of this. I have NEVER come down to that level and clearly it was a retaliatory personal attack back at a personal remark about Dan. Even though things like this may not bother Dan, I have too much respect for him to have let this go and it was just too easy to sit back and say nothing. Dan worked tirelessly to build CT into a community of respectful, helpful and knowledgeable people where all kinds of diverse opinions can be shared without personal attacks or insults. Diverse opinions are what makes this country great and move forward. But it was the constant display of negativity, ungratefulness and what at least I perceived as a personal attack toward Dan in this last post that triggered a nerve I guess.

In email and written words like even here on the forums it is sometimes very difficult to convey information without some sort of at least perceived emotion. Sometimes people just write in a style that is misunderstood and if the conversation was held in person with all the eye contact. body language, voice inflection, etc then the whole feeling and meaning may be different.

So, IF these comments were penned in the manner in which they were taken then I stand by my comments but at the same time apologize to the community which I respect. If I am guilty of misunderstanding the comments and the author is just terrible at writing then I apologize to sdeens and invite him to stay but ask that he really review what he writes and do so in a more appreciative and respectful manner.

 

[electron]

PS: anyone want to buy 4 defective QSE-100 units?

????

Are you really looking at selling yours?

Well all my units are doing stuff they aren't supposed to, so I assumed they are defective :hesaid: It was a bad attempt at being funny I guess. I don't think I"ll ever sell them, they are just too useful, especially for that price.

 

[beelzerob]

Ok, I give. HOW do you update the firmware on this thing?? I tried using the driver installer, and it showed no option, and the firmware I downloaded isn't an executable.

How??

 

[electron]

As far as I know, you can only use the web interface to update the firmware. I forgot where exactly in the menu it is hiding, but it's similar to other routers/devices where you click the Browse button and point it to the local firmware file.

 

[intozwave]

New link http://cgi.ebay.com/ws/eBayISAPI.dll?ViewI...em=390100574296 - good thru 10/10

 

[beelzerob]

As far as I know, you can only use the web interface to update the firmware. I forgot where exactly in the menu it is hiding, but it's similar to other routers/devices where you click the Browse button and point it to the local firmware file.

Bingo! Thanks. I hadn't used the web interface yet.

 

[beelzerob]

Well, so far with a Datanab, Yamaha receiver, Ocelot, and ALC lighting, the thing works great!

 

[BraveSirRobbin]

Well, so far with a Datanab, Yamaha receiver, Ocelot, and ALC lighting, the thing works great!

This post got me thinking. It would be great if people could post what devices they had success with interfacing to these units.