Why Does the TCP Connection Fail Even If the Server and Client Both Initiate a TCP Connection?

I have some devices where I have to hold the reset for 20 seconds. So try holding it longer. And make sure the print server is powered up when you do it.

Can you PING the L230 device from the server? In other words, are you confident there is a clear IP path from server to device? Also, if you're running on XP, turn off the XP firewall as a test. If that works and you still want to run with the firewall on, then you'll need to specify specific ports to be opened up on your firewall or your domain's firewall policy. Those ports, as listed from NComputing's website are:
Port Exceptions

• For L-series device connection
  • TCP: 27605, 27615, 3581, 3597, 3645, 3646
  • UDP: 1027, 1283, 3581
• For vSpace registration
  • TCP Port 3630
  • Point to:
    • register.ncomputing.com
    • or 85.214.107.229
• For vSpace Update
  • TCP Ports 20 & 21
  • Point to:
    • 70.182.176.102
    • or 81.169.173.128
    • or 81.169.173.128
    
    

Hi there,
Enabling DHCP at the Client To enable the Windows NT DHCP client, you must log on as administrator at the Windows NT client.

Normally, you enable DHCP as part of the installation procedure for Microsoft TCP/IP, however, you can use this procedure if you have manually configured TCP/IP:

1. Run Control Panel and choose Network.
   
   The Network Settings dialog box appears.
2. Under Installed Network Software, select TCP/IP Protocol and then choose configure.
   
   The TCP/IP configuration dialog box appears.
3. Select Enable Automatic DHCP Configuration.
   
   A Microsoft (MS) TCP/IP message appears, indicating that the DHCP Protocol attempts to configure the server automatically during system initialization.
4. Choose Yes.
   
   A MS TCP/IP Configuration dialog box appears, displaying current TCP/IP configuration parameters. The IP Address and Subnet Mask boxes are not available (grayed out) and the manually configured values are no longer displayed.
5. Choose OK to return to the Network Settings dialog box.
6. Choose OK again.
7. Shut down and restart the computer.

To enable DHCP on a Windows for Workgroups client if TCP/IP is not installed yet:

1. Use Network Setup to install the MS TCP/IP-32 3.11 protocol.
2. In the MS TCP/IP Configuration dialog box, select the Enable Automatic DHCP Configuration check box, and choose Continue.
3. Restart the computer to initialize TCP/IP using DHCP.

To enable DHCP on a Windows for Workgroups client if TCP/IP is installed:

1. To access the Network Drivers dialog box, run Network Setup.
2. Select Microsoft TCP/IP-32 3.11, and then choose Setup.
3. In the MS TCP/IP Configuration dialog box, select the Enable Automatic DHCP Configuration check box, and choose continue.
   
   A message box appears indicating that the configuration of DHCP overrides any values established locally.
4. Choose Yes.
5. To initialize TCP/IP using DHCP information, restart the computer.

try to disable Vpn client in Network control panel

So you verified ICMP traffic isn't blocked and it appears the servers allow the netBios traffic to pass.

On the client machine, check to make sure the windows print and file sharing is installed and the machine isn't blocking netBios traffic.

Make sure TCP ports 137,139, and 445 are open on the xp machine and any devices in between.

It's acting like the TCP data is being blocked by the client machine.

HTH,
-Aaron

You may be behind a firewall or NAT. You can set an option that you are; if that still does not work, you may need to open some ports on the firewall.
Yahoo! Messenger uses a variety of ports.
Service Ports Chat & Messenger TCP Port 5050: Client Access only Insider/Room Lists TCP Port 80: Client Access only File Transfer TCP Port 80: Server Access.
Your ISP may block this port, as its used for web hosting.
You can change port in Messenger, Preferences, File Transfer. Voice Chat UDP 5000-5010
TCP 5000-5001: Client Access
If UDP Fails, TCP will be used instead, see below. WebCam TCP Port 5100: Client Access Super Webcam TCP Port 5100: Server Access P2P Instant Messages TCP Port 5101: Server Access
PMs between Buddys may not use the Yahoo! Server, but this is not a requirement.

set the timeout longer

Resolutions: 1) if you have firewall, open TCP Port 1723, IP Protocol 47 (GRE). 2) make sure you can reach the VPN server by using ping. Sometimes, poor connection can cause this issue too. 3) You may need to updated firmware on a router or firewall if other OS (win9x/nt/me/w2k) works except XP. 4) The VPN server may not be able to get IP from DHCP for the VPN client. So, you may want to re-configure VPN host networking settings. For XP pro VPN host, go to the Properties of the VPN>Network, check Specify TCP/IP address and Allow calling computer to specify its own IP address, and uncheck Assign TCP/IP addresses automatically using DHCP. 5) Make sure no other secure software blocks your access, for example, if you use Norton secure software, you may need to add the remote client's IP so that the client can access. 6) If your VPN running on a Windows RRAS with NAT enabled, you may want to check the NAT settings. 7) If you can establish the VPN from the desktop at home but not from the laptop. Make sure no security software like Microsoft OneCare software that blocks the GRE.