Name | Number(h) | Type | Usage |
00 | U | Workstation service | |
01 | U | Messenger service | |
01 | G | Master Browser | |
03 | U | Messenger service | |
06 | U | Remote Access Server service | |
1F | U | NetDDE service | |
20 | U | File Server service | |
21 | U | Remote Access Server client service | |
22 | U | Exchange Interchange (MSMail Connector) | |
23 | U | Exchange Store | |
24 | U | Exchange Directory | |
30 | U | Modem Sharing Server service | |
31 | U | Modem Sharing client service | |
43 | U | SMS Clients Remote Control | |
44 | U | SMS Administrators Remote Control Tool | |
45 | U | SMS Clients Remote Chat | |
46 | U | SMS Clients Remote Transfer | |
87 | U | Microsoft Exchange MTA | |
6A | U | Microsoft Exchange IMC | |
BE | U | Network Monitor Agent | |
BF | U | Network Monitor Application | |
03 | U | Messenger service | |
00 | G | Domain Name | |
1B | U | Domain Master Browser | |
1C | G | Domain Controllers | |
1D | U | Master Browser | |
1E | G | Browser Service Elections | |
1C | G | IIS | |
00 | U | IIS |
Search This Blog
Oct 13, 2006
NetBIOS name resource types
Network issues that affect TCP/IP and RPC traffic across firewall or VPN after Windows 2003 SP1
After you install Windows Server 2003 Service Pack 1 (SP1), you may
experience issues that affect server-to-server communication for TCP/IP
traffic or remote procedure call (RPC) traffic across firewall or
virtual private network (VPN) products in rare and specific network
configurations.
Before carrying any troubleshooting, check the following KBs:
Q899148 Some firewalls may reject network traffic that originates from
Windows Server 2003 Service Pack 1-based computers
Q898060 Installing security update MS05-019 or Windows Server 2003
Service Pack 1 may cause network connectivity between clients and
servers to fail
experience issues that affect server-to-server communication for TCP/IP
traffic or remote procedure call (RPC) traffic across firewall or
virtual private network (VPN) products in rare and specific network
configurations.
Before carrying any troubleshooting, check the following KBs:
Q899148 Some firewalls may reject network traffic that originates from
Windows Server 2003 Service Pack 1-based computers
Q898060 Installing security update MS05-019 or Windows Server 2003
Service Pack 1 may cause network connectivity between clients and
servers to fail
Sep 13, 2006
DFSR notes 1
- Basic: DFS Namespace and DFS Replication are totally separate things despite the fact that they can work together and often work together
- You configure DFSR to replicate physical folders then publish them into namespaces
- You can’t create file under DFS namespace? (Access denied.) However you can do so on physical folders
Answer: this is because target folder can be created only on shared folders. And I grant Read only on those shared folders. - You can add(associate) multiple target folders into one folder in namespace. DFS Namespace will give you chance to create RG(you don’t have to). You will be referred to one of the targets when accessing using DFS namespace.
- Looks like we have to create RB then create namespace folder from RB, or vice versa. We can’t create both ready and connect them.
- To configure one-way replication, we can disable one of the sending connections in RG. However this is not recommended by Microsoft (see Planning Guide). Instead, NTFS permissions should be used to control replication direction.
- Domain controllers don’t have to run on R2. On servers that are involved in replication or act as name space server have to run R2. R2 schema (version 31) is that is required.
End#
Subscribe to:
Posts (Atom)