Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Problem Connecting to some computers on a different subnet

Posted on 2008-10-16
9
Medium Priority
?
282 Views
Last Modified: 2010-04-18
Our VoIP and corporate networks are on seperate subnets.  We are having a problem with our VoIP server connecting to the Exchange server.  We can ping through from one subnet to the other from the routers and from the VoIP to the DC on the corporate side and vise versa but no other servers on the corporate side will talk with the VoIP server.  This was working then and there have not been any changes to routing or major changes to the serverr
0
Comment
Question by:ivwildbil
  • 5
  • 3
9 Comments
 
LVL 7

Expert Comment

by:cmarandi
ID: 22732766
How is your DNS setup?  Is there a forwarder on the DNS for each subnet?  

WINS running anywhere?  Maybe on one subnet and not the other, therefore causing DNS on one subnet to purge records because of decay.
0
 

Author Comment

by:ivwildbil
ID: 22733931
Name resolution is working fine.  The VoIP server is using one of the DCs for DNS resolution.
0
 
LVL 7

Expert Comment

by:cmarandi
ID: 22734181
Switch configuration... Are you using a managed switch?  On my managed switch I control the traffic types going between the two subnets... for example no icmp.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Accepted Solution

by:
ivwildbil earned 0 total points
ID: 22734855
That "MIGHT" be the case but I doubt it.  I'll double check but I don't think there is any filtering on the switches.

And we have resolve the problem by adding a static route to the VoIP network on the Exchange server.  The other servers are still not get to the VoIP network but they do not have a need to connect to that network.  The question now is why this stopped working.  One of the DCs has a static route but the other does not and it is routing to the VoIP network.
0
 
LVL 7

Expert Comment

by:cmarandi
ID: 22735502
Kind of an odd question:
Did you recently introduce a 2003 R2 DC where you had to upgrade the active directory to 31?
0
 
LVL 39

Expert Comment

by:ChiefIT
ID: 22742252
Could this be a Netbios issue??

Netbios broadcasts are not routeable, meaning it will not propogate over different subnets, through a VPN tunnel or across NAT.

Wins is routeable and can be used to bridge the two subnets. All you need is a WINS connection between your PDCe (as the domain master browser) and a server on the other side (as a master browser for that subnet).

I have seen netbios broadcasts work for a while, then just die for no appearant reason.

Here is a good article that explains the Browser service:
http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-us/net/chptr3.mspx?mfr=true

0
 
LVL 7

Expert Comment

by:cmarandi
ID: 22742710
I'm still baffled as to why it would suddenly change... That's why I was asking about the R2... When you introduce an R2, you have to upgrade the AD to 31 which changes the domain name scheme to must have the .com
So I wonder if a schema changed that is causing the VOIP to not communicate with the domain properly.
0
 

Author Comment

by:ivwildbil
ID: 22753937
R2 was not recently changed and there have been no major changes to AD architeture.
0
 
LVL 7

Expert Comment

by:cmarandi
ID: 22759986
No changes on Exchange?   Can you make sure the VOIP is configured properly and is using the correct Exchange settings?
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

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

On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses

783 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