So you want to do this?
IPC ----(192.168.1.X)------ Domain Box -------- ( 10.150.X.X) ^ | ^_______________________| Performing Add client on IPC and entering the Domain Box's IP works OK? Then most likely something in the routing table is not correct What happens if you ping 192.168.1.7 from DOmain box? How about tracert 192.168.1.7 from domain box? Finally, what is the output of route print --Angelo On 5/18/05, Sean Brace <[EMAIL PROTECTED]> wrote: > Maybe someone can help me... > > > > I have a PC that has two NICs in it. NIC1 is connected to our company > domain. NIC2 is connected to another network that includes a PC and some > other industrial I/O equipment. > > > > NIC1 IP info is... IP 10.150.20.0/255.255.0.0 - Default Gateway 10.150.2.1 > > NIC2 IP info is... IP 192.168.1.0/255.255.0.0 - No Default Gateway > > > > I cannot VNC to the PC on the industrial network by using VNC Viewer on the > Domain PC. I can set the Domain PC to VNC Viewer Listener mode and then > "add a client" on the Industrial PC, this works fine. > > > > The Industrial PC IP info is... IP 192.168.1.7/255.255.0.0 - Default Gateway > 192.168.1.0 > > > > The two PC's can "see" each other on the network and we can browse between > them. > > > > The only protocol being used is TCP/IP. We have the Industrial PC in the > host file of the Domain PC. > > > > I've tried using the machine name and the IP address to connect. > > > > Anyone have any ideas? > > > > Thanks, > > > > Sean Brace > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
