PDA

View Full Version : No Reply Yet again.

ragtim
13-01-2005, 22:00
Ok. I have seen this problem a thousand times, but here are all the details that I can provide.

I recieve the standard No Reply error message when I try to connect to the TS server. I have tried is from my office and I have also tried is from another computer on the LAN. The only way that I have been able to connect is with 127.0.0.1 from the computer I am actually running the server on. I am running the newest client and server.

I have tried the DMZ, Port Forwarding, Virtual Servers, and every combination of the previouls mentioned port related approaches. I have set the client on Debug.

TSclient log
---------------------------------------------------------------
-------------- log started at 13-01-05 15:30 -------------
---------------------------------------------------------------
13-01-05 15:30:57,3544,DEBUG,All,Startup,Client version 2.0.32.60
13-01-05 15:30:57,3544,DEBUG,ProcedureInfo,Client Open,Creating and starting threads
13-01-05 15:30:57,3544,DEBUG,All,TDSoundIn.Open,opend direct Capture 8bit=0 , 11khz=1
13-01-05 15:31:00,3544,DEBUG,ProcedureInfo,Client Open,host 69.91.79.219 resolved to 69.91.79.219
13-01-05 15:31:00,3544,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
13-01-05 15:31:00,3544,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
13-01-05 15:31:03,3544,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
13-01-05 15:31:03,500,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."
13-01-05 15:31:04,3544,DEBUG,All,TMainForm.FormDestroy,FCal lbackSynchronizer.Free done
13-01-05 15:31:04,3544,DEBUG,All,TMainForm.FormDestroy,FSou nd.Free; done
13-01-05 15:31:04,3544,DEBUG,All,TMainForm.FormDestroy,FSou ndNotifications.Free done
13-01-05 15:31:04,3544,DEBUG,All,TMainForm.FormDestroy,FWav eSaver.Free done
13-01-05 15:31:04,3544,DEBUG,All,TClient.Destroy,active FClientReadThread.waitfor
13-01-05 15:31:04,3076,DEBUG,All,TClientReadThread.Execute, leaving
13-01-05 15:31:04,3544,DEBUG,All,TClient.Destroy,active FClientReadThread.freeing
13-01-05 15:31:04,3544,DEBUG,All,TClient.Destroy,active FClientReadThread.Freed
13-01-05 15:31:04,3248,DEBUG,All,TClientWriteThread.Execute ,Close confirmed
13-01-05 15:31:04,3336,DEBUG,All,TClientEventThread.Execute ,Close confirmed
13-01-05 15:31:04,3544,DEBUG,All,TClient.Destroy,active closed buffer
13-01-05 15:31:04,3544,DEBUG,All,TClient.Destroy,active FClientWriteThread.Freed;
13-01-05 15:31:04,3544,DEBUG,All,TClient.Destroy,active FClientEventThread.Freed
13-01-05 15:31:04,3544,DEBUG,All,TClient.Destroy,active destroyed buffer
---------------------------------------------------------------
--------------- log ended at 13-01-05 15:31 --------------
---------------------------------------------------------------


Any ideas?
CheshireCat
13-01-2005, 22:07
Hi RagTim,
Which firewall are you running?
Turn off firewalls, antivirus software, popup stoppers, anti spyware or any other protection. (it's not just firewalls that block sometimes)
Test again then turn each one on in turn to see if any're causing the problem
Post back with success or failure.
guldi
14-01-2005, 08:10
The only way that I have been able to connect is with 127.0.0.1 from the computer I am actually running the server on.
- using the LAN IP of the TS server doesn't work from within the LAN as well ?
- have you read through the "no reply" FAQ thread ?
- Do you run a WLAN ?
ragtim
14-01-2005, 21:51
yes i do run a wireless lan. no i couldn't use the local ip of the computer running the ts server from another computer.


Also, i have disabled all firewalls. Anti-virus and Popup blockers, etc...
guldi
17-01-2005, 09:26
1) wlan's are known to cause timeouts, "especially" as the 32.60'er client is a little bit sensitive to timeouts. As you already have tested the debug mode, I could only suggest trying an older client
Have you checked for a firmware update for your wlan device ?

2) you get a timeout even when using the LAN IP an connecting from the PC the server is running on (or from an other PC within the same LAN) ?
Under normal circumstance this could only be due to a firewall or an extraordinary bad network configuration (bad HW or driver) ? I've never seen nor heard about timeout problems within a LAN (cable connections, no wlan) where firewalls, packet filters,... were excluded :confused:
ragtim
17-01-2005, 23:03
The client is running in a wired office network. The server is on a wireless computer.
ragtim
18-01-2005, 16:56
Ok. I moved my TS server to a computer on the wired LAN and it is still having the same troubles.

