# "port out of range" error on Digi connect Wi-sp using the real port driver

**URL:** <https://forums.digi.com/t/port-out-of-range-error-on-digi-connect-wi-sp-using-the-real-port-driver/15694>\
**Category:** Realport\
**Tags:** wi-sp, realport\
**Created:** [October 30, 2015, 2:30pm UTC](https://forums.digi.com/t/port-out-of-range-error-on-digi-connect-wi-sp-using-the-real-port-driver/15694 "2015-10-30T14:30:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![coling](https://avatars.discourse-cdn.com/v4/letter/c/9de053/32.png) [@coling](https://forums.digi.com/u/coling)\
**Post date:** [October 30, 2015, 2:30pm UTC](https://forums.digi.com/t/port-out-of-range-error-on-digi-connect-wi-sp-using-the-real-port-driver/15694/1 "2015-10-30T14:30:54Z")

</div>

I have setup a network that was working with 3 Digi connect wi-SP units. However, no the PC cannot interface with the serial port and in a terminal I just get “port out of range” repeated four times each time I try to connect to the realport on socket 771. reboots of both the devices and PC do not correct the issue. Any ideas to what is causing this error?

---

<div class="post-metadata">

**Author:** ![userid0](https://avatars.discourse-cdn.com/v4/letter/u/f6c823/32.png) [@userid0](https://forums.digi.com/u/userid0)\
**Post date:** [November 3, 2015, 10:18am UTC](https://forums.digi.com/t/port-out-of-range-error-on-digi-connect-wi-sp-using-the-real-port-driver/15694/2 "2015-11-03T10:18:33Z")

</div>

Is it possible some sort of firewall/antivirus is blocking access to the 771 port for the driver?

---

<div class="post-metadata">

**Author:** ![coling](https://avatars.discourse-cdn.com/v4/letter/c/9de053/32.png) [@coling](https://forums.digi.com/u/coling)\
**Post date:** [November 3, 2015, 2:33pm UTC](https://forums.digi.com/t/port-out-of-range-error-on-digi-connect-wi-sp-using-the-real-port-driver/15694/3 "2015-11-03T14:33:23Z")

</div>

It could be possible, but the configurations was working for a day and then stopped. I am guessing there is an issue with the realport driver somehow. Still have not found a fix.
