lsass.exe listening on UDP port 1033

WINDOWS SERVER

    Sponsored Links

    Next

  • 1. Wireless workstations dont get software installations from group policy
    I have a few xp workstation using wireless, they don't seem to be able to get software installations while hard wired xp workstations do. My guess is that the software installation try to install before wireless connection completed any ideas?
  • 2. Licensing: User or device CAL for standalone app computer
    Regarding CALs for Windows Server 2003: The Licensing FAQ has this to say about user and device CALs: "Q. What is the difference between a device CAL and a user CAL? A. A device CAL permits one device (used by any user) to access the server software. A user CAL permits one user (using any device) to access the server software." What about one device used by NO user? We have a computer (running Windows XP) that connects to our domain controller, and runs standalone, and runs software to receive faxes and e- mails that are sent to an archive mailbox. All of this happens with no user intervention (and rarely does any user ever look at the messages in that mailbox's PST file, and when they do, it's from another computer). No person logs on to this computer, although of course it has a logon username to connect to the domain. So would this computer be counted as "one" whether it's a device CAL or a user CAL? The Q&As don't seem to cover unattended computers at all. We're going to upgrade the server/domain controller from Windows 2000 server to Windows 2003 server, so I want to make sure we know how to count! Thanks. David Walker
  • 3. Adaptec 29230LPE on 2003 Server 64Bit
    Any others running the above hardware. We have the following.. Supermicro SuperServer 6025B-URB with the latest BIOS using an Adaptec 29230LPE SCSI card that is attaching a Quantum LTO 200/400GB tape drive. The server motherboard and SCSI card both have the latest BIOS updates, and Adaptec only offers 1 driver for 64Bit. When the driver loads, random reboots happen, as well as blue screens on shutdown. Adaptec is "looking into the problem", but this has been going on for about 3 weeks now, and I need to get the tape drive back up and running! Just curious if any others run the above combo, and if they have any problems (mostly wondering about the combo of that OS with this particular card)?
  • 4. Tape Backup
    Hi, Am trying to use a tape from Server A into Server B with NTBACKUP but when I try to do so the tape just get rejected out of the slot. Any clue anyone? Thanks

lsass.exe listening on UDP port 1033

Postby Y2hhc3dvb2Q » Wed, 10 Aug 2005 21:42:19 GMT

We have a new installation for Windows Terminal Services running at a 
client's site.  

In the security audit log we are getting the following failure on a constant 
basis:
*********
The Windows Firewall has detedted an application listening for incoming 
traffic.

Name: -
Path: C:\WINDOWS\system32\lsass.exe
Process identifier: 472
User account: SYSTEM
User Domain: NT AUTHORITY
Service: Yes
RPC server: No
IP version: IPv4
IP protocol: 1033
Allowed: No
User notified: No
*********

I have searched for process id 472 as well as anything relating to listening 
on port 1033, but find very little.  Is this something we should be concerned 
about?  If so, how do we turn it off?

Thank you in advance!


-- 
chaswood
IT Consultant
Heartland Computer


Similar Threads:

1.Port 1033 (netinfo) port is open - what's it for and how do I close it

2.LISTENING, ESTABLISHED, CLOSE_WAIT TCP Ports & UDP Ports?

I'm running Windows Server 2003.
Can somebody explain me why are all this ports opened, and how are they bein 
used, is this a security risk can somebody in the network or from the 
internet gain access to my server?
what kind of messure do I need to take beside just to place a firewall?
Thanks a lot...

This is what i get when I run netstat -ano
Active Connections

  Proto  Local Address          Foreign Address        State           PID
  TCP    0.0.0.0:42             0.0.0.0:0              LISTENING 
wins.exe
  TCP    0.0.0.0:53             0.0.0.0:0              LISTENING 
dns.exe
  TCP    0.0.0.0:88             0.0.0.0:0              LISTENING 
lsass.exe
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING 
svchost.exe
  TCP    0.0.0.0:389            0.0.0.0:0              LISTENING 
lsass.exe
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING 
System
  TCP    0.0.0.0:464            0.0.0.0:0              LISTENING 
