Disconnect Code 2308

Ada Green

unread,

Jun 5, 2002, 5:14:45 PM6/5/02

to

I've had reports of users disconnecting from their
Terminal Server sessions so I embedded a bit of code in
the connect.asp page to generate error codes so that I may
know where to begin troubleshooting.
I finally got a report of a disconnected session with
disconnect code 2308. According to technet, the reason for
disconnection is Socket Closed.

I've searched the Internet and have had little luck in
trying to find some resolution to this. I've increased my
idle timeout for TS sessions to 3 hours.

Has anyone ever had anything like this before?

Any help would is greatly appreciated.

Ada Green

Ryan Basile [MS]

unread,

Jun 5, 2002, 6:05:58 PM6/5/02

to

Ada,

2308 is a socket closed error. For a list of disconnect code descriptions
see Q284439.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q284439

--
--
Thank You

--Ryan

--
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Ada Green" <avg...@rcnchicago.com> wrote in message
news:b93101c20cd6$04282670$19ef2ecf@tkmsftngxa01...

Ada Green

unread,

Jun 6, 2002, 9:59:35 AM6/6/02

to

That's right.
I'm trying to find a resolution for this. Based on my
findings, the workstation ceased to respond to the server,
causing a lost session. i was able to replicate this by
disconnecting my network cable from my computer while in a
TS session over IE.
I also received reports of the same error this morning for
these remote locations and a new one: 516 WinSock socket
connect failed.
I'm trying to rule out whether or it's something on our
end or the client's end before addressing this issue with
the client. I think it's them because they tend to
experience network problems from time to time which
includes slow internet access.
Is there a way to solve this issue better diagnose?

Thanks again,

ada green

>.
>

Ryan Basile [MS]

unread,

Jun 6, 2002, 1:20:00 PM6/6/02

to

Can you take the middle man out of the network loop for a test? Use the
client on the same local network as the server.

--
--
Thank You

--Ryan

--
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Ada Green" <avg...@rcnchicago.com> wrote in message

news:c21e01c20d62$63d86f80$39ef2ecf@TKMSFTNGXA08...

Ryan Basile [MS]

unread,

Jun 6, 2002, 1:51:09 PM6/6/02

to

Ada,

Also, It's not clear from this mail if you are running TSAC1.0 or the XP
client.

Try using the XP client. It will in many cases give a more detailed error
message that can help diagnose the problem.

--
--
Thank You

--Ryan

--
This posting is provided "AS IS" with no warranties, and confers no rights.
--

"Ryan Basile [MS]" <rya...@online.microsoft.com> wrote in message
news:u#HdJ5XDCHA.1880@tkmsftngp04...

Ada Green

unread,

Jun 6, 2002, 2:23:43 PM6/6/02

to

We are using TS advanced client on Windows 2000 Advanced
Server.
I called MS this morning and was told those specific
disconnect codes had to do with firewall configurations
that had timeout disconnects.
I forwarded all my findings to the client who then came
back and confirmed that their firewalls were set to
disconnect after 60 minutes.
They need to make a change on their end and we're going to
monitor and see how everything goes...

>.
>

Ryan Basile [MS]

unread,

Jun 6, 2002, 2:39:38 PM6/6/02

to

Great. Please post your resolution if everything works out!

--
--
Thank You

--Ryan

--
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Ada Green" <avg...@rcnchicago.com> wrote in message

news:add001c20d87$4a499ec0$36ef2ecf@tkmsftngxa12...

Ada Green

unread,

Jun 6, 2002, 2:52:54 PM6/6/02

to

Will do; check back in a few days.

>> >> > >> I've had reports of uÍ{ wÀ Z oÔ?FÔ? FÌ£^
ìô sers disconnecting from their