Help: Ports open on Wifi, closed with ethernet

harmonicD

Reputable
Mar 3, 2015
9
0
4,510
I need to open up and allow Port 80 when connected via ethernet. I have the port forwarded in my router, and allowed in the windows firewall. Completely turning off the windows firewall also does not help.

Here is the kicker: This is only an issue when connected via LAN. If I plug USB Wireless Adapter and unplug the ethernet then everything works fine.

If I'm on LAN, then none of the ports are open. This has been driving me crazy! Any one have any ideas?

SETUP:

Running a D-LInk DIR-628. Ethernet is just plugged into LAN port 1.
A Fresh install in Win8 with nothing else installed yet except Chrome, VLC, and JRE8.
 
Solution
I don't have any idea yet on why it works on wifi and not on lan because you only seem to only answer a fraction of the questions I ask.

At this point you still have not specified if it is the server or a client that you are switching from wifi to lan, I don't know if the client machine is inside your network or outside. And there is other things I have not asked yet because I am still trying to get the basic information.

Please answer all of this:
Is the webserver hardwired or wireless?
Do you have static IP set up for the server?
What software are you using to host the web server (python, windows IIS, etc)?
What networking hardware is there (routers, switches, etc)
Are you certain the lan port you are using on the client is using...
Thank you for the speedy reply kanewolf.

The forwarded port has the LAN IP address. I should probably make an amendment though; Port forwarding isn't needed at all on Wifi, none of the ports are blocked. It's only when I connect to LAN that everything closes up.
 
What are you trying to do exactly, what computer has the webserver?

Is it the computer hosting the webserver that you are switching from wifi to Ethernet?
Is it a computer on the local network that is not accessing the server when connected to Ethernet or what exactly is going on?
 
It's a .jar file i'm trying to run. If connected via WiFi, everything works beautifully. If connected via LAN, I get a socket timeout error - because for some reason port 80 times out.
 


So it is the client computer accessing the .jar file that cant connect to the webpage on the server via Ethernet only via WiFi?
If it is all on your local network then port forwarding on router should play zero factor in this.

 


That's interesting! Any idea on why it can connect on WiFI no problem but times out when on LAN?

 
I don't have any idea yet on why it works on wifi and not on lan because you only seem to only answer a fraction of the questions I ask.

At this point you still have not specified if it is the server or a client that you are switching from wifi to lan, I don't know if the client machine is inside your network or outside. And there is other things I have not asked yet because I am still trying to get the basic information.

Please answer all of this:
Is the webserver hardwired or wireless?
Do you have static IP set up for the server?
What software are you using to host the web server (python, windows IIS, etc)?
What networking hardware is there (routers, switches, etc)
Are you certain the lan port you are using on the client is using the same subnet as the server?
Is there any sort of whitelisting that only allows certain IPs to view the web server?
 
Solution
Sorry about that boosted, I thought you were on to something in previous post about port forwarding not being the problem and went from there.

I'm afraid I cannot give you all of the information requested, but I'll answer what I can!


I am running a .jar that connects to a server using port 80. The server is NOT hosted on my machine or even anywhere near my network. I think you are right that port forwarding is not the issue here. I do know without a doubt that the server the .jar connects to is not blocking any incoming connections - so the problem is not that my LAN IP is blocked by the server.

I've tried white listing port 80 in the Windows Firewall with no luck. I also tried switching my network connection from Private (default Win8 connection - replaces the Home Network) to Public, and also tried disabling the firewall completely. Even with all of that, it cannot connect via LAN, but if I connect via WiFi, then there is no problem (and just in case, yes I have full internet access with LAN).

 
Can you explain what the jar file is coded to do, what is its purpose.
You see I assumed it was a javascript webpage you were hosting on your local network, now from your last post it sounds the .jar is a program that either displays or extracts data from someone else's webpage.

Is the network the problem machine on a home or a business network? Is there just the one router or an assortment of routers and switches?
Did you code the .jar or did someone else?
 
I did not code the Jar myself, but I know that it works well as it has been used on literally thousands of machines before (and works perfectly on my other Win8 Desktop on the same home network).

You are correct, the jar helps extract/display information from a server. I am running this on a simple home network.

Once again, I think the 'root' of the problem here is that the .jar is able to access and connect through port 80 when on Wifi no problem, but is unable to do so when connected via ethernet.

I just have one router (D-LInk DIR-628) connected to my modem, and am only using LAN port 1 to connect the problem machine.

I really appreciate your help with this! I didn't go to bed until 4am last night because this was driving me insane haha.
 
FYI unless it is something very offbeat special this is how normal internet traffic works.
Internet traffic has an outgoing and incoming port number.
In order to keep track of which computer is asking for what data it assigns each data request its own specific port number. So when Computer A wants a webpage it gives it a port of say 32100 and Computer B is in a Skype conference that its data connection is port 33433, and TV has a Netflix stream which is put on port 42124, etc, etc.
Now this is for solicited (you requested it) data, for unsolicited requests you need a specific port number and the router has to have port forwarding enabled because the router did not make a request for data on that port.
So in your case you are going to a HTTP address which its standard port is port 80, whoever hosts the webserver has to have port80 forwarded to their web server; the traffic sent back to you is on whatever port the router told it to send it back on. Thus for the kind of connection you are using there is no port forwarding required because your router is requesting the data and it assigned that data an incoming port.
 
Windows 8, currently set as Public but I changed it from Private (Private is windows 8's version of trusted Home Network). I also completely disabled the firewall and was still having the issue. Firewall is turned off on all stages (both public and private networks).
 
It's not a webpage, but a video streaming server that I am connecting to.

No configuration of the .jar was needed, so no settings for the jar that would affect how it performs on wifi or lan.
 
Can you obtain the IP address of the webserver? Then you could at least do a ping or nslookup command (in command prompt) of the IP address to see if you have a connection to it over lan.

Does the program have a folder with data in it, or is it just the .jar file and that is all?
I am wondering if when you first ran it, if it created a data file that had your settings in it, and so it got configured for just wifi.
At this point this is completely speculation because you did not say what the program is.

Is this to connect to a minecraft server?
 
It's just the .jar alone, no settings files have been created although that was a good idea!

It's not minecraft haha.

Basically it's a .jar hack to connect to NHL Gamecenter so I can watch their streams in French instead of English (yes, I am paying for gamecenter, but they only offer the eng feed in my area. The jar replaces the audio stream in VLC so I can get the FR).
 

TRENDING THREADS