Connection Refused - 10061
Roland Sippel
rs "at" kunstbar.tv
Wed Apr 6 15:21:01 2005
I think it is NO problem of the router.
> !!VNC Client connect works AFTER "Add New CLIENT" at VCN-Server!!!
After this i have:
TCP 172.18.1.130:5800 172.18.1.130:5800 Listen
TCP 172.18.1.130:5900 172.18.1.130:5900 Listen
I need no change on router for work.
Roland
John Aldrich schrieb:
> Possibly need to open ports 5800 and 5900 in the router?? I'm guessing your
> router allows outbound connections on any port to have data come back in,
> but you probably don't have ports 5800 and 5900 open on the router. In any
> case, I'm not a big fan of leaving VNC ports open on the router myself. I
> would, personally, recommend using a different port on the outside and
> port-forwarding that to 5800 and 5900 INSIDE the router.... i.e. port 9999
> would forward to 5800 on your win2k box and port 9998 would forward to port
> 5900 on your win2k machine. Another alternative would be set up some sort of
> tunnel, either VPN or SSH or something like that. Just a friendly
> suggestion. :-)
> John
>
> -----Original Message-----
> From: Roland Sippel [mailto:rs "at" kunstbar.tv]
> Sent: Wednesday, April 06, 2005 6:26 AM
> To: vnc-list "at" realvnc.com
> Subject: Connection Refused - 10061
>
>
> I have problems with VNC 4.1.1:
> Connection Refused - 10061, after start W2k Prof. SP4
>
> a) enable as service is active, start automatically at boot
> b) NO Connect possible at Win2k login-Mask
> c) "telnet 172.18.1.121 5900" not work
> d) after Login as Administrator the follow netstat:
>
> Proto Locale Adress Remoteadress Status
> TCP 0.0.0.0:7 0.0.0.0:0 Listen
> TCP 0.0.0.0:9 0.0.0.0:0 Listen
> TCP 0.0.0.0:13 0.0.0.0:0 Listen
> TCP 0.0.0.0:17 0.0.0.0:0 Listen
> TCP 0.0.0.0:19 0.0.0.0:0 Listen
> TCP 0.0.0.0:135 0.0.0.0:0 Listen
> TCP 0.0.0.0:445 0.0.0.0:0 Listen
> TCP 0.0.0.0:1025 0.0.0.0:0 Listen
> TCP 0.0.0.0:1026 0.0.0.0:0 Listen
> TCP 0.0.0.0:5800 0.0.0.0:0 Listen
> TCP 0.0.0.0:5900 0.0.0.0:0 Listen
> TCP 0.0.0.0:18350 0.0.0.0:0 Listen
> TCP 127.0.0.1:1028 127.0.0.1:18350 Waiting
> TCP 172.18.1.121:139 0.0.0.0:0 Listen
> UDP 0.0.0.0:7 *:*
> UDP 0.0.0.0:9 *:*
> UDP 0.0.0.0:13 *:*
> UDP 0.0.0.0:17 *:*
> UDP 0.0.0.0:19 *:*
> UDP 0.0.0.0:445 *:*
> UDP 172.18.1.121:137 *:*
> UDP 172.18.1.121:138 *:*
>
> Ethernetadapter "LAN-Connection":
>
> Verbindungsspezifisches DNS-Suffix:
> Beschreibung. . . . . . . . . . . : NVIDIA nForce MCP Networking Adapter
> DHCP-active. . . . . . . . . .... : NO
> IP-Adress.. . . . . . . . . . . . : 172.18.1.121
> Subnetmask. . . . . . . . . . ... : 255.255.0.0
> Standardgateway . . . . . .. . .. : 172.18.1.1
> DNS-Server. . . . . . . . .. . .. : 145.253.2.11
>
> - Standardgateway: is a WLAN DSL-Router "LINKSYS WRT 54G"
> - VNC-CLIENT is Windows XP Home at WLAN Adress: 172.18.1.130
> - NO Firewall on Server or Client, all ports open
> - ping to 172.18.1.121 works from client
> - VNC-Option Connection: 172.18.0.0/255.255.0.0
>
> !!VNC Client connect works AFTER "Add New CLIENT" at VCN-Server!!!
>
> Any Hints?
> Roland