The teamviewer killer has arrived?

[fincoder]

even just through my own Cat 6 GBit LAN the lag was noticeable

I assume all traffic goes over WAN to microsoft servers, even if connecting to another computer on the local LAN.

 

[britechguy]

I assume all traffic goes over WAN to microsoft servers, even if connecting to another computer on the local LAN.

You can only get as much flow as the smallest, or most congested, pipe will allow. As soon as anything goes off one's own network there could be myriad monkey wrenches that end up thrown into the works.

 

[Mick]

I assume all traffic goes over WAN to microsoft servers, even if connecting to another computer on the local LAN.

Good point. Without doing a lot of Wireshark- type fiddling, I don't know the answer to that but it seems likely. It didn't make QA unusable, so it's a minor quibble at best.

 

[glennd]

Ultraviewer will probably go pay when they get their base built up. Thats fine. Ill be there to swoop up a lifetime license if they offer it. However, I do need the linux support and that may come in time along with MAC.

If the program goes open source then it will be around for a long time and will really improve since many will be working on it to improve it. However, The backend server portion would need to be handled. What would be really cool is that if they could release some version that you run on your server to handle all the backend stuff. Then you do not need to depend on some server to hand out ID's and such.

I am going to start using it and slowly work it into my fold of software even though it does not do linux at this time. I think they are just gearing up with it as the website gives me the impression that they took it over and have not updated things yet.

I've been playing with it this week and it's been mostly fine. Today I can't get a remote connection or when it does, it drops out almost immediately.

 

[coffee]

I've been playing with it this week and it's been mostly fine. Today I can't get a remote connection or when it does, it drops out almost immediately.

Not that its your situation but I imagine alot more people are on the internet then normal.
Ive had TV do weird things and I have to reconnect. Things like not being able to remotely click on any desktop icons or bring up a menu. I just have to disconnect and reconnect.

Ultraviewer seems really similar in looks to TV. I wonder if they are using the same code somehow and just modifying it.

 

[glennd]

Not that its your situation but I imagine alot more people are on the internet then normal.
Ive had TV do weird things and I have to reconnect. Things like not being able to remotely click on any desktop icons or bring up a menu. I just have to disconnect and reconnect.

Ultraviewer seems really similar in looks to TV. I wonder if they are using the same code somehow and just modifying it.

You might be right. I'm getting long ping times to ultraviewer.net of 250ms - 450ms. I'm not sure how this technology works but I would have thought once the connection is made, it's just traffic directly between the two computers in question.

 

[coffee]

You might be right. I'm getting long ping times to ultraviewer.net of 250ms - 450ms. I'm not sure how this technology works but I would have thought once the connection is made, it's just traffic directly between the two computers in question.

For shits and grins, Change your DNS and see if you get any improvement.

 

[glennd]

For shits and grins, Change your DNS and see if you get any improvement.

no change. because ping looks up the dns once then pings the ip address. the dns lookup doesn't factor into the ping times.

 

[coffee]

no change. because ping looks up the dns once then pings the ip address. the dns lookup doesn't factor into the ping times.

really? Clear out your DNS setting and then run:

ping www.yahoo.com

Update: Oops, I kinda read that wrong. Sorry. Yes, After the initial DNS lookup, Ping will then use the ipaddress.

If you have high ping rates then its most likely network congestion IMHO. I would try and narrow it down with a traceroute.

 

[SAFCasper]

no change. because ping looks up the dns once then pings the ip address. the dns lookup doesn't factor into the ping times.

You clearly are not familiar with the great DNS Haiku.

 

[glennd]

I tested it again today. The ping times are around 260ms but the connection is now fast and stable. Go figure...

 

[glennd]

I was also testing the file transfer yesterday which crashed Ultraviewer and dropped the connection. Today it's working.

Did you know it can do file transfers?