Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Subnet make RDS not work in DNA

Status
Not open for further replies.

167734

Technical User
May 16, 2008
20
HK
Hi,

I get a problem. The connector symbol in the statusbar of OWS is not connected, hence name seraching failure.

The below are IP setting:-


1. OWS IP, Mask and Gate. 192.1.52.101 255.255.255.0 192.1.52.251
2. DNA IP, Mask and Gate. 192.1.40.167 255.255.255.0 192.1.40.21
3. PABX 192.1.40.19 255.255.255.0 192.1.40.24


Ping test result:
Ping from OWS to DNA OK.
Ping from DNA to OWS FAIL.
Ping from DNA to PBX OK.
Ping from OWS to PBX FAIL.
DNA, under MD110 support, version DNA52_SP3


Subnet in OWS is 52, that cannot be changed at customer site for security issue.

Any trick on this?
 
It's down to the network routers. They're allowing traffic in one direction but not another.
 
Hi Slash50,

Thanks. That mean this is not our DNA problem. I will discuss with customer.
 

If you use tracert instead of ping, this will tell you how far you can get across the network until it fails.

Wireshark the ping or tracert + you can see the device that is the problem where the send fails.

slash50 is correct, but it may make your case better to the customer. I am surprised they cannot already see this from their config and logfiles on their devices?

best parnum
 
Hi Parnum,

Thanks. I will search the link where there is wireshark program and start how to use it.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top