Service Pak 4 and Term Services

[CCS8DENI]

Our business is running 2 remote sites via ISDN accessing
our 2000 business server via Term Services. Since applying
service pack 4 we can't get into the server using terminal
services from the remote sites. All other machines on the
network (at the central site) can be pinged from the
external machine except the 2000 server.


Andrew
andrew.mcmillan@det.nsw.edu.au

Technology Adviser
Dept. of Education and Training
Deniliquin District
New South Wales
Australia

 

[crazylife]

Hi

This does not help you much, but I applied SP4 and now I have a number of users that just can not connect, server busy errors etc, mainly from older O/S such as win 98. However from XP or 2000 there are no errors, before SP4 all was fine!

 

[MattWray]

Can the 2000 server ping the Remote machine? Can the local network access the Terminal Server?

Thanks,

Matt Wray
MCSE, MCSA, MCP, CCNA

http://www.sss-steel.com

 

[ajwright]

A similar thing happened to me the other day, and I'm still trying to resolve it. I used terminal services to apply W2Ksp4 to our proxy server and subsequently lost connectivity to it. It cannot be ping'd by any other system on the network, and not only that, but I cannot access the networking properties at all via the console. When I go into My network places and try to access the properties of the network connection, the app crashes with no error message, the screen flashes and I'm put back to the desktop. An event shows up EVENT ID 1002 Source: Winlogon "The shell stopped unexpectedly and Explorer.exe was restarted." I also show no IP address info when doing an IPCONFIG on this system. I'm really gunshy now about applying any more service packs to our remote servers via terminal services. The service pack has been behaving well up to this point on other servers.