lsass.exe
  TCP    0.0.0.0:593            0.0.0.0:0              LISTENING 
svchost.exe
  TCP    0.0.0.0:636            0.0.0.0:0              LISTENING 
lsass.exe
  TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING 
lsass.exe
  TCP    0.0.0.0:1026           0.0.0.0:0              LISTENING 
svchost.exe
  TCP    0.0.0.0:1028           0.0.0.0:0              LISTENING 
lsass.exe
  TCP    0.0.0.0:2804           0.0.0.0:0              LISTENING 
IDUServ.exe
  TCP    0.0.0.0:3001           0.0.0.0:0              LISTENING 
ntfrs.exe
  TCP    0.0.0.0:3005           0.0.0.0:0              LISTENING 
wins.exe
  TCP    0.0.0.0:3011           0.0.0.0:0              LISTENING 
dns.exe
  TCP    0.0.0.0:3012           0.0.0.0:0              LISTENING 
tcpsvcs.exe
  TCP    0.0.0.0:3268           0.0.0.0:0              LISTENING 
lsass.exe
  TCP    0.0.0.0:3269           0.0.0.0:0              LISTENING 
lsass.exe
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING 
svchost.exe
  TCP    127.0.0.1:389          127.0.0.1:1037         ESTABLISHED 
lsass.exe
  TCP    127.0.0.1:389          127.0.0.1:1038         ESTABLISHED 
lsass.exe
  TCP    127.0.0.1:389          127.0.0.1:1039         ESTABLISHED 
lsass.exe
  TCP    127.0.0.1:389          127.0.0.1:3007         ESTABLISHED 
lsass.exe
  TCP    127.0.0.1:1032         0.0.0.0:0              LISTENING 
ccproxy.exe
  TCP    127.0.0.1:1037         127.0.0.1:389          ESTABLISHED 
ismserv.exe
  TCP    127.0.0.1:1038         127.0.0.1:389          ESTABLISHED 
ismserv.exe
  TCP    127.0.0.1:1039         127.0.0.1:389          ESTABLISHED 
ismserv.exe
  TCP    127.0.0.1:2804         127.0.0.1:3117         ESTABLISHED 
IDUServ.exe
  TCP    127.0.0.1:2804         127.0.0.1:4202         ESTABLISHED 
IDUServ.exe
  TCP    127.0.0.1:3007         127.0.0.1:389          ESTABLISHED 
dns.exe
  TCP    127.0.0.1:3082         0.0.0.0:0              LISTENING 
alg.exe
  TCP    127.0.0.1:3117         127.0.0.1:2804         ESTABLISHED 
iptray.exe
  TCP    127.0.0.1:4202         127.0.0.1:2804         ESTABLISHED 
iptray.exe
  TCP    192.168.1.10:139       0.0.0.0:0              LISTENING 
System
  TCP    192.168.1.10:139       192.168.1.50:2931      ESTABLISHED 
System
  TCP    192.168.1.10:139       192.168.1.56:1267      ESTABLISHED 
System
  TCP    192.168.1.10:389       192.168.1.10:3099      ESTABLISHED 
lsass.exe
  TCP    192.168.1.10:1025      192.168.1.10:3103      ESTABLISHED 
lsass.exe
  TCP    192.168.1.10:1025      192.168.1.10:3105      ESTABLISHED 
lsass.exe
  TCP    192.168.1.10:1025      192.168.1.10:3902      ESTABLISHED 
lsass.exe
  TCP    192.168.1.10:1025      192.168.1.10:4742      ESTABLISHED 
lsass.exe
  TCP    192.168.1.10:3099      192.168.1.10:389       ESTABLISHED 
ntfrs.exe
  TCP    192.168.1.10:3103      192.168.1.10:1025      ESTABLISHED 
ntfrs.exe
  TCP    192.168.1.10:3105      192.168.1.10:1025      ESTABLISHED 
ntfrs.exe
  TCP    192.168.1.10:3389      66.245.216.179:10215   ESTABLISHED 
svchost.exe
  TCP    192.168.1.10:3832      192.168.1.10:389       CLOSE_WAIT 
