UNSOLVED

Dodomac

updated

5 years ago

D

Dodomac

6 Posts

0

1526

July 5th, 2021 06:00

AW3420DW, MacBook Pro loses IP address?

I purchased a AW3420DW 34" (arrived) and a new AW laptop and accessories (hasn't arrived yet).

I am currently using my Apple MacBook Pro 2013.

Each time I plug in the monitor (DP via thunderbolt) I either pick up basic resolution of the monitor but lose the ethernet IP address and cannot renew it (even after removing monitor and restarting everything), or the monitor is not picked up.

I had to leave the computer over night before it was able to see the ethernet again.

I ran a standalone diagnostics on the monitor and went through the different colored screens successfully.

For my Mac model I have the following ports:

  • MagSafe 2 power port
  • Two Thunderbolt 2 ports (up to 20 Gbps) - (on another site I found: 1x 4K & 2x 1440p both @60hz)
  • Two USB 3 ports (up to 5 Gbps)
  • HDMI port
  • Headphone port
  • SDXC card slot
  • Apple Thunderbolt to FireWire Adapter (sold separately)
  • Apple Thunderbolt to Gigabit Ethernet Adapter (sold separately)

Should I give in and wait for my new laptop to arrive or is there a way to make this work?

  • Dodomac

    6 Posts

    1325

    0

    Posted July 5th, 2021 06:00

    Can't see a way to edit my question, so here is some more information.

    I am using Windows10 Home edition on my boot camped MacBook Pro 2013.

  • Dodomac

    6 Posts

    1295

    0

    Posted July 6th, 2021 12:00

    Hi, the network problem only occurred after I plugged the monitor in. I never had this problem in the past 10 years of using this mac. I twice tried to use the monitor and the problem happened twice. That is how I know it is related. Yes you can argue it is a coincidence but that wouldn't be a strong argument.

  • Mary G

    6 Operator

    20095 Posts

    1299

    0

    Posted July 6th, 2021 12:00

    Here's the manual and other info Support for Alienware AW3420DW | Documentation | Dell US

    But your question is about the network connection on the mac. Doesn't have anything to the monitor.

    PS To edit your post click on the 3 dots in the upper right corner of your post.

  • Vanadiel

    8 Professor

    7088 Posts

    29677 Points

    1278

    0

    Posted July 6th, 2021 18:00

    It has likely to do with the thunderbolt connection. 

    Try HDMI and see if the problem goes away.

  • speedstep

    11 Legend

    46969 Posts

    1272

    0

    Posted July 6th, 2021 20:00

    Use Gigabit USB3 adapter.

    Thunderbolt is the issue.

  • Dodomac

    6 Posts

    1252

    0

    Posted July 7th, 2021 14:00

    Will thunderbolt behave the same on my new AW laptop (that hasn't arrived yet)? Is the recommendation to stay clear of thunderbolt and favour HDMI? I know this hasn't been suggested but thought I would ask all the same.

    It's taking me 2 days to get the Ethernet back. Swapped everything, cables, switches, even reset the router to factory settings, nothing worked, then suddenly it came back. So purely a configuration problem.

  • speedstep

    11 Legend

    46969 Posts

    1250

    0

    Posted July 7th, 2021 14:00

    Thunderbolt 3 and 4 aka USB4 have the same issue.

  • r72019

    8 Professor

    5344 Posts

    1228

    0

    Posted July 7th, 2021 23:00


    @Dodomac wrote:

    Will thunderbolt behave the same on my new AW laptop (that hasn't arrived yet)? Is the recommendation to stay clear of thunderbolt and favour HDMI? 



    speedstep wrote: 

    Thunderbolt 3 and 4 aka USB4 have the same issue.



    No, I believe this is a fixable problem with your Mac improperly recognizing and then assigning Ethernet over Thunderbolt when the Monitor is connected via TBH 2.  TBH can be used for ethernet too, but that's not what you want to do here. 

    To fix, try going to system preferences / network preferences, and then make Thunderbolt Ethernet inactive and I believe this should solve your issue. 

    I don't think this is a generally applicable problem with the monitor or connection type, so I wouldn't worry about it.