tcexperts77
asked on
Port 808 is being blocked
I am unable to open Port 808 on my Dell 2012 PowerEdge T110 ii) Server, which has Windows Server 2008 R2 Foundation as its O.S. A custom program I am trying to install needs port 808, but that is the ONLY port being blocked by this PC. I am using PFPortChecker by PortForward.com to check the ports -- it sees all other ports (that I wanted to open) as being open, except for port 808! It is not a router or ISP issue, because I can open that port on any other PC on the local network. I have also tried 3 different routers - none were successful. I even ran a new CAT6 cable to this PC. It is not a Windows firewall issue, because I have turned it off on both the public and private settings. I am thinking of installing another Ethernet card in this Server, because I also can't get this existing NIC (Broadcom NetXtreme Gigabit Ethernet) to connect faster than 100 Mbps. Any ideas?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
go into your advanced firewall configuration and open the port. Link Speed and Firewall are 2 different issues.
Port 808 is used by the NET.TCP port sharing service. It's unlikely you need this service, so you could potentially disable it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
[u]To Lockdown32: [/u] I should have said I am unable to port forward 808 to my Windows 2008 Server, no matter what LAN IP address I give my Server, yet I can port forward to other PCs on the network.
To David Johnson: Sorry, I should have also said that I already tried the advanced settings with no success.
To Adrein Decroy: The program I am installing needs NET.TCP. It's interesting that is the only port that is not open when I port forward to this PC. I should mention this program was running previously on this PC. After it failed a 9 days ago, I tried to reinstall it and was unsuccessful. Maybe this is why it failed (the port was not open any more)?
To Ian Arakel: I have run netstat and there is nothing listening on that port. My problem is the program I am trying to install apparently is listening on that port - only when I install it>>>>I need to verify that.
To David Johnson: Sorry, I should have also said that I already tried the advanced settings with no success.
To Adrein Decroy: The program I am installing needs NET.TCP. It's interesting that is the only port that is not open when I port forward to this PC. I should mention this program was running previously on this PC. After it failed a 9 days ago, I tried to reinstall it and was unsuccessful. Maybe this is why it failed (the port was not open any more)?
To Ian Arakel: I have run netstat and there is nothing listening on that port. My problem is the program I am trying to install apparently is listening on that port - only when I install it>>>>I need to verify that.
ASKER
I installed a new ethernet card yesterday and the speed issue was fixed immediately, but the port still was not seen as "open". I don't know if it was installing a new ethernet card or something else, but I was successful with installation of the software the first time I tried this (Saturday) morning! Running netstat -aon during the install first showed many lines with 808 port status listed as "time_wait". Now, running the command again after the program installation, shows the port with the status of "listening" and "established"! Running a port test through canyouseeme.org shows it is not being blocked anymore! I am not sure what really fixed the problem, but today was the first time I tried installing the software AFTER I installed the new ethernet card and that was the only change I made to the Server. The only thing I did differently was to run the netstat command DURING the install. Could that be what fixed it?
Hi there,
Any idea about netstat -ano | findstr 0.0.0.0 output before installation of the new ethernet card.
Moreover, could you post the current output of the above command.
The above command confirms the ports which the server is currently listening on.
This command would not affect the application installation.
Could you install the old card on some other lab server and try installing the application on that??
Any idea about netstat -ano | findstr 0.0.0.0 output before installation of the new ethernet card.
Moreover, could you post the current output of the above command.
The above command confirms the ports which the server is currently listening on.
This command would not affect the application installation.
Could you install the old card on some other lab server and try installing the application on that??
ASKER
Are you saying I should run the following command:
netstat -ano | findstr 0.0.0.0 output
I cannot install the old card anywhere else, because it is an integral part of the system board. I did some research on speed issues with this Broadcom Gigabit Extreme card on a 2012 Dell Poweredge server. Apparently the cause for the 100 Mbps speed was due to one of the 8 pins being bent (Gigabit speed requires all 8 pins?). I could have looked for a bent pin on this PC, but I thought it was just as easy - and a sure thing - to just put in another card.
netstat -ano | findstr 0.0.0.0 output
I cannot install the old card anywhere else, because it is an integral part of the system board. I did some research on speed issues with this Broadcom Gigabit Extreme card on a 2012 Dell Poweredge server. Apparently the cause for the 100 Mbps speed was due to one of the 8 pins being bent (Gigabit speed requires all 8 pins?). I could have looked for a bent pin on this PC, but I thought it was just as easy - and a sure thing - to just put in another card.
ASKER
It seems like I was at a "Catch-22" where I needed to install software that first needed to listen on a port before it could install, but firewall needed to have a program installed and listening before it would open that port? In any case, I do appreciate the info from everyone! Installing a new Ethernet card fixed the speed issue (and may have helped with the port forwarding).