lsass.exe listening on UDP port 1033

WINDOWS SERVER

    Sponsored Links

    Next

  • 1. Windows Backup
    I chose to use Windows Backup, and the option to append data to tape with data is not available. its greyed out. Please help. Thanx
  • 2. Backup and restore of Active Directory
    Is there a method to backup and restore my active directory in case I decide I need to re-install my server 2003 installation. I currently am using server 2000 and we just upgraded to Server 2003. I did not see any method to perform a AD backup and I was wondering if this was a feature that was implimented in this version of the software. Thanks! >> larry << MIS Norris Precision Mfg
  • 3. Weird System Winodow message
    Hi, While I was using the terminal, it pop out the system windows as below: ================================ Bitmap Disk Cache Failure Your disk is full or the cache directory is missing or corrupted. Some bitmaps may not appear It is recommended that you disconnect and reconnect to disable caching bitmaps to disk =============================== Any infomation will be appreciated. Thank you in advance, Johnny Chow
  • 4. Event ID 1085 and 1091 messages in app log
    Apparently, I have a GPO with a Wireless policy causing 1085 and 1091 errors in the application logs. The servers have SP1 installed and according to KB article 823608, this SP should resolve these errors. I'm not ready to rebuild the policy at this time is there a remedy for these errors?
  • 5. Edit webpage from work??????
    I am new to frontpage 2003 and server 2003, IIs 6.0. I am hosting my own website on a box at my house that i am running the previously mentioned software and os on. I am trying to figure out how to edit my website from work during the day. Like i said i am new at this. The site is up and running fine. When i go to the page from work i can click on edit with Fp and it will launch FP with my front page ready to edit. Whenever i make changes and save it saves on my local drive. What do i need to do to have that sent back to my server or am i doing it all wrong. Any help would be great. If anyone knows another good FP reference site that would be good also. 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 50 guest