Re: ConnectComputer error log

David,

Thanks for plugging through this with me. I managed to get past the
ConnectComputer error through a combination of registry edits and using a
different name for the client computer. I am positive there were multiple
demons (not daemons) contributing to my problem, but all I can say for sure
is the final variable was changing the client computer name. I did this
several times early on with no success.

All that said, I did try your suggestions before I broke through
1. I tried KB310570 with no luck. I found it strange that everytime I
reboot the server, the registry entry returned to the original incorrect
value. Something to ponder for another time.
2. The server commands ran successfully and returned expected values.
3. Different clients could logon to the domain.
4. Firewalls were deactivated during my efforts.
5. I never got to try KB244474.

Thanks again for all your assistance!
Ray

"David Copeland [MSFT]" wrote:

> Ray,
>
> Was noticing that in your server's ipconfig output that it's showing a Node
> Type of Unknown. Might want to see if the following kb resolves at least
> that part..
> http://support.microsoft.com/default.aspx?scid=KB;EN-US;310570
>
> On the server from a command prompt run the following
>
> nbtstat -n
> To make sure that the server's netbios names are registered (none show in
> conflict)
>
> net share
> Verify that the expected admin shares exists such as IPC$, C$, Admin$, as
> well as, netlogon, sysvol.
>
> Do you have any clients that are already members of the domain? And they can
> still logon to the domain (verified by logon script running, group policies
> are applied etc)
>
> Do you have any kind of firewall or AV software installed on the client or
> the server?
> Verify that the client is in the same time range (within 5mins) of the
> server including date/time/timezone/am/pm.
>
> Might try the registry key from the following article on both the server and
> the client to force kerberos to use TCP instead of UDP.. If this works, I'd
> be kinda curious about your physical network layout.
>
> http://support.microsoft.com/default.aspx?scid=KB;EN-US;244474
>
> --
>
> Hope that helps,
> David Copeland
> Microsoft Small Business Server Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> SBS Newsgroups:
>
> SBS v4.x: microsoft.public.backoffice.smallbiz
> SBS 2000: microsoft.public.backoffice.smallbiz2000
> SBS 2003: microsoft.public.windows.server.sbs
>
> "raydw00" <raydw00@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:11493F08-D945-47E2-8118-FC5ECDEF884B@xxxxxxxxxxxxxxxx
> > Merv,
> >
> > I can always use an extra straw ;) The client is WinXPPro
> >
> > I was pointed to Brandy's informative and detailed post. I tried her
> > suggestions with no luck, but here are a few interesting points:
> >
> > On her final list of 10 steps:
> > 1. On the Server, I received several warnings when I initiated Domain
> > Controller Security. About six pop-ups all titled "Administrative
> > Template"
> > and starting with the following lines "The following entry in the
> > [strings]
> > section is too long and has been truncated."
> > Each message had different details. (I apologize but the quantity of text
> > is overwhelming for me to type at the moment) Suffice it to say the first
> > message was about DCOM Activation Security Check. Others were about
> > offline
> > files and folders, another on prohibiting "make available offline" option.
> > Needless to say, I find that interesting since the lack of synch for my
> > client's offline folders started my adventure.
> > 2&3. I changed the Network Security option as she directed and ran
> > gpupdate
> > 4&5. Changed the registry items where appropriate on the server
> > 6. client side now, confirmed registry items
> > 7&8. My Domain members were missing. Is that a problem I should be
> > concerned
> > about. Remember at this point my system is still a member of a workgroup.
> > 9&10. No success :-(
> >
> > Any comments or advice you can provide is appreciated.
> >
> > regards,
> > Ray
> >
> >
> >
> > "Merv Porter [SBS-MVP]" wrote:
> >
> >> I guess I'll throw this out as a straw to clutch: Brandy Nee [MSFT] had
> >> some potential fixes for this error in the following post (but it wasn't
> >> clear if they fixed the problem)...
> >>
> >> http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_frm/thread/953d1dbcd12a1232/29ea25ed91534086?lnk=st&q=%22An+error+occurred+when+configuring+networking+settings%22&rnum=2&hl=en#29ea25ed91534086
> >>
> >> BTW... are the client computers WinXP Pro or Win2K Pro?
> >>
> >> --
> >> Merv Porter [SBS MVP]
> >> ===================================
> >> "raydw00" <raydw00@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:0982848B-0EC1-4C38-8074-BD04C614D006@xxxxxxxxxxxxxxxx
> >> > Jeff - Thanks for addressing my questions so quickly.
> >> >
> >> > I ran through the uninstall and re-install as you described. Same
> >> > resulting
> >> > error message.
> >> > "An error occured when configuring networking settings. See your
> >> > network
> >> > administrator."
> >> > I was really hoping this would do it. I appreciate your taking the
> >> > time
> >> > to
> >> > share a few ideas. Please let me know if anything else comes to mind.
> >> >
> >> > Regards, Ray
> >> >
> >> > "Jeff Middleton [SBS-MVP]" wrote:
> >> >
> >> >> The questions you answered are correct, you might not even need the
> >> >> CD.
> >> >>
> >> >> RDP is remote desktop protocol....also known as Terminal Services.
> >> >>
> >> >>
> >> >> "raydw00" <raydw00@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> >> news:FC1F6A8B-437D-40EF-A2A9-3F1E6FA4BF2F@xxxxxxxxxxxxxxxx
> >> >> > Thanks Jeff - I will try this out, but since its my first time I
> >> >> > want
> >> >> > to
> >> >> make
> >> >> > sure I am on-track. A few (basic) questions:
> >> >> >
> >> >> > > 6. Reinstall all the required Network Protocols from above.
> >> >> > Where do I get the Network Protocols to reinstall? WinXPPro CD?
> >> >> >
> >> >> > > 7. Try joining the domain again now.
> >> >> > use http:/server/connectcomputer?
> >> >> >
> >> >> > What is RDP? I will eventually look it up, but right now I am up to
> >> >> > my
> >> >> > eyeballs in workstations. ;-)
> >> >> >
> >> >> > "Jeff Middleton [SBS-MVP]" wrote:
> >> >> >
> >> >> > > Hi,
> >> >> > >
> >> >> > > I've seen this before, but what I've seen may not be what's
> >> >> > > happening
> >> >> here.
> >> >> > >
> >> >> > > The resolution I have found to work is simple and does no harm.
> >> >> > >
> >> >> > > 1. Logon to the workstation locally with an account that has
> >> >> Administrator
> >> >> > > rights.
> >> >> > > 2. Ensure that you have a local user account with Administrator
> >> >> > > rights
> >> >> and
> >> >> > > the password to go with it.
> >> >> > > 3. In the Network Properties for the NIC(s), uninstall all
> >> >> > > protocols
> >> >> > > and
> >> >> > > services, namely Client for Microsoft Networks and Microsoft File
> >> >> > > and
> >> >> > > Printer Sharing. Leave only TCP/IP installed.
> >> >> > > 4. Reboot the computer.
> >> >> > > 5. Logon again as a local Administrator
> >> >> > > 6. Reinstall all the required Network Protocols from above.
> >> >> > > 7. Try joining the domain again now.
> >> >> > >
> >> >> > >
> >> >> > > Note, this will also work in a remote troubleshoot scenario if you
> >> >> > > are
> >> >> > > off-site and connecting to the SBS in order to gain access to the
> >> >> > > RDP
> >> >> > > session to the workstation, simply because RDP doesn't require
> >> >> > > those
> >> >> other
> >> >> > > protocols, only the TCP/IP.
> >> >> > >
> >> >> > > - Jeff Middleton SBS-MVP
> >> >> > > YCST@xxxxxxxxxxxxxxxx
> >> >> > >
> >> >> > >
> >> >> > > "raydw00" <raydw00@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> >> > > news:0F264952-03B6-4A27-8F71-A0E93AE0FB25@xxxxxxxxxxxxxxxx
> >> >> > > > Hi,
> >> >> > > >
> >> >> > > > I am using http://servername/connectcomputer to add a client to
> >> >> > > > my
> >> >> SBS2003
> >> >> > > > domain. During the process (after I enter the users and pick
> >> >> > > > the
> >> >> computer
> >> >> > > > name), I finish the wizard and a minute later I get an error
> >> >> > > > message.
> >> >> "An
> >> >> > > > error occured when confirguring networking settings. See your
> >> >> > > > network
> >> >> > > > administrator."
> >> >> > > >
> >> >> > > > Where would I find this error log? on the client? on the server?
> >> >> > > >
> >> >> > > > Any ideas what is happening here? I checked the DNS (w/
> >> >> > > > "ipconfig
> >> >> /all"
> >> >> > > > command) and it is pointing to the SBS server.
> >> >> > > >
> >> >> > > > Thanks in advance,
> >> >> > > > Ray
> >> >> > >
> >> >> > >
> >> >> > >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • RE: Fax monitor incoming + outgoing calls?
    ... problem between the client computer and the SBS server. ... Client is using the internal IP address of the SBS server as the ... To the folder redirection GPO issue: ...
    (microsoft.public.windows.server.sbs)
  • RE: (Very) Slow browsing server shares - Net Work Monitor shows ca
    ... If this issue happen only when browse shared folders on SBS from one XP ... client computer, this will be a client side error. ... click to check the "Hide All Microsoft Services" ... Digitally sign communications (if server ...
    (microsoft.public.windows.server.sbs)
  • RE: No Client or Server Desktop Access Through RWW SBS 2003 SP2
    ... internal client Remote Desktop via RWW. ... Please perform the steps on the SBS and internal client computers: ... Click Remote tab, tick Enable Remote Desktop on this computer ... On the SBS server, click Start, click Run, type "regedit" (without the ...
    (microsoft.public.windows.server.sbs)
  • RE: trouble with shared fax service
    ... Thank you for posting in SBS newsgroup. ... install fax service on client computers. ... the SBS server or on the client workstation. ... and then choose 'Install' for the 'Fax Services' item. ...
    (microsoft.public.windows.server.sbs)
  • Re: Small Biz Design
    ... After we installed SBS 2003 successfully on the server box, the Client ... >When we setup SBS 2003 server using installation disks, ...
    (microsoft.public.windows.server.sbs)
Quantcast