The format of the specified computer name is invalid

When trying to remotely manage a Windows 2000 Server system (member server
in a W2K domain) I get various errors. Connecting to machine in Computer
Management works, some items work and some don't. For example, Services
snap-in works fine, but Event Viewer can not connect:
- if connecting vith a NetBIOS name: The network path not found
- if connecting with FQDN: The format of the specified computer name is
invalid
System name is BCH-SAFIR-SRV (13 characters), FQDN length is 24 chars, no
special characters except '-' in computer name.
Ping works for both short name and FQDN.
Computer name is registered in both DNS and WINS.
NET VIEW \\computername, as well as general file access work. However, there
are problems accessing file shares from a service application running on a
different system (this system computer account has appropriate access rights
on both share and NTFS levels). This service app returns 'access denied'
error. I don't know if it's related to the first problem, or it is something
else.

Any suggestions?
Thanks
Eugene.

OOPS. It was the Remote Registry Service. Somehow it happened to be set to
Manual startup.

"Eugene Kalinin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> When trying to remotely manage a Windows 2000 Server system (member server
> in a W2K domain) I get various errors. Connecting to machine in Computer
> Management works, some items work and some don't. For example, Services
> snap-in works fine, but Event Viewer can not connect:
> - if connecting vith a NetBIOS name: The network path not found
> - if connecting with FQDN: The format of the specified computer name is
> invalid
> System name is BCH-SAFIR-SRV (13 characters), FQDN length is 24 chars, no
> special characters except '-' in computer name.
> Ping works for both short name and FQDN.
> Computer name is registered in both DNS and WINS.
> NET VIEW \\computername, as well as general file access work. However,
there
> are problems accessing file shares from a service application running on a
> different system (this system computer account has appropriate access
rights
> on both share and NTFS levels). This service app returns 'access denied'
> error. I don't know if it's related to the first problem, or it is
something
> else.
>
> Any suggestions?
> Thanks
> Eugene.
>
>

That'll do it.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Eugene Kalinin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> OOPS. It was the Remote Registry Service. Somehow it happened to be set to
> Manual startup.
>
> "Eugene Kalinin" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > When trying to remotely manage a Windows 2000 Server system (member
server
> > in a W2K domain) I get various errors. Connecting to machine in Computer
> > Management works, some items work and some don't. For example, Services
> > snap-in works fine, but Event Viewer can not connect:
> > - if connecting vith a NetBIOS name: The network path not found
> > - if connecting with FQDN: The format of the specified computer name is
> > invalid
> > System name is BCH-SAFIR-SRV (13 characters), FQDN length is 24 chars,
no
> > special characters except '-' in computer name.
> > Ping works for both short name and FQDN.
> > Computer name is registered in both DNS and WINS.
> > NET VIEW \\computername, as well as general file access work. However,
> there
> > are problems accessing file shares from a service application running on
a
> > different system (this system computer account has appropriate access
> rights
> > on both share and NTFS levels). This service app returns 'access denied'
> > error. I don't know if it's related to the first problem, or it is
> something
> > else.
> >
> > Any suggestions?
> > Thanks
> > Eugene.
> >
> >
>
>