• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 527
  • Last Modified:

Can't browse to our second subnet

Out domain has two subnets; 100.x and 200.x.  We have one physical Domain controller in each subnet.  The HQ office is in the 100.x subnet and the application servers are in the 200.x subnet.  About a week ago, we replace the virtual DC in the 200.x subnet with a physical server because if we have a VMWare issue, then the DC goes down.  That promotion and demotion went as planned and things worked well for about 5 days.  Then for not apparent reason, we lost the capability to browse from the 100.x subnet to the 200.x subnet.  If I open a windows explorer, all I see are systems in the 100.x subnet.  

I can RDC by name and IP address the servers on the 200.x subnet.
I can DameWare by name and IP address the servers on the 200.x subnet.
I can use the run window to route to the servers on the 200.x subnet. (\\servername\c$)

If I remote to the 200.x side, I have the same problem.  I can only see the servers on the 200.x side.
0
sfletcher1959
Asked:
sfletcher1959
  • 3
  • 2
1 Solution
 
xDUCKxCommented:
What's the subnet mask?

Was the VMHost acting as a network bridge between the two subnets?  Did it have a NIC attached to both subnets?

Is it only this new server that can't connect to the 100.x subnet or are you having a global outage across all devices?

Quick fix:

route print
verify the interface (0x1 or 0x2)
route add xxx.xxx.100.0 mask 255.255.255.0 <default Gateway> Metric 10 IF 2

Open in new window

0
 
sfletcher1959Author Commented:
It is a global outage.  Nothing in the 100.x subnet can browse the 200.x subnet and visa versa.

Nothing in the router changed, so not sure where you are looking to put these route statements.
0
 
xDUCKxCommented:
Put the route statement on the physical host that you just brought online.  If you're using DHCP to hand out IP Addresses, you can add option 249 Classless Routes to hand out the Route info to your clients.

If you're using a 24 bit subnet mask (255.255.255.0) then you'll need to have a route somewhere that can direct the traffic.
0
 
sfletcher1959Author Commented:
One other thing, our previous DC's were 2003.  The new physical box is the first 2008 R2 DC.   The forest prep was done and all schema roles upgraded.

I have forced replication (repadmin /syncall /AdeP)

I have verified both DC are GC's for their subnets

I have flushed DNS and rebooted both DC's

If I do AD search, it see's all objects on both sides.

Forward and Reverse DNS servers see all the objects

The Master browser shows both DC's as either the primary or backup browser
0
 
sfletcher1959Author Commented:
Thanks for the help.  It turned out the Browser Service was hung.  It hadn't failed, but it wasn't working either.  I stopped and restarted the service and it began working.  Not sure why it didn't work with a restart, but it is working now.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now