# Device Connections **URL:** \ **Category:** Ignition\ **Created:** [January 15, 2025, 7:19pm UTC](https://forum.inductiveautomation.com/t/device-connections/100940 "2025-01-15T19:19:03Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![dick.willis](https://avatars.discourse-cdn.com/v4/letter/d/7ea924/32.png) [@dick.willis](https://forum.inductiveautomation.com/u/dick.willis)\ **Post date:** [January 15, 2025, 7:19pm UTC](https://forum.inductiveautomation.com/t/device-connections/100940/1 "2025-01-15T19:19:03Z")
I'm all of a sudden having difficulty with a device ... and I'm curious if maybe another device is misconfigured and using the same IP address. Our network team has detected traffic to the device on 102 (expected) and 44818 (unexpected) Anybody know of a way to dump the device connections info out to a text file so I can search through it? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 15, 2025, 7:26pm UTC](https://forum.inductiveautomation.com/t/device-connections/100940/2 "2025-01-15T19:26:22Z")
You could pair these two functions, to get a _guess_ about what in Ignition is connected to it, and then go in and double check your ports. The traffic logs should show you the source of the connection, though? > **[system.device.listDevices | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-device/system-device-listDevices)** > > Returns a dataset of information about each configured device. > **[system.device.getDeviceHostname | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-device/system-device-getDeviceHostname)** > > Returns the hostname of the device. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 15, 2025, 7:57pm UTC](https://forum.inductiveautomation.com/t/device-connections/100940/3 "2025-01-15T19:57:45Z")
44818 is the port for EtherNet/IP. Look for a Rockwell device sitting on the same IP. ---
**Author:** ![dick.willis](https://avatars.discourse-cdn.com/v4/letter/d/7ea924/32.png) [@dick.willis](https://forum.inductiveautomation.com/u/dick.willis)\ **Post date:** [January 15, 2025, 8:09pm UTC](https://forum.inductiveautomation.com/t/device-connections/100940/4 "2025-01-15T20:09:30Z")
Yup ... that's what I was thinking, too ... am now looking for a rogue entry ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 15, 2025, 8:11pm UTC](https://forum.inductiveautomation.com/t/device-connections/100940/5 "2025-01-15T20:11:59Z")
Are you sure the bad traffic is coming from Ignition? I'd be looking at a PCAP from the router showing the peer address that is using port 44818. ---
**Author:** ![dick.willis](https://avatars.discourse-cdn.com/v4/letter/d/7ea924/32.png) [@dick.willis](https://forum.inductiveautomation.com/u/dick.willis)\ **Post date:** [January 15, 2025, 10:19pm UTC](https://forum.inductiveautomation.com/t/device-connections/100940/6 "2025-01-15T22:19:59Z")
We did actually find an AB-driver device that WAS attempting to connect to the same IP address as the newly-installed Siemens device. We disabled the AB device ... and after some time waiting for reset/re-attempting the connection ... everything finished settling down and the Siemens device connection now looks good. Thanks for the help and interest.