Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Trouble connecting to server across Point to Point T1 - DNS issues

Posted on 2009-05-03
6
Medium Priority
?
240 Views
Last Modified: 2013-12-05
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
0
Comment
Question by:captnapalm
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
6 Comments
 
LVL 4

Expert Comment

by:ValleyENT
ID: 24292398
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.
0
 

Author Comment

by:captnapalm
ID: 24292539
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
0
 
LVL 4

Assisted Solution

by:ValleyENT
ValleyENT earned 400 total points
ID: 24292552
You stated that you can ping the server by ip, but not the name, this would be a DNS issue of sorts. Try to set one of the systems to dynamic so it receives its ip via dhcp. If you are picking up the necessary information and everything works then it is a problem with your static information. It could also be an issue with your hardware routing.
0
Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Author Comment

by:captnapalm
ID: 24292587
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?

0
 

Author Comment

by:captnapalm
ID: 24296461
Any comments from the morning crew?
0
 

Accepted Solution

by:
captnapalm earned 0 total points
ID: 24296631
Fixed it with the help of an experienced network admin.

The issue is that my location A machines were using NetBIOS to talk to each other, but NetBIOS isn't made to connect through routers.

I had to add a zone for the server in DNS, and also add the DNS suffix to my XP machine. Now I'm connecting fine.

500 points go to my favorite NetAdmin.
0

Featured Post

Introducing the WatchGuard 420 Access Point

WatchGuard's newest access point includes an 802.11ac Wave 2 chipset, providing the fastest speeds for VoIP, video and music streaming, and large data file transfers. Additionally, enjoy the benefits of strong security as the 3rd radio delivers dedicated WIPS protection!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found here: http://www.experts-exchang…
Have you considered what group policies are backwards and forwards compatible? Windows Active Directory servers and clients use group policy templates to deploy sets of policies within your domain. But, there is a catch to deploying policies. The…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
In response to a need for security and privacy, and to continue fostering an environment members can turn to for support, solutions, and education, Experts Exchange has created anonymous question capabilities. This new feature is available to our Pr…

670 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question