I suggest that you use winpcap and windump/ethereal to sniff the traffic on both the machine you are trying to connect to and the machine you are trying to connect from.
It should show you clearly what is going on with the connection. Jordan > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Andrew Rosborough > Sent: Thursday, March 06, 2003 2:59 PM > To: 'Crooked River Consulting'; [EMAIL PROTECTED] > Subject: RE: VNC with Dlink DI-701 router > > > Hi, I have a DI-704P which most likely runs on the same firmware. I had > experienced the same problem as you before, so I decided to look into it > more closely. Make sure your router is rebooted, btw. > > When I tried this I got the following results in my log file. > > <-Snip-> > 06/03/03 17:16:51 Got connection from client 66.123.20.58 > 06/03/03 17:16:51 rfbProcessClientProtocolVersion: client gone > 06/03/03 17:16:51 Client 66.123.20.58 gone > 06/03/03 17:16:51 Statistics: > 06/03/03 17:16:51 framebuffer updates 0, rectangles 0, bytes 0 > <-Snip-> > > 66.123.20.58 is www.gotomyvnc.com. It shows that their method of > connecting works, but vncviewer isn't set up correctly, or something > else is interfering. > > Oddly, my McAfee firewall blocked each attempt but they showed up on > sequential ports that seemed unrelated to vnc. > > Today Source IP Hostname > Event Info > 2003/03/06 17:21:55 myip:63467 (myhostname) 192.168.0.106:2614 Never > Offline > 2003/03/06 17:21:01 myip:63467 (myhostname) 192.168.0.106:2613 > SMNTUBootstrap > 2003/03/06 17:20:27 myip:63467 (myhostname) 192.168.0.106:2612 Qpasa > Agent > 2003/03/06 17:13:45 myip:63427 (myhostname) 192.168.0.106:2591 Maytag > Shuffle > > This is odd because 192.168.0.106 isn't the computer I my virtual server > on, disabling the firewall doesn't help. I'm trying to make connections > to virtual server on 192.168.0.128 which works fine on the LAN. > > This may be a stab in the dark but VNC may NAT (Network Address > Translation). D-Link tech support says this when asked about Nortel > VPN: > > "Note: Nortel Contivity VPN may not work with our routers. Try following > the steps above and disable the Keep Alive feature on your Nortel > Contivity client software. Please contact your IT department with > information regarding your VPN if it can be used with NAT (Network > Address Translation)." > > I hope all of this information can be useful to somebody. All I know is > that a few of us D-Link users can't use vnc outside of our home > networks. > > Andrew Rosborough > http://www.rosborough.net > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Crooked River Consulting > Sent: Thursday, March 06, 2003 5:04 PM > To: VNC List > Subject: VNC with Dlink DI-701 router > > Hello All, > > I have an issue trying to connect with VNC to my home computer. I have > AT&T > Broadband at home, and they have assured me that they are not blocking > any > ports, and claim I can use VNC but won't support me. > > At home I have a NAT address range with a Dlink DI-701 router. I have > enabled a range of ports to be forwarded to my home machine.(5800-5999) > Now > in the Dlink setup it calls it a virtual server, although I can set a > range > of ports, so I believe it is the same as port forwarding. On my home > LAN > VNC works fine. When I go to www.gotomyvnc.com, it shows the following: > > Checking you out at IP address "24.131.xxx.xxx"... > > 24.131.xxx.xxx is accepting connections on Display 0 (TCP port 5900). > > I logon to my dial account and try to connect to: > > 24.131.xxx.xxx:0 > 24.131.xxx.xxx:5900 > > And I get the failed to connect to server. > > I have the VNC Listener and server both launched. > > What gives? > > Thanks in advanced. > > Michael Hager _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
