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 Email 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 to detect and defend against a TCP port 445 exploit and attacks

How was a MikroTik router hack used to hijack traffic?

Implementing VMware border router ingress and egress filtering

6 AIOps security use cases to safeguard the cloud

Implement Kubernetes for multi-cloud architecture security

Google forms cyber insurance pact with Allianz, Munich Re

Wi-Fi 6 rollout requires careful review of network devices

How cloud-native networking will transform infrastructure

The role of network observability in distributed systems

Managing cybersecurity during the pandemic and in the new digital age

Enterprise architecture has business's ear at Scottish Water

4 IT contract negotiation strategies to drive value in 2021

Incorporating zero trust into endpoint security

Keeping tabs on employees in the hybrid workplace

Top 6 endpoint security software options in 2021

Choose the right serverless container service

IBM boosts vertical cloud push with financial services cloud

Open source cloud platforms and tools to consider

Biden sanctions Russia over SolarWinds cyber attacks

Only government standing in the way of fair compensation for subpostmasters

University of Hertfordshire is latest academic cyber attack victim