I am facing a challenge with windows 7 networking. I am a scientist maintaining lab equipment, so apologies for any networking idiocies.
I have two Windows 7 machines running in one of our labs. Both have IP addresses issued by institutional DHCP server; both machines can ping each other (by IP address or by
<hostname>.<domain>). I am trying to map a network drive on machine 1 (from machine 2). When I attempt to map the drive as
All is right in the world (I am prompted for username/password, etc). If I attempt to map
\\<IP address>\<share folder>
I simply hang on
"Attempting to connect to \\<IP address>\<share folder>"
until I receive a
"Network error: Windows cannot access \\<IP address>\<share folder>".
Additional information: both machines are running institutionally-mandated/configured Symantec Endpoint Protection. If I disable it (not a sustainable solution), the error goes away, and I can map by IP address to my heart's content. Ultimately, though, I will need to be able to map by IP address for reasons beyond the scope of this question (happy to explain, though).
So: clearly Symantec is doing something that's stopping me from successfully mapping by IP address. Any ideas how it is doing this? My crude understanding from frantic googling is that windows filesharing uses ports 139 and 445... would mapping by IP address rather than network hostname change what port the filesharing request is sent/read on? i.e., perhaps Symantec is blocking one port but not the other? Otherwise, I'm unclear what information is going along for the ride that allows Symantec to distinguish the two operations.