captnapalm
asked on
Trouble connecting to server across Point to Point T1 - DNS issues
My company is setting up a second location for a fulfillment center. We have a point to point T1 connected between the two locations. Cisco routers on either side.
Location A has 192.168.1.x addresses.
Location B has 192.168.2.x addresses.
All have 255.255.255.0 subnet.
Rules are set up on the router to direct traffic accordingly.
I have two servers, both with W2K Server. One is the DC. Both are in location A.
All workstations are XP Pro SP3 and have the DC's IP set as the primary DNS.
Location A workstations can easily see and log into both servers. Location B workstations could ping location A servers, but couldn't see names, couldn't join domain.
I set WINS on one of the location B workstations to the DC's IP, and that solved the problem of joining the domain. Now I can see and browse to all domain machines, and can log into shared resources for the DC without issues.
However, I can't connect to the second server across the PtP. I can see its name in my network places, but when I click on it I get 'The network path was not found." I can ping it by IP but not by name.
I should also mention that I just recently demoted this server from being a DC and made it a member of my current domain. All Location A workstations can connect to it just fine though. It's only across the PtP that there are issues.
I verified with the circuit vendor that the routers are wide open to all traffic between the two.
Is there a greater issue here in my configuration? It seems strange that my criteria for logging into servers are different locally than across the PtP.
Thanks
Location A has 192.168.1.x addresses.
Location B has 192.168.2.x addresses.
All have 255.255.255.0 subnet.
Rules are set up on the router to direct traffic accordingly.
I have two servers, both with W2K Server. One is the DC. Both are in location A.
All workstations are XP Pro SP3 and have the DC's IP set as the primary DNS.
Location A workstations can easily see and log into both servers. Location B workstations could ping location A servers, but couldn't see names, couldn't join domain.
I set WINS on one of the location B workstations to the DC's IP, and that solved the problem of joining the domain. Now I can see and browse to all domain machines, and can log into shared resources for the DC without issues.
However, I can't connect to the second server across the PtP. I can see its name in my network places, but when I click on it I get 'The network path was not found." I can ping it by IP but not by name.
I should also mention that I just recently demoted this server from being a DC and made it a member of my current domain. All Location A workstations can connect to it just fine though. It's only across the PtP that there are issues.
I verified with the circuit vendor that the routers are wide open to all traffic between the two.
Is there a greater issue here in my configuration? It seems strange that my criteria for logging into servers are different locally than across the PtP.
Thanks
Is the DC DHCP for Location B? Also, make sure you setup revers lookups in DNS for the 192.168.1.X and 2.X subnets.
ASKER
Everything is static. There's a firewall on each end that's a gateway and DHCP is running on those, but I use everything static.
I just added the reverse lookups in DNS for both, and updated the PTR record for my DC. Still having the same issue.
I also tried adding a new host for my second server, but that didn't change anything either.
thanks
I just added the reverse lookups in DNS for both, and updated the PTR record for my DC. Still having the same issue.
I also tried adding a new host for my second server, but that didn't change anything either.
thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Unfortunately I can't try this easily as one of the machines is 1 mile away and the other is a half hour drive. I'm connecting to them with VNC, and if the IPs change I'll lose my access to them until I can drive to each location.
Any idea why this would be an issue with one server and not the other?
Any idea why this would be an issue with one server and not the other?
ASKER
Any comments from the morning crew?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.