The most recent Client log info is below. Also I used Ethereal and I can see the incoming communication from the client and the outgoing commmunication to the Server.

---------------------------------------------------------------
-------------- log started at 18-01-05 10:46 -------------
---------------------------------------------------------------
18-01-05 10:46:19,516,DEBUG,All,Startup,Client version 2.0.32.60
18-01-05 10:46:19,516,DEBUG,ProcedureInfo,Client Open,Creating and starting threads
18-01-05 10:46:20,516,DEBUG,All,TDSoundIn.Open,opend direct Capture 8bit=0 , 11khz=1
18-01-05 10:46:44,516,DEBUG,ProcedureInfo,Client Open,host 69.91.79.219 resolved to 69.91.79.219
18-01-05 10:46:44,516,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
18-01-05 10:46:44,516,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
18-01-05 10:46:47,516,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
18-01-05 10:46:58,516,DEBUG,ProcedureInfo,Client Open,host 69.91.79.219 resolved to 69.91.79.219
18-01-05 10:46:58,516,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
18-01-05 10:46:58,516,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
18-01-05 10:47:02,516,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
18-01-05 10:47:02,1208,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."
18-01-05 10:47:15,516,DEBUG,ProcedureInfo,Client Open,host 69.91.79.219 resolved to 69.91.79.219
18-01-05 10:47:15,516,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
18-01-05 10:47:15,516,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
18-01-05 10:47:18,516,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
18-01-05 10:48:36,516,DEBUG,ProcedureInfo,Client Open,host 69.91.79.219 resolved to 69.91.79.219
18-01-05 10:48:36,516,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
18-01-05 10:48:36,516,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
18-01-05 10:48:39,516,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
18-01-05 10:48:39,1208,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."
18-01-05 10:54:21,516,DEBUG,ProcedureInfo,Client Open,host 69.91.79.219 resolved to 69.91.79.219
18-01-05 10:54:21,516,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
18-01-05 10:54:21,516,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
18-01-05 10:54:24,516,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
18-01-05 10:54:24,1208,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."
xCav8r
18-01-2005, 19:10
Perhaps it would be helpful here to start with the basics.

1. Can you ping the server from the machine you're using for your TS2 client?

2. In Ethereal, what are you seeing going back and forth between server and client? ICMP?

Here's my log with my server turned off:
---------------------------------------------------------------
-------------- log started at 18-01-05 12:39 -------------
---------------------------------------------------------------
18-01-05 12:39:41,2716,DEBUG,All,Startup,Client version 2.0.32.60
18-01-05 12:39:41,2716,DEBUG,ProcedureInfo,Client Open,Creating and starting threads
18-01-05 12:39:42,2716,DEBUG,All,TDSoundIn.Open,opend direct Capture 8bit=0 , 11khz=1
18-01-05 12:39:51,2716,DEBUG,ProcedureInfo,Client Open,host 192.168.2.100 resolved to 192.168.2.100
18-01-05 12:39:51,2716,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
18-01-05 12:39:51,2716,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
18-01-05 12:39:51,3052,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.
18-01-05 12:39:54,2716,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
18-01-05 12:54:10,2716,DEBUG,ProcedureInfo,Client Open,host 192.168.2.100 resolved to 192.168.2.100
18-01-05 12:54:10,2716,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
18-01-05 12:54:10,2716,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
18-01-05 12:54:10,3052,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.
18-01-05 12:54:10,3052,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.
18-01-05 12:54:13,2716,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait

Here's me connecting to a server that's up:
18-01-05 13:03:35,2716,DEBUG,ProcedureInfo,Client Open,host teamspeak.seltecnet.ca resolved to 64.56.159.1
18-01-05 13:03:35,2716,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
18-01-05 13:03:35,2716,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
18-01-05 13:03:35,2716,DEBUG,ProcedureInfo,Client Open,LoginStep2 received
18-01-05 13:03:35,2716,DEBUG,ProcedureInfo,Client Open,Sending LoginStep3

Here's me turning on my XP firewall to block TS:
18-01-05 13:09:08,164,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
18-01-05 13:09:08,164,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
18-01-05 13:09:11,164,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
18-01-05 13:09:24,164,DEBUG,ProcedureInfo,Client Open,host 192.168.2.100 resolved to 192.168.2.100
18-01-05 13:09:24,164,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
18-01-05 13:09:24,164,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
18-01-05 13:09:24,2784,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.
18-01-05 13:09:27,164,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
18-01-05 13:09:27,1912,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."