Quote:
Originally Posted by ilesterg
That's right, can you give a logical layout of your network (local to remote UDP), then how exactly you implemented this? (VMs and the like)
|
I could not understand what kind of information you are expecting. Apologize for that. Still, will try to explain my setup.
Issue & its history:
We want to establish a jdbc connection to the MSSQL DB server. That was failing. On looking into the driver's source, we found that the jdbc driver was sending an UDP packet to the MSSQL DB Server. (When we send a UDP packet with a pre-defined data to the MSSQL Server, it will respond with some connection information.) After using wireshark, we came to the conclusion that, the udp packet is not received at the server side. Then we started narrowing down by trying from other machines, writing a custom UDP server and so on.
Setup:
We have two VMWare ESX Servers. One has SLES and RHEL and that too have the same issue. But, due to a hardware problem, we could not access them. For now, we'll ignore it.
On the another ESX server, we have two VMs (VM1 and VM2). Both are running RHEL. All the other settings are default. And both of the VMs use Bridged networking. (So, they have individual IPs.) And in the same network, I have a linux UDP server (Physical machine). And we have an MSSQL DB Server running in our test network. (Different subnet altogether and this is also on an ESX Server).
From VM1 and the ESX Server, I could send the UDP packet to both my physical UDP Server and the MSSQL and I could get proper responses.
From VM2, the behaviour is as mentioned in
my eariler comment. This is the same behavior when I try to reach both of the machines. (MSSQL and my test UDP server)
Thanks for your response. In case you need more clarity, will try to provide them.
