Recently upgraded our DHCP/WINS server from 2k to 2k3. Everything seemed to go smooth, however I'm experiencing a computer browsing issue.
For some reason, the subnet that the DHCP/WINS server resides on (lets call it 60) can only browse other pc's on the same subnet. PC's on other subnets (61, 62, 63, etc) can view everything besides the 60 subnet.
All of the 60net servers are registered in WINS, no changes have been made besides the upgrade of the server itself.
I usually wouldnt care because I dont use browsing. However, our Symantec server is on the 60net and uses computer browsing to manually push updates. As of now, it can only push updates to pc's on the same subnet because those are the only ones listed. Ideas?
For some reason, the subnet that the DHCP/WINS server resides on (lets call it 60) can only browse other pc's on the same subnet. PC's on other subnets (61, 62, 63, etc) can view everything besides the 60 subnet.
All of the 60net servers are registered in WINS, no changes have been made besides the upgrade of the server itself.
I usually wouldnt care because I dont use browsing. However, our Symantec server is on the 60net and uses computer browsing to manually push updates. As of now, it can only push updates to pc's on the same subnet because those are the only ones listed. Ideas?
Facebook
Twitter