Network Issues, ARP, RTPS, NDPS, DNS

I am having frequent 'glitches' when connecting to a device on the network. The attached diagram illustrates that these 'glitches' occur between the application server and 2 controllers (PLC). These 'glitches' cause havoc on the applications that run on the application server.

I ran wireshark on my domain controller, application server and workstation. The outputs from the application server are attached.

I have layer 2 switches throughout the network


simple-network-diagram.JPG
wireshark-application-server-pin.txt
adimitAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Netman66Commented:
The only thing that comes to mind is the binding order for the Application server.  It's a bit of a dicey issue since it's domain-joined and runs DNS.

Services generally bind to the NIC at the top of the binding order - in your case, the 192.203.0.11 NIC since it's part of the domain and DNS should service the domain-facing NIC.  I'm unclear by the drawing if any domain-based services are running on it.

However, the PLC communication may have issues if the application controlling them is bound to the NIC at the top of the binding order since it's not on the right network.

Try changing the binding order to put the 192.201.0.9 NIC at the top.  Reboot the server and test again.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
adimitAuthor Commented:
I'm a little bit worried about changing the binding order because both NIC's are of equal importance. I am having issues on both NIC's. Changing the binding order may not solve the problem

In answer to your question the diagram mentions that the domain controller has dns enabled. The application server does not have any dns, AD, or wins services running
0
Netman66Commented:
Post the content of the command: route print

Perhaps a simple static route might help, but I won't know until I see what the server knows about.

0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

pgm554Commented:
So the APP server is running as a workgrop (peer node) and not a member server?
0
adimitAuthor Commented:
static route attached


ip-route-app-server.JPG
0
Netman66Commented:
On the PLC NIC, unbind everything except TCP/IP.  Restart this server when you can after making the change.

This will stop this NIC from doing anything other than use IP.  

It may be an issue of interference with all the other services loaded.

You still need to ensure the domain-facing NIC is at the top of the binding order though.

0
adimitAuthor Commented:
the app node is running windows 2003 server and connected to two physically different networks (no vlan, two physically different layer 2 switches)

NIC1 is connected to a domain controller
NIc2 is not

The computer itself is a member of the domain.
i'm wondering if traffic from one network ever gets routed to traffic on the other network?
0
adimitAuthor Commented:
i will try netman's suggestions when I can stop production. For now is there something wrong with the addressing scheme?
0
pgm554Commented:
So your PLC's are talking to the APP server peer to peer?

That uses Netbios for discovery and you have WINS turned off.

Add an entry to the etc file of the WS and the PLC's of the APP server and see if that helps.

Remember Netbios is not routable.
0
pgm554Commented:
Your issues have nothing to do with the AD side of the network.
Your issues are on the work group side ,so concentrate on that.
0
pgm554Commented:
Here's some "lite" reading.

http://support.microsoft.com/kb/166159
0
adimitAuthor Commented:
how do you set the primjary transport in windows 2003 server
0
adimitAuthor Commented:
disabled netbios as per instructions but now I get the following error:

Windows cannot access the file gpt.ini for GPO
0
adimitAuthor Commented:
the error appears on the DC with netbios disabled
0
adimitAuthor Commented:
thank you Vee_Mod
0
adimitAuthor Commented:
There was an application that was causing the problems. The application was modified and all is well.

Please note:  Setting the primary transport actually had no significant effect in this instance. Implementing http://support.microsoft.com/kb/166159 actually made communication much worse. This is most likely due to the fact that the problematic application used both nics on the machine.

Thanks for all of your help
0
adimitAuthor Commented:
Although all suggestions were good and accurate. For some reason they did not help in this case, probably because my issues were caused by an application that used both nics on the machine with equal priority.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
OS Security

From novice to tech pro — start learning today.