March 28, 2024, 02:05:07 PM

Author Topic: Connection Error occured - Error 1208 (resolved)  (Read 22437 times)

Omni

  • Member
  • *
  • Posts: 1
Connection Error occured - Error 1208 (resolved)
« on: May 27, 2010, 07:28:50 AM »
Running the trial edition of NEWT Pro 2.5 on a Windows 2003 SBS server and recieving \"Connection Error occurred (Error 1208: An extended error has occurred.)

Any idea\'s, help or suggestions. Scan completes on the SBS server but fails on the PC\'s that are part of the same domain.

Thanks

Komodo Support

  • Administrator
  • Member
  • *****
  • Posts: 2702
  • Dayton, Ohio, USA
Connection Error occured - Error 1208 (resolved)
« Reply #1 on: May 30, 2010, 06:38:46 AM »
Hello there.  We sincerely apologize for the delay.  We usually respond multiple times a day, and at least once a day depending on the time zone.

As for this very strange error.. what happens if you just try to visit one of those PCs from Windows Explorer or IE, as in \"\\\\ThePCName\" (no quotes), from that SBS Server?

OlivierH

  • Member
  • *
  • Posts: 14
Connection Error occured - Error 1208 (resolved)
« Reply #2 on: September 14, 2010, 06:40:59 AM »
Any update on this issue. I am also suddenly receiving this message on all my servers. It worked fine about a week ago.
Error 1208: An extended error has occurred. Making a UNC connection to the server works fine.

Komodo Support

  • Administrator
  • Member
  • *****
  • Posts: 2702
  • Dayton, Ohio, USA
Connection Error occured - Error 1208 (resolved)
« Reply #3 on: September 14, 2010, 06:21:30 PM »
Hello again.  Can you right-click on the error there under the \"Scan Status\" column and paste the error here so we can see it exactly as it appears?  That may help.

OlivierH

  • Member
  • *
  • Posts: 14
Connection Error occured - Error 1208 (resolved)
« Reply #4 on: September 15, 2010, 04:33:35 AM »
Hi. Here you go:

Connection error occurred (Error 1208: An extended error has occurred.) -> Hint: Try visiting \"\\\\AFCPT1SUPP1\" from Windows Explorer or IE.


Visiting \\\\afcpt1supp1 works fine.

Komodo Support

  • Administrator
  • Member
  • *****
  • Posts: 2702
  • Dayton, Ohio, USA
Connection Error occured - Error 1208 (resolved)
« Reply #5 on: September 15, 2010, 06:15:18 PM »
Are you entering credentials into NEWT\'s Credential Manager?  You can check this by right-clicking on a machine and choosing \"Credential Manager\".  And, are you logged onto the domain with a user that\'s part of the Domain Admin group?

OlivierH

  • Member
  • *
  • Posts: 14
Connection Error occured - Error 1208 (resolved)
« Reply #6 on: September 16, 2010, 05:03:43 AM »
I have an account in credential manager that is a server operator on the servers. This has worked up until this week.

Komodo Support

  • Administrator
  • Member
  • *****
  • Posts: 2702
  • Dayton, Ohio, USA
Connection Error occured - Error 1208 (resolved)
« Reply #7 on: September 16, 2010, 07:18:39 PM »
That\'s very interesting.  I should have asked before, but when you visit \"\\\\afcpt1supp1\" in Windows Explorer, does it prompt you to enter credentials?  If not, what happens if you remove the credentials in NEWT and try to scan?

OlivierH

  • Member
  • *
  • Posts: 14
Connection Error occured - Error 1208 (resolved)
« Reply #8 on: September 27, 2010, 12:04:43 PM »
No difference. With or without credentails I get the same message. Visiting the server \\\\afcpt1supp1 from Explorer goes through fine. Does not ask for credentials.

Komodo Support

  • Administrator
  • Member
  • *****
  • Posts: 2702
  • Dayton, Ohio, USA
Connection Error occured - Error 1208 (resolved)
« Reply #9 on: September 27, 2010, 11:21:57 PM »
Before we continue, we just want to make sure.  Can you also get to \\\\afcpt1supp1\\ADMIN$ in Explorer without Windows asking for credentials?

Also, under NEWT\'s Preferences, do you have \"Use IP Address instead of Machine Name\" enabled (checked)?

Komodo Support

  • Administrator
  • Member
  • *****
  • Posts: 2702
  • Dayton, Ohio, USA
Connection Error occured - Error 1208 (resolved)
« Reply #10 on: September 29, 2010, 01:41:16 AM »
I wanted to let you know we\'ve just emailed you with a link to a new build to try.  It should give us a little more info about this mysterious error.

Komodo Support

  • Administrator
  • Member
  • *****
  • Posts: 2702
  • Dayton, Ohio, USA
Connection Error occured - Error 1208 (resolved)
« Reply #11 on: October 12, 2010, 05:58:22 PM »
Just to let everyone know.  It turns out this is a \"network specific\" error.   In build 170 we added an additional check to give the user a better explanation of the error.  With this new build, Olivier was able to track down his issue to an account with an expired password and corrected it on his end.

Thank you for helping us with this Olivier!