Unable to reach public network share through Wifi (Private/Public network profile)
Hi,
I've a windows 2016 server set in a DMZ environment. He's sharing a network folder through it's public IP Address. Current network profile is private
When I try to reach this network share from a Windows 10 release 1803 computer, it works only if I'm connected through the domain network profile.
However, as soon as I'm trying to reach this same network share from the private/public network profile, it does not work. It must be some silly rule somewhere to fix this but I couldnt find anything.
I've double checked the Firewall rules, the network profiles rules (the 3 of them have the same settings) and I'm still can't reach this network share unless I'm connected through the domain network profile (ethernet wire).
does anyone had such issue and has a clue on how solve it? :)
Looking forward to hearing from you.
D.
I've a windows 2016 server set in a DMZ environment. He's sharing a network folder through it's public IP Address. Current network profile is private
When I try to reach this network share from a Windows 10 release 1803 computer, it works only if I'm connected through the domain network profile.
However, as soon as I'm trying to reach this same network share from the private/public network profile, it does not work. It must be some silly rule somewhere to fix this but I couldnt find anything.
I've double checked the Firewall rules, the network profiles rules (the 3 of them have the same settings) and I'm still can't reach this network share unless I'm connected through the domain network profile (ethernet wire).
does anyone had such issue and has a clue on how solve it? :)
Looking forward to hearing from you.
D.
Last Comment
ASKER
Hi,
thanks for your reply. About the error message, I just get the standard error "Windows cannot access.... \\blablaba\share$" and suggest to perform a network diagnosis...
Telnet on port 445 works on all non domain profiles, which is a very good sign.
The system does itself automatically the switch when we go from Wired network to WiFi.
Any ideas?
thanks for your reply. About the error message, I just get the standard error "Windows cannot access.... \\blablaba\share$" and suggest to perform a network diagnosis...
Telnet on port 445 works on all non domain profiles, which is a very good sign.
The system does itself automatically the switch when we go from Wired network to WiFi.
Any ideas?
If the port is reachable, it should just work. Are any 3rd party firewalls active as well?
ASKER
Hi,
Thanks for your message and support :)
my apologizes, the telnet on 445 doesn't work while on WiFi.
I've excluded device from all GPO's, reset the windows defender firewall settings but problem persists.
the computer is actually a MS Sufrace Pro 4.
I've tried yesterday on a "standard" laptop, which has same GPO rules and it works.
I've McAfee ENS installed (standard antivirus, no firewall suite). I will remove it and keep you posted.
very very weird...
Thanks for your message and support :)
my apologizes, the telnet on 445 doesn't work while on WiFi.
I've excluded device from all GPO's, reset the windows defender firewall settings but problem persists.
the computer is actually a MS Sufrace Pro 4.
I've tried yesterday on a "standard" laptop, which has same GPO rules and it works.
I've McAfee ENS installed (standard antivirus, no firewall suite). I will remove it and keep you posted.
very very weird...
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Brillant. it was actually our WiFi router which is blocking 445 port. pfiouuuuu
Thanks a lot!
Thanks a lot!
Great :-)
Windows OS
This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
I assume you get an error message which is…?
The file share is reachable on port 445, so please see if you can reach that port from your non-domain profiles at all.
But foremost: why do you even have to switch profiles?