svchost.exe
  TCP    192.168.1.10:3902      192.168.1.10:1025      ESTABLISHED 
lsass.exe
  TCP    192.168.1.10:4204      192.168.1.10:389       CLOSE_WAIT 
mmc.exe
  TCP    192.168.1.10:4339      192.168.1.10:389       CLOSE_WAIT 
mmc.exe
  TCP    192.168.1.10:4455      192.168.1.10:389       CLOSE_WAIT 
mmc.exe
  TCP    192.168.1.10:4478      192.168.1.10:389       CLOSE_WAIT 
mmc.exe
  TCP    192.168.1.10:4742      192.168.1.10:1025      ESTABLISHED 
lsass.exe
  UDP    0.0.0.0:42             *:* 
wins.exe
  UDP    0.0.0.0:445            *:* 
System
  UDP    0.0.0.0:500            *:* 
lsass.exe
  UDP    0.0.0.0:1030           *:* 
svchost.exe
  UDP    0.0.0.0:1031           *:* 
svchost.exe
  UDP    0.0.0.0:1035           *:* 
dns.exe
  UDP    0.0.0.0:1036           *:* 
ismserv.exe
  UDP    0.0.0.0:3002           *:* 
ntfrs.exe
  UDP    0.0.0.0:3004           *:* 
wins.exe
  UDP    0.0.0.0:3006           *:* 
dns.exe
  UDP    0.0.0.0:3068           *:* 
lsass.exe
  UDP    0.0.0.0:3086           *:* 
winlogon.exe
  UDP    0.0.0.0:3419           *:* 
spoolsv.exe
  UDP    0.0.0.0:3587           *:* 
dfssvc.exe
  UDP    0.0.0.0:3831           *:* 
svchost.exe
  UDP    0.0.0.0:3908           *:* 
llssrv.exe
  UDP    0.0.0.0:4199           *:* 
winlogon.exe
  UDP    0.0.0.0:4203           *:* 
mmc.exe
  UDP    0.0.0.0:4338           *:* 
mmc.exe
  UDP    0.0.0.0:4500           *:* 
lsass.exe
  UDP    127.0.0.1:53           *:* 
dns.exe
  UDP    127.0.0.1:123          *:* 
svchost.exe
  UDP    127.0.0.1:1034         *:* 
dns.exe
  UDP    127.0.0.1:3129         *:* 
iexplore.exe
  UDP    192.168.1.10:53        *:* 
dns.exe
  UDP    192.168.1.10:67        *:* 
tcpsvcs.exe
  UDP    192.168.1.10:68        *:* 
tcpsvcs.exe
  UDP    192.168.1.10:88        *:* 
lsass.exe
  UDP    192.168.1.10:123       *:* 
svchost.exe
  UDP    192.168.1.10:137       *:* 
System
  UDP    192.168.1.10:138       *:* 
System
  UDP    192.168.1.10:389       *:* 
lsass.exe
  UDP    192.168.1.10:464       *:* 
lsass.exe
  UDP    192.168.1.10:2535      *:* 
tcpsvcs.exe 


3.[sockets] Listen on several UDP ports ?

>
>
> I am thinking about if someone have 2 pc (or more) and want to play my 
> game on both, then he will have to use another port [...]
>
You are not thinking correctly. UDP/IP datagrams have remote as well as 
local information.

4.Listen on several UDP ports ?

I don't understand what you mean, can you explain a bit more ?

5.[sockets] Listen on several UDP ports ?

Hi, first of all sorry if I am not in the right section, I program for
windows then I thought it was a good place.

I am developping an online game using a UDP server/client connection,
I am thinking about if someone have 2 pc (or more) and want to play my
game on both, then he will have to use another port but how can I make
my server listening several port ?
Must I open several socket for all ports I want to listen ? It'd mean
I'll have to check successively for each port ?

Thanks

6. Listen on several UDP ports ?

7. alg.exe listening on udp 1026?

8. LSASS.EXE or lsass.exe...which one



Return to WINDOWS SERVER

 

Who is online

Users browsing this forum: No registered users and 1 guest