Why is "Nebula Secure Segment Transfer Protocol" attacking me?

[Sharon Smith]

Can someone help me as to why nsstp is attacking me?

I installed a firewall program and now, daily, I get the message that
"206.13.28.12" is trying to connect to "port 1036" by "svchost.exe".

When I google that, I don't find out what it is.
All I can find is what is shown in the port lists, e.g.,
http://www.iana.org/assignments/port-numbers
i.e.,
# Arnold E. Mauer <[email protected]> April 2003
nsstp 1036/tcp Nebula Secure Segment Transfer Protocol
nsstp 1036/udp Nebula Secure Segment Transfer Protocol

QUESTION:
Can someone help me as to why nsstp is attacking me?
What is this thing?

Sharon

 

[lorenzodes]

Sharon Smith wrote on date 22/12/2004 17.13:

Can someone help me as to why nsstp is attacking me?

I installed a firewall program and now, daily, I get the message that
"206.13.28.12" is trying to connect to "port 1036" by "svchost.exe".

When I google that, I don't find out what it is.
All I can find is what is shown in the port lists, e.g.,
http://www.iana.org/assignments/port-numbers
i.e.,
# Arnold E. Mauer <[email protected]> April 2003
nsstp 1036/tcp Nebula Secure Segment Transfer Protocol
nsstp 1036/udp Nebula Secure Segment Transfer Protocol

QUESTION:
Can someone help me as to why nsstp is attacking me?
What is this thing?

Sharon

206.13.28.12 is a DNS server, judging from the header of your post, it
may be your DNS server. Was it UDP traffic by any chance? And was the
remote port 53?

 

[C.C. Chapman]

Sharon Smith wrote on date 22/12/2004 17.13:

206.13.28.12 is a DNS server, judging from the header of your post, it
may be your DNS server. Was it UDP traffic by any chance? And was the
remote port 53?

It's probably the Windows network systems standard time parser (nsstp)
checking to see if your system clock is set properly. Your ISP needs
that information to accurately track your actions. Did you change your
clock? If so you probably tipped them off to make the nsstp check.

 

[lorenzodes]

C.C. Chapman wrote on date 24/12/2004 8.57:

It's probably the Windows network systems standard time parser (nsstp)
checking to see if your system clock is set properly. Your ISP needs
that information to accurately track your actions. Did you change your
clock? If so you probably tipped them off to make the nsstp check.

You have a strange sense of humour.