Mapping network drives with limited protocols/services

What protocol/service if any is required when mapping network drives? I'm running a software-based firewall to...

Step 2 of 2:

You forgot to provide an Email Address.

This email address doesn’t appear to be valid.

This email address is already registered. Please login.

You have exceeded the maximum character limit.

Please provide a Corporate E-mail Address.
- I agree to TechTarget’s Terms of Use, Privacy Policy, and the transfer of my information to the United States for processing to provide me with relevant information as described in our Privacy Policy.
Please check the box if you want to proceed.
- I agree to my information being processed by TechTarget and its Partners to contact me via phone, email, or other means regarding information relevant to my professional interests. I may unsubscribe at any time.
Please check the box if you want to proceed.

separate my two network segments and wish to better secure my network by only allowing those service needed to access computers on lets say segment_B. I'm currently allowing ICMP, UDP, TCP, FTP and RDP request through the firewall. If I set the security rule to allow for any service, mapping a drive from one netork to the next is not problem.

Microsoft site

Windows 2000 is a different animal if using the new features and not older NT 4.0 features. Direct hosted "NetBIOS-less" SMB traffic uses port 445 (TCP and UDP). In this situation, a four-byte header precedes the SMB traffic. The first byte of this header is always 0x00, and the next three bytes are the length of the remaining data.

This is obvious. Microsoft no longer will support them.

Infrastructure and Network Security

Is there a site I could go to that might assist me in knowing what protocol/service controls which communication request? As found on the , NT 4.0 used: NetBIOS over TCP traditionally with the following ports: nbname 137/UDP nbname 137/TCP nbdatagram 138/UDP nbsession 139/TCP Finally, I think the answer is found in if you are using NetBIOS over TCP (ports 137, 138 and 139) or the newer NetBIOS-less SMB traffic over port 445 (TCP & UDP). Fair warning any of the following will not work with a Win 2000 server unless running the following in legacy mode: IBM OS/2 1.3 Lan Manager 2.2 Microsoft Net Server 1.11 Hewlett-Packard Unix Lan Manager X For more information on this topic, visit these other SearchSecurity.com resources: Ask the Expert: What is NetBIOS? Ask the Expert: Determining which TCP/IP services are needed Best Web Links:

This was last published in December 2002

Dig Deeper on Web application and API security best practices

SearchCloudSecurity

UDP (User Datagram Protocol)

How was a MikroTik router hack used to hijack traffic?

Implementing VMware border router ingress and egress filtering

Nmap tutorial: Nmap scan examples for vulnerability discovery

6 SaaS security best practices to protect applications

Review these 7 CASB vendors to best secure cloud access

CASB explained: Know its use cases before you buy

Considerations for SASE management and troubleshooting

Cisco sweetens Acacia deal by $2 billion

SASE challenges include network security roles, product choice

Parler sues AWS, seeks restraining order

Digital healthcare top priority for CIOs in 2021

C-suite execs give future technology predictions for the decade

Will Windows 10 be the last Windows OS?

CES: Laptops sport designs friendly for remote workers

Evaluate if Windows 10 needs third-party antivirus

COVID-19 and remote work shift cloud predictions for 2021

Cloud providers jockey for 2021 market share

How to build a cloud center of excellence

MoD reports 18% rise in data loss incidents

Three UK, Tata team to accelerate 5G network roll-out

Hyperoptic offers free broadband packages for home schooling