NetTalk Central

Author Topic: The public port number can not be 88  (Read 6482 times)

mikem01

  • Newbie
  • *
  • Posts: 1
    • View Profile
    • Email
The public port number can not be 88
« on: December 19, 2007, 10:15:58 AM »
Just getting started with webserver but I can't get beyond localhost.

I have set up Zone alarm to allow port 88 but when I try to change the router the full msg I get is:

The public port number can not be 88.  Because it will have a collision with the Wireless Router web service.

The router is not on a network - just sharing an internet conncetion between 2 PCs.

Using No-Ip to get an "IP address".

Can anyone see where I'm going wrong?

regards

Mike



Wolfgang Orth

  • Sr. Member
  • ****
  • Posts: 251
    • View Profile
    • oData Wolfgang Orth
Re: The public port number can not be 88
« Reply #1 on: December 19, 2007, 02:41:06 PM »
Mike,
apparently there is another device that uses port 88.

You have two options:
a) find that one and assign another port for this device if powssible or
b) assign another port to your webserver.... (seems the easier option)

and yes, c) replace ZoneAlarm with something else, like Comodo Personal Firewall (http://www.personalfirewall.comodo.com/)

I have half a dozend webserver running on one machine, and all are accessible from the internet, using those dynamic DNS-services like that NO-IP you mentioned. It was quite easy to setup all of them, so I know it has to work for you also!

bye
Wolfgang

Mike McLoughlin

  • Full Member
  • ***
  • Posts: 126
    • View Profile
    • Clarion Templates
    • Email
Re: The public port number can not be 88
« Reply #2 on: December 20, 2007, 12:31:38 AM »
Thanks Wolfgang.

Another thing I noticed while playing around in the router set up - the IP address it (Belkin) needed was the Default Gateway, not the PC's IP address.

This might help someone else struggling with security blocking them.

regards

Mike
Mike McLoughlin