|It would appear to be a dns thing.|
how are the workstaitons getting to the groupwise subnet?
there does not appear to be a path.
from a workstation do a tracert to the groupwise server and post the results please.
Cisco vlan/routing training, in my opinion, promotes this vlan/subnet confusion. They train you on a super large network but don't explain that you can do vlans and don't have to do subnetting.
Ideally the entire network would have been you could have supernetted two class c's for 510 hosts
192.168.0.0 subnet mask 255.255.254.0 would have given you 192.168.0.0 - 192.168.1.255
Or a class b subnet. For example
172.16.0.1 subnet mask 255.255.0.0 would have provided a ip range of 172.16.0.1 - 172.16.255.254 [65534 hosts]
You would do no vlan routing. Server nics would be in all vlans whereas pcs would be divided up to smaller broadcast vlan domains. Everything would have been in a common subnet.
This way the servers are seen by all vlans but the pc vlans themselves don't talk ot each other.
The immediate solution to the issue is the correct DNS configuration. Servers should have host and ptr records as well as the workstations also. I would also suggest in Active Directory your present subnets should be listed under Sites and Services so AD knows about them.