Samba machine not showing in Network folder

Not sure if here or the Ubuntu forums is the correct place to post this, so I'm posting to both.

I have a file server running Ubuntu Server 14.04, with Samba set up for Windows file shares. I have it all set up to do mostly what I want, but there's one odd problem that I can't seem to fix: even though I can manually go to //192.168.1.3 (the IP) or //fileserver and browse my shares and files normally, I can't get the file server to show up in Windows' Network folder.

No amount of refreshing the folder, restarting Samba, or rebooting either my computer or the file server seems to fix this. All that shows up is the machine I'm using, as well as whatever other Windows PCs are running (which means that network discovery is definitely set properly). Also, I can map network drives to the specific shares without an issue.

I've confirmed that both machines are on the same workgroup (smb.conf has workgroup = WORKGROUP, and my Windows 10 machine is on WORKGROUP as well (and is stuck on that, too, since it's running 10 Home). Googling the issue showed other people with similar problems, and offered various config options in smb.conf as a solution, but none of them work. (I did of course restart Samba after each attempt.)

This is my smb.conf, edited for privacy and to remove commented lines (it's mostly default):

Code:

[global]

workgroup = WORKGROUP

server string = <server string>

dns proxy = no

log file = /var/log/samba/log.%m

max log size = 1000

syslog = 0

panic action = /usr/share/samba/panic-action %d

server role = standalone server

passdb backend = tdbsam

obey pam restrictions = yes

unix password sync = yes

pam password change = yes

map to guest = bad user

[Share A]
path = /home/fileserver/blah/blah
read only = no
writeable = yes
browseable = yes
create mask = 0770
force create mode = 0770
locking = yes

[Share B]
path = /home/fileserver/blah/blah
read only = no
writeable = yes
browseable = yes
create mask = 0770
force create mode = 0770
locking = yes

Nothing but more shares with identical settings below here.

Did I set something wrong or what?

EDIT: I just noticed that it shows up like it should on my Surface RT's network folder, so the problem seems to be just on Windows' end on my main machine.