# USRP N200 connection problem

**URL:** <https://www.ruby-forum.com/t/usrp-n200-connection-problem/235715>\
**Category:** GNU Radio\
**Created:** [July 10, 2013, 8:52pm UTC](https://www.ruby-forum.com/t/usrp-n200-connection-problem/235715 "2013-07-10T20:52:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\
**Post date:** [July 10, 2013, 8:52pm UTC](https://www.ruby-forum.com/t/usrp-n200-connection-problem/235715/1 "2013-07-10T20:52:34Z")

</div>

Hello All,

I’ve been trying to connect a USRP N200 to a PC, however, I had no  
success.  
During some seconds, the connection is established, I do can ping the IP  
192.168.10.2 and find the device by uhd\_find\_devices command, but then  
it  
dies.  
The LEDs D and F remain on.

I could not even install the FPGA image into it.

I am using Gnuradio 3.6.4.1, Ubuntu 12.04 and Realtek Semiconductor Co.,  
Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 09).

Can somebody give me a hint?

Best Regards,

–  
Felipe F.  
Electrical Engineering Undergraduate Student  
Federal University of Campina Grande - UFCG - Brazil

Electrical Engineering  
San Diego State University

---

<div class="post-metadata">

**Author:** ![opa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/f475e1/32.png) [@opa](https://www.ruby-forum.com/u/opa)\
**Post date:** [July 10, 2013, 10:25pm UTC](https://www.ruby-forum.com/t/usrp-n200-connection-problem/235715/2 "2013-07-10T22:25:26Z")

</div>

> Federal University of Campina Grande - UFCG - Brazil
> 
> Electrical Engineering  
> San Diego State University
> 
> * * *
> 
> Discuss-gnuradio mailing list  
> [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
> [Discuss-gnuradio Info Page](https://lists.gnu.org/mailman/listinfo/discuss-gnuradio)  
> It’s very likely that you have DHCP still turned on on that port (via  
> network manager). This means Network Manager will “probe” for a DHCP  
> server  
> a few times before taking the port down, and you’re likely seeing  
> “success” only during the window when Network Manager is still looking  
> for  
> a DHCP server. Turn off the automatic address assignment on that  
> port, and make sure that it has a static address.