Date parsed: 12/17/2002 6:28:50 PM
Date: Tue, 17 Dec 2002 18:28:50 +0100
Services (like SL4NT) can start on XP computers BEFORE the network
(including interfaces with static addresses) is fully initialized because of
the default "Fast Logon Optimization" behaviour of XP. This is of course
undesireable if any server services (like SL4NT) are running on the XP
computer.
You should turn off "Fast Logon Optimization", by enabling the following
policy setting:
Computer Configuration\Administrative Templates\System\Logon\ Always wait
for the network at computer startup and logon
When this policy is enabled, a Windows XP client behaves in the same manner
as a Windows 2000/.NET Server computer at both system startup and at user
logon.
Franz
"Slide" <slide@oddpost.com> wrote in message
news:om0AcwXpCHA.3184@is1.netal.com...
> Thanks for looking things up Franz. Its good to know its part of normal
> operation.
>
> Best Regards,
> Slide
>
> p.s. I have a dual ethernet setup. Only one of the ports has a fixed IP
> address. The other
> is DHCP.
>
> "Franz Krainer" <franzk@netal.com> wrote in message
> news:H5vrpMIpCHA.2924@is1.netal.com...
> > Hi Slide,
> >
> > I found the cause of the error event entry you see in the Application
> event
> > log:
> >
> > It is written when the SL4NT service is starting and at startup time no
> > network interface has a valid IP-address (because, for example, the
> existing
> > network interface is DHCP-enabled and has not been initialized
> successfully
> > at the time of SL4NT startup).
> >
> > In this case SL4NT tries to bind to 127.0.0.1:514 two times
(erroneously)
> > and at the second time it fails and logs the error message.
> >
> > You can safely ignore this message, it does not indicate a real problem.
> >
> > But please be aware of the fact that this message is logged because
> there's
> > currently no valid IP-address on any interface (because of DHCP, for
> > example). This means that SL4NT will in this case only be bound to the
> > loopback-address, not to addresses which are available some seconds
after
> > startup of SL4NT.
> >
> > Franz
> >
> > "Slide" <slide@oddpost.com> wrote in message
> > news:mBvS$I6oCHA.4728@is1.netal.com...
> > > Thanks for the quick reply Franz.
> > >
> > > It looks like it is sl4ntsvc.exe which is the SL4NT service process.
> > >
> > > snippet from netstat -ano
> > >
> > > UDP 127.0.0.1:123 *:*
> > 1052
> > > UDP 127.0.0.1:514 *:*
> > 1760
> > > UDP 127.0.0.1:1900 *:*
> > 1272
> > > UDP 127.0.0.1:2051 *:*
> > 1748
> > > UDP 127.0.0.1:2260 *:*
> 284
> > > UDP 127.0.0.1:2508 *:*
> > 2732
> > > UDP 192.168.0.5:123 *:*
> > 1052
> > > UDP 192.168.0.5:137 *:*
4
> > > UDP 192.168.0.5:138 *:*
4
> > > UDP 192.168.0.5:514 *:*
> > 1760
> > > UDP 192.168.0.5:1900 *:*
> > 1272
> > > UDP 192.168.0.5:11037 *:*
> > 1812
> > > UDP 192.168.0.5:15625 *:*
> > 1812
> > >
> > > and from task manager
> > >
> > > ImageName PID User Name
> > > sl4ntsvc.exe 1760 SYSTEM
> > >
> > > So my guess is that every so often something is try to bind to that
> port.
> > I
> > > am not sure what it might be. What other Windows process try and
listen
> on
> > > 514?
> > >
> > > Slide
> > >
> > >
> > > "Franz Krainer" <franzk@netal.com> wrote in message
> > > news:VTrRHz2oCHA.4036@is1.netal.com...
> > > > Hi Slide,
> > > >
> > > > please try the 'netstat' tool again, this time with the parameter
> > '-ano'.
> > > >
> > > > The additional 'o' switch will display the process ID (PID) of the
> > owning
> > > > process. Use the displayed PID at the end of the line 'UDP
> > > 127.0.0.1:514
> > > > *:*' to find out the name of the owning process by looking at the
list
> > of
> > > > (all) running processes in Task Manager.
> > > >
> > > > I guess that there's another process using the port 127.0.0.1:514,
> > > > preventing SL4NT from binding to this port.
> > > >
> > > > Franz
> > > >
> > > >
> > > > "Slide" <slide@oddpost.com> wrote in message
> > > > news:Unk4kR0oCHA.4724@is1.netal.com...
> > > > > I am getting the following error in the Application EventLog with
> > regard
> > > > to
> > > > > SL4NT:
> > > > >
> > > > > "An error occurred in binding a socket to 127.0.0.1:514/UDP.
> > WinSockets
> > > > > Error: 10048 - Only one usage of each socket address
> (protocol/network
> > > > > address/port) is normally permitted."
> > > > >
> > > > > The error occurs about once a day.
> > > > >
> > > > > I am running Windows XP professional. Here is a snippet from the
> > > > > 'netstat -an' command to see what is listening on what ports.
> > > > >
> > > > > UDP 0.0.0.0:135 *:*
> > > > > UDP 0.0.0.0:445 *:*
> > > > > UDP 0.0.0.0:500 *:*
> > > > > UDP 0.0.0.0:1026 *:*
> > > > > UDP 0.0.0.0:1028 *:*
> > > > > UDP 0.0.0.0:1029 *:*
> > > > > UDP 0.0.0.0:1034 *:*
> > > > > UDP 0.0.0.0:1045 *:*
> > > > > UDP 0.0.0.0:1122 *:*
> > > > > UDP 0.0.0.0:1481 *:*
> > > > > UDP 0.0.0.0:3456 *:*
> > > > > UDP 127.0.0.1:123 *:*
> > > > > UDP 127.0.0.1:514 *:*
> > > > > UDP 127.0.0.1:1900 *:*
> > > > > UDP 127.0.0.1:2051 *:*
> > > > > UDP 127.0.0.1:2260 *:*
> > > > > UDP 127.0.0.1:2441 *:*
> > > > > UDP 127.0.0.1:2452 *:*
> > > > > UDP 127.0.0.1:2474 *:*
> > > > > UDP 127.0.0.1:2499 *:*
> > > > > UDP 192.168.0.5:123 *:*
> > > > > UDP 192.168.0.5:137 *:*
> > > > > UDP 192.168.0.5:138 *:*
> > > > > UDP 192.168.0.5:514 *:*
> > > > > UDP 192.168.0.5:1900 *:*
> > > > > UDP 192.168.0.5:11037 *:*
> > > > > UDP 192.168.0.5:54649 *:*
> > > > >
> > > > > Slide
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>