Re: The machine cannot be found on the network

From: Gregg Miskelly (greggm_at_online.microsoft.com)
Date: 04/27/04 

Date: Tue, 27 Apr 2004 14:43:11 -0700

If you enter the computer name into the Processes dialog (Tools->Debug
Processes), do you get the same error as when you hit F5 on your web app? 

-- 
Gregg Miskelly
http://blogs.msdn.com/greggm
This posting is provided "AS IS", with no warranties, and confers no rights.
"drankin" <donrankin99@hotmail.com> wrote in message
news:OH0oBKILEHA.1144@TK2MSFTNGP12.phx.gbl...
> *sorry if this is a re-post, can't see my reply*
> In response,
> Neither web server (working vs non-working) is behind a firewall.
> I do maintain file share access to both web servers.
>
> Re: DCOM testing, I've used the RPC ping utility (rpingc/rpings) to
> successfully test communication in both directions (workstation to server
>  and server to workstation), and to/from both web servers.
> That said, I am not certain the RPC test definitively proves the
> communication is working.  Perhaps there is some other aspect of
> DCOM for which rpingc does not test.
>
> Any other ideas?
>
> > "Gregg Miskelly" <greggm@online.microsoft.com> wrote in message
> > news:OAQW8JNKEHA.2808@TK2MSFTNGP11.phx.gbl...
> > Is the web server behind a firewall? Can you connect to the web server
via
> > file sharing? It sounds like something is blocking DCOM packets going to
> > your web server.
> >
> > -- 
> > Gregg Miskelly
> > http://blogs.msdn.com/greggm
> >
> > This posting is provided "AS IS", with no warranties, and confers no
> rights.
> > > "drankin" <donrankin99@hotmail.com> wrote in message
> > > news:OhLq9gIKEHA.1040@TK2MSFTNGP10.phx.gbl...
> > > Problem:
> > >
> > > I am unable to start debugging a WebApp on a particular remote Web
> server
> > > from my local machine.  Remote debugging on another web server works
> fine,
> > > but I have not discovered any difference thus far between the two
> servers.
> > > Local debugging works fine as well.
> > >
> > >
> > >
> > > Error msg 1:
> > >
> > > Error while trying to run project: Unable to start debugging on the
web
> > > server. Unable to map the debug start page URL to a machine name. ...
> > >
> > >
> > >
> > > Per one of the suggestions in the various links, I attempt to manually
> > > attach to the remote web server by choosing from VS IDE menu: Debug /
> > > Processes /[Name: remote_machine] and get the following error.
> > >
> > >
> > >
> > > Error msg 2:
> > >
> > > Unable to connect to the machine 'machinename'. The machine cannot be
> found
> > > on the network.
> > >
> > >
> > >
> > > Above error seems to be 'root' cause and is described on MSDN at
> > >
>
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/ht
> > > ml/vxurfunabletoconnecttomachine.asp).
> > >
> > >
> > >
> > > The "Solution" contained in the above link indicates that Enable
remote
> > > connection should be selected in dcomcnfg.exe.  I am NOT able to find
> this
> > > setting in dcomcnfg.exe -- perhaps I've missed something or it is my
> lack of
> > > understanding but I cannot find this specific reference in the
> dcomcnfg.exe.
> > > For what it's worth, I've compared settings in dcomcnfg.exe between
the
> > > working and non-working web servers and cannot find a difference.
> > >
> > > Continuing with dcomcnfg, of the various apps listed in Dcomcnfg, my
> guess
> > > is that MDM and JIT apply to remote debugging.  The current access
> > > permissions for these apps currently include the Debugger Users group
> and
> > > Administrators of which I am a member.
> > >
> > >
> > > Environments:
> > >
> > > Local: Win2k SP3, VS.NET 2003 EA
> > >
> > > Web Servers: Win2k, VS.NET remote debugging installed, (no IIS
Lockdown,
> yet)
> > >
> > > Different Domains:
> > >
> > > One potential issue is that the 'problem' server is in a different
> domain,
> > > while I do not normally log into the domain of the problem server, I
am
> > > connected (via UNC) to the web server as member of Administrators and
> > > Debugger Users as well as VS Developers group.  I have tried logging
> into
> > > the 2nd domain and attempted to debug but got the same error result.
The
> > > 2nd web server, for which remote debugging works, is in yet a 3rd
domain
> to
> > > which I am also UNC connected, so I don't see 'domain' as being part
of
> the
> > > problem.  Last, username/password on all domains are the same and I am
> > > member of Administrators in all machines involved.
> > >
> > > Remedies attempted:
> > >
> > > I have followed all steps in (http://support.microsoft.com/?id=822355)
> > > without resolution.
> > >
> > > On the non-working web server I have:
> > >
> > >             VS .NET Prerequisites
> > >
> > >             VS .NET Reinstall under Server Components, select Web
> > > Development and Remote Debugger)
> > >
> > >             Installed FrontPage Extensions
> > >
> > > Various other items tried:
> > > - Reinstalled (dotnetfx.exe),
> > > - Reinstalled "Remote Components" from VS.NET CD installer.
> > >
> > > Ran the 'install full remote debugging support on all operating
systems'
> as
> > > included in the RemoteComponents.htm found on VS.NET CD's.
> > > - Tested rpc ping successfully.
> > >
> > >
> > > I would appreciate any help as I'm at a dead-end.
>
>

Relevant Pages

  • vs2005 debugging on ws2k3 server
    ... I get the error "Unable to start debugging on the web server. ... good for localhost so they must be for any site on the local machine. ... NETWORK SERVICES and my user account - to no avail. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Debugging in multiple domains
    ... > Has anybody succedded in running Remote Debugging when your web client is ... in a different doman than your web server? ... something about not resolving the URL for the start page. ... IIS - but things are just totally pig-slow when I'm running IIS, V Studio, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Debugging in multiple domains
    ... > Has anybody succedded in running Remote Debugging when your web client is ... in a different doman than your web server? ... something about not resolving the URL for the start page. ... IIS - but things are just totally pig-slow when I'm running IIS, V Studio, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: The machine cannot be found on the network
    ... Neither web server is behind a firewall. ... >> I am unable to start debugging a WebApp on a particular remote Web ... >> is that MDM and JIT apply to remote debugging. ...
    (microsoft.public.vsnet.debugging)
  • Debugging returning 401 HTTP error
    ... Unable to start debugging on the web server." ... DEBUG verb is returning a 401 error. ... Web.config is well-formed and debugging is set to true. ... Enabled security auditing, ...
    (microsoft.public.dotnet.framework.aspnet)
Loading