Computer with the same name ?



  • hello,
    i have 12 pc windows xp ,and i will use pfsense for load balancing , when my (all) pc boot they have a error message "they existe a computer with the same name" ,when i shutdown pfsense i don't have this problem
    i seting my pfsense rule like this : http://doc.pfsense.org/index.php/Image:MultiWANrulesFirst.png

    i think pfsense duplicate netbios name ,i use pfsense in vmware 5.5, i install pfsense 1.0.1, the load balancing and fallover work fine but i have  netbios name problem, for a test i install (no upgrade ) pfsense 1-2 and i have the same problem
    perhaps :
    lan "netbios name 1"–> pfsense (bad nat , routing ?) --> "netbios name 1" but another ip --> lan :error netbios



  • I also have this, but it hasn't caused any problems so I haven't done anything about it, I am running under VMWare server on Windows server.  The actual message I get is a "duplicate name exists on the network"
    This has happened ever since I started using pfsense (just before Christmas last year).



  • with this problem it's imposible to use the shared printer and folder  :'(



  • I run large pfsense VMware labs in Workstation, Server, and ESX and have never seen this. There has to be something weird with how you're configuring things to cause such a message.

    How are your NIC's configured?  (what VMnets are they on and what do those connect to?)
    What exactly are you using it for?



  • The only iffy thing about my setup at the moment is that one of my modem subnets is running on the same lan as my inside LAN, I am planning to put in VLAN capable switches shortly, so I will know if that sorts it out.

    I am running with shared lan (suppress arp ) turned on in system - advanced at the moment.

    VMWare setup is as described in the VMWare on windows Wiki, and load balance pretty much as described in the multi-WAN wiki.



  • @cmb:

    I run large pfsense VMware labs in Workstation, Server, and ESX and have never seen this. There has to be something weird with how you're configuring things to cause such a message.

    How are your NIC's configured?  (what VMnets are they on and what do those connect to?)
    What exactly are you using it for?

    i have the 3 pfsense nic connecte at vmnet0(default bridged)



  • @Pootle:

    The only iffy thing about my setup at the moment is that one of my modem subnets is running on the same lan as my inside LAN, I am planning to put in VLAN capable switches shortly, so I will know if that sorts it out.

    This is the result of the dhcp/netbios daemon responding on the WAN/OPT1 interface even when not configured to.

    You can block this by adding a rule blocking port 67 sent to the WAN/OPT1 address on the WAN/OPT1 interface from the LAN subnet.

    An example of what Windows reports in the Application Event Log

    Event Type: Error
    Event Source: NetBT
    Event Category: None
    Event ID: 4321
    Date: xx/xx/2008
    Time: 7:00:00 PM
    User: N/A
    Computer: <computer name="">Description:
    The name "<computer name="">:20" could not be registered on the Interface with IP address 10.0.x.x. The machine with the IP address <wan address="">did not allow the name to be claimed by this machine.</wan></computer></computer>



  • Allow me to bring up this old thread, and add some more info on it.

    I have stumbled on this exact same problem, and it happens exactly when I change my default gateway from * to a failover queue. I just finished seting up failover on my pfSense router (running on a VMware machine), I route outgoing traffic with several rules. My last rule was directing traffic to * , so unrecognised traffic would be going out of WAN, and just by changing * to FailoverTC (which is a failover queue that uses two internet connections, if one is down, it will use the second one) my XP computers will start giving me errors that there is already a computer on the lan with that name.

    I was geting some errors on status -> system logs -> dhcp so indeed, it seemed that pfSense (which is also my DHCP server) was trying to assign twice a computer name and IP address to every computer.

    Now, I am not exactly sure on why the following fixes the problem, but it did for me. I just put a new rule on my WAN interface, the first one, for blocking Netbios traffic on my network. I would say that DHCP does not use the same ports Netbios uses, but oh well… I used to have this rule active some time ago because I was geting garbage on my logs, but now I had it disabled (no idea why). Just enabling it again makes my XP computers not whine any more about a duplicate computer on the network.

    Block - TCP/UDP - * - * - * - Netbios - *

    (Netbios is an alias than contains ports 137,138,139)



  • I had the same problem with my network. my two routers is connected to the backbone and to the pfsense. i was having duplicate name errors. i made 3 rules blocking 3 kinds of netbios on LAN, WAN1 and WAN2.

    i put he load balance rule below the 3 (netbios block) rules in the LAN. so far i have'nt found any problems..

    please post any problem you might think i encounter by doing this settings.


Log in to reply