Connecting to SC kills the network

stalks · Post by **stalks** » 2005-10-16 12:33

I'm having a problem on 2 machines, both fresh installs a week ago, although they both have a similar software setup, hardware wise they are miles apart.

We have Computer A being either of the above mentioned PC's, and Computer B is the one with UltraVNC Viewer in Listen Mode.

A dbl clicks the SC exe and creates a connection to B. B accepts the connection and can immediately see a snapshot of A's desktop. A then immediately loses all connectivity. B's connection with A will timeout. A has effectively had his network card switch off. No connections can be made to local/internet hosts, all existing connections will time out.

The systray icon is unresponsive. As soon as the winvnc.exe and sc.exe processes are force closed connectivity is returned.

This will happen if computer A is either of my home PCs. One is Intel, other is AMD. Both use WinXP SP2, no software firewall. Any ideas?

Ares · Post by **Ares** » 2005-10-16 20:31

Are you using a wireless network somewhere in between the two machines?

-Ares

stalks · Post by **stalks** » 2005-10-16 20:41

No.

Network topology is:

ADSL, 8 IP Block
Zoom x3 ADSL Router, NAT disabled.
Debian Box running iptables with source natting. Amongst other things.
-- 2 network cards, 1 going to router, 1 to a 5-port switch with internal LAN
2 PCs on LAN, the OP issue happens with both.

When the connection is attempted and the PC loses network connectivity, they cant ping the debian box, or the other PC on the switch. Its like the network card just ceases to function. Very strange.

I had Hamachi installed on both machines, plus they both had UltraVNC server running. I uninstalled both peices of software and rebooted, thinking they would be interfering, but it didnt help.

Dwalf · Post by **Dwalf** » 2005-10-16 21:53

stalks wrote: I had Hamachi installed on both machines, plus they both had UltraVNC server running. I uninstalled both peices of software and rebooted, thinking they would be interfering, but it didnt help.

Have you tried a diffrent IP or have run vncviewer on a diffrent port?
sounds like what hapens when you have 2 computers on a network with the same ip, one gets kicked off.

Hope it helps

Dwalf

stalks · Post by **stalks** » 2005-10-16 21:55

Well, the machines that are having the problems are the ones running the SC software. They are initiating an outgoing connection to a waiting vncviewer. I dont think having that viewer run on a different port is going to make any difference.

The machine that is awaiting a connection from one of my machines is outbound on the internet. I am not attempting to connect from one internal machine to another, I have just tried using both to share its desktop with a 3rd party.

redge · Post by **redge** » 2005-10-16 22:02

you need to change the old viewer <=1.0.0 to new vncviewer 1.0.1 would solve the problem
that auto switching codec would kill the network. fixed in the new vncviewer
1.0.1

stalks · Post by **stalks** » 2005-10-16 22:03

I'll double check with the person holding the viewer that he is using version 1.0.1. He only downloaded and installed it today, he may of clicked the wrong link somehow.