I know those were kernel functions,I searched kernel API entries in some reference documents,and found most of functions listed in <<Windows Kernel Interals-Process Architecture>>,only
NtGetNextProcess(),NtGetNextThread()
could not be found.Even I could NOT found entrys of them
in ntdll.dll...
Hi:
I'v read the document <<Windows Kernel Interals-Process Architecture>>,written by David B. Probert, Ph.D.
In that he list some Windows native APIs like:
NtGetNextProcess(),NtGetNextThread()...
I tried but I could not find these APIs reference.
Any advice is helpful,thanks.
alixiang
Thanks for your infomation.Could you tell me why the System process listening those ports?I'v not installed any network service in my system.
Best regard!
Alixiang
Hello everyone:
When Windows 2000 running,it was listning some TCP and UDP ports.I know about TCP 135,139 and 445,but most of them were mystification.
They are:
TCP:1025,1057,1079,1081,1093,1096,1098,1100,1101,1103,1104,
1105,1106,1108,1109,1111,1112,1113,1115,1117,1119,1120,1121...
The NIC worked well. The ISP did not require any addtional software to build the link. This problem started since I changed the ISP.
I did the "ipconfig /renew" command when the Internet connection interrupted, the NIC got the new correct IP!
Thanks to GlenJohnson,ricpinto...
Hi friends:
I have changed to a new ISP for few days. They use DHCP to provide IP to customer. I use a Windows 2000 system, after I boot the system, the IP has assign to the NIC linked to ISP,normally was 219.x.x.x
My problem is, 2~3 hours late, the IP is changed to 169.x.x.x and be without...
Use "no shutdown" command to make FastEthernet 0/1 up.
Linke a actived NIC to the Fa port,then the line protocol would turn up.
When any interfaces in a vlan was active£¬the vlan's line protocol would turn up.
kevinchen129:
It's look like a route table problem. the route to the
net 192.168.0.0/24 is point to elxl1,so your ICMP request
to elxl2 was responed by elxl1.
You could test this to change the IP address of elxl2 to
a diff sub-net,like 192.168.100.2/24,then link a client with
IP...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.