"Error: The TCP/IP connection was unexpectedly terminated by the server"

Discussion in 'Windows Small Business Server' started by Tim \(Newsgroups\), May 3, 2005.

  1. I've just rebuilt a workstation (connected to SBS2003 Premium - ISA2000)
    following a hardware upgrade.

    I'm trying to set up a connection to msnews.microsoft.com but when I try to
    pick up messages I get the error in the subject line.

    Account: msnews.microsoft.com

    Server: msnews.microsoft.com

    Protocol: NNTP

    Port: 119

    Secure(SSL): 0

    Code: 800ccc0f

    I have no problem connecting to Newsgroups from other workstation in the SBS
    domain so I'm thinking it's down to this workstations configuration (I built
    it from scratch, added XP SP2, added Office 2003 SP1, antivirus etc THEN ran
    http://servername/connectcomputer). All the others had SP2 added AFTER they
    became domain members)

    Anyone any ideas??

    Kind Regards

    Tim
     
    Tim \(Newsgroups\), May 3, 2005
    #1
    1. Advertisements

  2. Do you have the firewall client running on the workstation?
     
    Robbie Niblock, May 3, 2005
    #2
    1. Advertisements

  3. Tim \(Newsgroups\)

    Mal Osborne Guest

    Try the following:

    1. Ping the news server from the broken & a "known good" client. Same IP
    resolved?

    2. At a command prompt type "TELNET msnews.microsoft.com 119" This should
    connect you directly to the news server, and give you a welcome message,
    starting with the string "200". Type "LIST" and you should see a list of
    all the newsgroups on that server.

    Post back some results

    Mal Osborne
    MCSE MVP Mensa
     
    Mal Osborne, May 3, 2005
    #3
  4. Yes

    However.....after logging on it often moves to "ISA server not configured".
    After forcing a refresh.....it reverts to the more usual "Configured to use
    servername"
     
    Tim \(Newsgroups\), May 4, 2005
    #4
  5. Hi Mal

    Thanks for helping me out here:)

    1) Same IP resolved 207.46.248.16
    2) The telnet command worked as expected with the good workstation, but
    didn't manage to connect at all on the "dodgy" client. The command just
    hangs and then returns to the C:\

    Could this be the Windows Firewall (since I joined this machine to the SBS
    domain after installing XP SP2)?

    Thanks

    Tim
     
    Tim \(Newsgroups\), May 4, 2005
    #5
  6. Hi Mal

    Thanks for helping me out here:)

    1) Same IP resolved 207.46.248.16
    2) The telnet command worked as expected with the good workstation, but
    didn't manage to connect at all on the "dodgy" client. The command just
    hangs and then returns to the C:\

    Could this be the Windows Firewall (since I joined this machine to the SBS
    domain after installing XP SP2)?

    Thanks

    Tim
     
    Tim \(Newsgroups\), May 4, 2005
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads
There are no similar threads yet.
Loading...