W7 vmware 7 pfsense 2.0 want to acces sabnzb under windows
-
pfSense won't be blocking the port and your problem has nothing to do with pfSense.
To find ports that are in use enter netstat -an -p tcp.
-
@Cry:
pfSense won't be blocking the port and your problem has nothing to do with pfSense.
To find ports that are in use enter netstat -an -p tcp.
i tried that :
$ netstat -an -p tcp
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp4 0 0 192.168.1.1.443 192.168.1.102.51569 ESTABLISHED
tcp6 0 0 *.53 . LISTEN
tcp4 0 0 *.53 . LISTEN
tcp4 0 0 *.80 . LISTEN
tcp4 0 0 *.443 . LISTENso most ports are free and still get error also other program camd for dvb-s under windows also get winsock error 10054
-
I'd take your problem to a forum or list for sabnzb.
-
@Cry:
I'd take your problem to a forum or list for sabnzb.
i think it is because vmware
when i stop pfsense problem stays did i something wrong with the adapter settings ?
when install program on other pc it works direct with no problem
also the acamd server for dvbviewer does not work now.
-
Are you referring to another VMWare Guest or the VMWare Host? Either way it is nothing to do with pfSense and this is not the right place to get help.
The problem is likely to be with Windows, so I'd try a Windows forum.
-
@Cry:
Are you referring to another VMWare Guest or the VMWare Host? Either way it is nothing to do with pfSense and this is not the right place to get help.
The problem is likely to be with Windows, so I'd try a Windows forum.
maybe not with pfsense but problem is started when i installed vmware workstation 7 with pfsense on my windows 7 pc
so i thought maybe there is some one here with the same problem ./
something in vmware settings ???
-
What you install in a Guest can't impact the Host - that's the point of virtualisation.
Your problem may be with VMWare, or something else with your Windows install. It has nothing to do with your pfSense install.
-
@Cry:
What you install in a Guest can't impact the Host - that's the point of virtualisation.
Your problem may be with VMWare, or something else with your Windows install. It has nothing to do with your pfSense install.
when i change to 127.0.0.1:8085 it works on host only not other pc's in lan do i have to route something ?
also other program on host in windows want to connect to wan but can not reach there
-
If you want it accessible to other hosts, don't use loopback or 127.0.0.1.
Ensure that the correct default gateway is set. As we don't know what your network looks like we can't tell you what that should be.
-
@Cry:
If you want it accessible to other hosts, don't use loopback or 127.0.0.1.
Ensure that the correct default gateway is set. As we don't know what your network looks like we can't tell you what that should be.
how do you mean ? gateway for host ?
lan 192.168.1.1 is gateway for other pc's
i can not find a port that works on this ip
-
how do you mean ? gateway for host ?
lan 192.168.1.1 is gateway for other pc's
You said that
@Gino:also other program on host in windows want to connect to wan but can not reach there
Which suggests that you haven't correctly configured the route to the Internet, but we don't know what your network looks like. We know you have pfSense on a VM, but we don't know if or how it relates. If that Windows computer is also on the 192.168.1/24 network then 192.168.1.1 is the right default gateway.
Please provide a diagram showing how your network is configured, including IP addresses for each interface and treat virtual hosts as if they were physical (but mark that they are VMs and what physical host they run on).
i can not find a port that works on this ip
That is off topic here - it's a VMWare/Windows problem and isn't one I'm going to tackle in this thread - it's confusing enough already.
-
problem solved
on the wan sides in windows windows services was on
now it works normaly
only the the virtual machine does not start automatically when i reboot pc it stops in workstaion 7
