WAN sets up fine, so does LAN, but Win2K comp connected to the LAN doesn't see..



  • …a connection; just says media state unplugged.

    It is connected the the LAN port, and I've tried setting a static, and DHCP.

    LAN's IP is 192.168.1.1, and I'm using a straight through cable.

    I can connect a NAS running FreeNAS, which is also BSD based, and if that's connected to the LAN port, the PFsense and the NAS can ping each other.

    Why can't the win2K comp see the LAN?



  • use a crossover cable.



  • @GruensFroeschli:

    use a crossover cable.

    I tried a cross over cable as well, and the win 2K box still doesn't pick it up.

    I tried a cross over between my router and NAS, and they can no longer ping each other.



  • (multiple posts in different forums are not so cool…)
    you need to specify more information:

    i assume you mean the 192.168.1.1 is on the LAN of your pfSense.
    do you have a DHCP on the pfSense active?

    is your client as DHCP client configured?
    if not. what IP's are you using? subnet?

    if you plug your cable in: is the LED on?
    can you ping something else if you plug your PC directly into the modem/router before pfSense?



  • yes, 192.168.1.1 is on the LAN of pfSense.

    DHCP is active

    I've tried having the client, a computer running Windows 2000 set to DHCP, i've also tried a static address of 192.168.1.101 subnet 255.255.255.0 gateway of 192.168.1.1 and my ISP's dns servers

    When I connect a straight through cable from the LAN port to the win 2K computer; the NIC leds do not light up.

    When I connect a cross over from the LAN port to the win 2K computer; the NIC leds do not light up.

    When I connect a cross over from the LAN port to the NAS the NIC leds do not light up.

    When I connect a straight throug from the LAN port to the NAS the NIC leds do light up, and they can ping one another.



  • Sounds like the NIC on your Win2K host is dead or disabled in the BIOS.



  • @Cry:

    Sounds like the NIC on your Win2K host is dead or disabled in the BIOS.

    It's not dead, it works fine connected to a Cable Modem, or connected to a linksys router.

    I have netbios set to use whatever the DHCP server is set to.



  • Secondary question; should I be using a cross over or a straight through ethernet cable?



  • could you provide a diagram how you connect what?
    are you using a switch?
    you never mentioned something about a swich and thus i suspect you plug the NAS "and" the win2k machines on different unterfaces directly into the pfSense.
    if you do that: do you have rules on the additional interface that allow traffic
    –> are you using different subnets between the different interfaces?



  • @GruensFroeschli:

    could you provide a diagram how you connect what?
    are you using a switch?
    you never mentioned something about a swich and thus i suspect you plug the NAS "and" the win2k machines on different unterfaces directly into the pfSense.
    if you do that: do you have rules on the additional interface that allow traffic
    –> are you using different subnets between the different interfaces?

    No switch

    Same subnet for everything

    and from the pfSense config how do you set these rules?

    Here's a diagram:



  • @Majin:

    <–-snip--->
    When I connect a straight through cable from the LAN port to the win 2K computer; the NIC leds do not light up.

    When I connect a cross over from the LAN port to the win 2K computer; the NIC leds do not light up.

    When I connect a cross over from the LAN port to the NAS the NIC leds do not light up.

    When I connect a straight throug from the LAN port to the NAS the NIC leds do light up, and they can ping one another.

    this sounds either like the interface card in the Win 2K machine is not working (mentioned it since the NIC leds don't light up either way) or the Interface card settings in the Win 2K machine are set to auto for NIC speed and duplex settings - you might try setting the interface card settings to match the interface settings on the pfSense box to see if that resolves the issue.  You might also want to try placing a hub or switch between the pfsense box and the Win 2k box to see what that does as well - it might be "something" in the Win 2K box or pfsense box that just does not "like" the other interface.

    Just some ideas.

    gm…



  • What exactly is this dark "thing" at you pfSense? :D
    If you want one single subnet for everything you need to bridge the two interfaces which go to the w2k and the NAS.
    (making it pfSense interally into a Switch)

    You create rules under firewall–>rules.....
    But if you dont know that and are using pfSense as a firewall then i'm asking myself if this is the right product for you.



  • Straight through ethernet cable only works with Gbit to Gbit nic else you will need to use crossover.
    You only want to use 1 dhcp server for you system. Maybe it has to be your win2k server ( one old dog :D )
    what do use it for?

    The steps i would take.
    Bridge all opt nic's on pFsense to lan
    Set firewall rules.
    Activate dhcp on lan.
    Test them with a client.
    When that works you can try again with your servers.



  • @GruensFroeschli:

    What exactly is this dark "thing" at you pfSense? :D

    …and where does 'WiFi' stand for in your diagram?

    First get the cabling right which means that at least the link LEDs on the pfSense NIC and your host have to be lit. Maybe a cheap switch can help.
    Take the working link from your NAS and plug it into your W2k box. If the link does not come up then you have an issue with this machine's NIC or settings.
    Depending on the NIC and the software that comes along with it, there are settigs like Auto-MDI/-MDX or port speed that can be set.

    Once the link is up make sure that DHCP is activated on all interfaces needed. Is the device connected getting an IP in the range of the respective LAN subnet?
    What does "ipconfig /all" on the W2k machine output then?
    Ping the interface IP of pfSense on this subnet. If you have created the appropriate rules then try and ping other subnets.



  • the wifi stands for the "dark thing" on the back of the pfsense box, haha, it's supposed to be a wifi antenna.

    And ok, I'll fiddle with the NIC settings on the win 2K machine, but how do you adjusts the settings on the pfSense box? Keep in mind, I do not have access to the webui at this point, since I can't get a machine with a browser to "sense" it.

    Also just an fyi the NIC on the win2K box is an onboard one, should I maybe try a PIC NIC? as one of you mentioned, it may be an issue with the NIC, I'm just not sure why it would work connected to anything but the PFsense box.

    What are the default NIC settings for a PIC NIC in pfsense? 100, I'm sure, but is it half or full duplex?



  • Put an el cheapo switch between pfSense and the Win2k machine and look where the link lights come up. Track down the error on the other side then. Use straight cables in this setup.



  • ok, I've been busy, so sorry I haven't posted before this; anyhow, here's what I found through some fiddling.

    Same situation; pfsense sees my WAN, and gets a DHCP assigned IP just fine. the LAN, set to 192.168.1.1 doesn't see a link to my win2k machine. It will pass traffic between my NAS, which has a static IP 192.168.250. I tried connecting my linksys router to the LAN port on pfsense with a crossover cable, no link. I tried a straight through, and the linksys sees a full connection; but pfsense only shows link, no activity. If I disable DHCP on my linksys, it will get an IP from pfsense, 192.168.1.199, but the linksys, can not ping my pfsense at 192.168.1.1.

    Why won't pfsense link to ANYTHING besides a NAS?

    The only way I can configure pfsense is via a keyboard hooked up to pfsense, since a PC can't link to it, I don't have access to the webui of pfsense.



  • few other notes, all equipment is known to be good, it works fine when not connected to pfsense, so it's not a hardware issue. All NICs are set to autosensing.



  • I kind of suspect you are trying to have the same subnet on every interface.
    This will never work (not with pfSense and not with any other router).
    A Router ROUTES between subnets –> you have to use different subnets on different interfaces.
    If you want to use the same subnet you need to bridge Interfaces together.



  • that's how it's set up.

    Maybe I was a bit confused at first but here's my initial assumption. Each NIC in the PFsense box, would be like another port on a cheap linksys/netgear/dlink router.

    Here's what I've kinda got the impression of thus far, the LAN port on PFsense needs to be linked to a switch and the switch ports will be like the 1, 2, 3, 4 ports on a cheap linksys/netgear/dlink router.



  • Is this how it needs to be set up? With the opt ports on PFsense being for different subnets?



  • yes.
    or if you want on OPT1 the same subnet you need to bridge it to LAN



  • ok, and I bet bridging to the LAN is in the webui?

    Alright. so, ignoring other things, the win2K machine that I'd like connected to the LAN, why won't it work, no matter what I set the NIC to, auto, 100base half, or full duplex?

    the physical link light on the NIC won't even activate, no matter how I have the win2K's NIC set.



  • Got a cheep switch, and hooked that to the LAN port, and now everything is working great.

    Just want to thank everyone who replied to my thread.


Log in to reply