Question : Browsing problems on network

Let me try and paint the picture& We used to have two subnets 192.168.1.0 with SBS 2003 and Server 2003 servers and a remote subnet 192.168.1.0 with Server 2003 running AD  (well refer to them as sites A and B) which were connected together via diginet. We have now put a bridged wireless network in place which is working 100%, low latency etc. and we only have one subnet now 192.168.0.0 with servers still at the same locations. Heres my problem&. Users in B are able to contact the exchange server for example which is on the original A or any other source with no problems., sometimes for up to 6 hours then suddenly they are unable to connect. I am able to ping, telnet  etc anywhere on the site B but not browse etc. Likewise from B I can ping, telnet etc on A but not browse. Then after some time (hours) everything is back to normal. I have even dcpromod site Bs server out so all the dcs are in A but im not clued up enough to troubleshoot AD. I hope I have made some sense with all this. Any help will be much appreciated.

Answer : Browsing problems on network

Can you clarify what you mean by "browsing"?  You said pinging works, right?  So, it's not an IP problem, per-se..  I suspect you're just clicking on network neighborhood and trying to see machines on the far side of the link?

Can you clarify that?  

One thing to look for is messages on your servers, especially your domain controller(s) reporting "Master Browser elections"..  It sounds like you may have a machine thats missing a LOT of windows updates "stealing" the master browser function from your domain contoller, and/or maybe you have machines with duplicate names?

Also, in your inital post, you said both networks were originally 192.168.1.0.  Can you confirm what the network is now, and whether there's a router in there somewhere, or if you're really having a bridged WAN connection?
Thanks!