Re: Sockets of domain controller can't be accessed by domain users

From: Joe Richards [MVP] (humorexpress@hotmail.com)
Date: 08/29/02 

From: "Joe Richards [MVP]" <humorexpress@hotmail.com>
Date: Thu, 29 Aug 2002 00:27:27 -0400

The MS Ping does it with a special Win32 API call that is defined in a
Platform SDK header file called IcmpAPI.h. The system does the pings on the
user's behalf then, the user doesn't open sockets directly. 

--
---
Joe Richards
www.joeware.net
---
"George" <george_x_yang@hotmail.com> wrote in message
news:lH%a9.1231$db.15059@newsfep1-win.server.ntli.net...
> Joe,
> Thanks for your answer.
> One thing I couldn't understand is what's the difference between the
system
> utility 'ping' and my utility 'ping'?
> I run them under the same domain user account and they behave differently.
> Why?
> I assume they both make use raw socket and work essentially the same way.
> Has any hidden/subtle thing been used by the OS to tell the system
utilities
> from user created executables?
> regards,
> George
>
> "Joe Richards [MVP]" <humorexpress@hotmail.com> wrote in message
> news:uq7Q6piTCHA.2576@tkmsftngp11...
> > Raw socket access on Windows 2000 requires admin access. This is
corrected
> > in XP and DotNET Server.
> >
> > --
> > Joe Richards
> > www.joeware.net
> > ---
> >
> > "George" <george_x_yang@hotmail.com> wrote in message
> > news:f24201c24e1c$2cf1a540$39ef2ecf@TKMSFTNGXA08...
> > > Hi, there,
> > > I am new to win2k server and have got a problem, which
> > > described as follows.
> > > I installed win2k server on my box as a domain controller
> > > and created a domain user. As a domain controller, the
> > > created user can't log in the box because the default
> > > security settings. So, I changed the local security
> > > setting and the domain controller's security setting, then
> > > the created user can log in now.
> > > Following that, I try to run ping utility to ping the box.
> > > It shows the result correctly.
> > > Then, I run my own ping utility, which actually is
> > > microsoft VC++ sample, I got an error, which shows access
> > > to socket denied.
> > > My own ping utility works well when I log in as
> > > administrator account.
> > > I guess the domain user may need some security right
> > > assigned before accessing sockets. (am I right?)
> > > Can anyone tell me how to enable a domain user
> > > create/access sockets on the domain controller?
> > >
> > > Regards,
> > >
> > > George
> >
> >
>
>

Relevant Pages

  • Re: Sockets of domain controller cant be accessed by domain users
    ... utility 'ping' and my utility 'ping'? ... I run them under the same domain user account and they behave differently. ... I assume they both make use raw socket and work essentially the same way. ... >> security settings. ...
    (microsoft.public.win2000.security)
  • Access denied as Users and Power Users
    ... If I log on like a Domain User or Power Users I can't use Ipconfig and ping ... The 3 Servers are configured identically.. ...
    (microsoft.public.win2000.general)
  • Re: Sockets of domain controller cant be accessed by domain users
    ... Raw socket access on Windows 2000 requires admin access. ... in XP and DotNET Server. ... I try to run ping utility to ping the box. ... > I guess the domain user may need some security right ...
    (microsoft.public.win2000.security)
  • Multithreading Socket Problem
    ... I am trying to implement a ping client that is multithreading. ... approach I have used is to create a ping class which I instantiate ... On reception of data on the socket the callback method referenced by ... is called and I cast the IAsyncResult asyn object to the CSocketPacket ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: not able to create socket ,coz of insufficient user rights
    ... including Ping, the ping function is openning Raw ... Socket is in System.Net.Sockets Namespace not in ... >> failing, I am not able to debug this code. ...
    (microsoft.public.security)