Question : WINS and NETBIOS resolution issues

Hello,
I am having some strange issues on my network, with drive mappings and slow logins, and I've had a hard time pinning down the issue.  I have come to a couple of conclusions - clearing the DNS cache on workstations helps (ipconfig /flushdns) but doesn't fix it.  Now, when joining a PC to the domain, I am running into a WINS resolution issue that might be at the root of my network issues since we are relying on NETBIOS calls for some scripts and such.

The issue I'm having now is that when trying to join a computer to the domain, I can join using the DNS name of my domain (mydomain.local) but unable to join using just the NETBIOS of the domain (ex.  MYDOMAIN).  Obviously I could just join using the DNS name, but I'd lke to fix my WINS issue and be able to join via NETBIOS, that should hopefully fix some other problems as well.

Single Windows 2008 SBS server, running WINS and DNS.  Win XP Pro workstations.
DHCP scope set correctly, here's the result of ipconifg:

Windows IP Configuration
        Host Name . . . . . . . . . . . . : C175
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : mydopain.local

Ethernet adapter Local Area Connection:
        Connection-specific DNS Suffix  . : mydomain.local
        Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controller
        Physical Address. . . . . . . . . : 00-02-B3-3C-75-78
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.6.115
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.6.1
        DHCP Server . . . . . . . . . . . : 192.168.6.2
        DNS Servers . . . . . . . . . . . : 192.168.6.2
        Primary WINS Server . . . . . . . : 192.168.6.2
        Lease Obtained. . . . . . . . . . : Thursday, August 06, 2009 8:59:58 AM
        Lease Expires . . . . . . . . . . : Friday, August 14, 2009 8:59:58 AM

I ran netdiag, it passed all tests, though a few warnings, and seems to think it's Win2000?  Definitey XP machine.
.................................
    Computer Name: C175
    DNS Host Name: C175
    System info : Windows 2000 Professional (Build 2600)
    Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
    List of installed hotfixes :
        KB923561
        KB926139-v2
        KB926141
        KB929399
        KB936782_WMP11
        KB938464-v2
        KB939683
        KB941569
        KB943729
        KB946648
        KB950760
        KB950762
        KB950974
        KB951066
        KB951376-v2
        KB951748
        KB951978
        KB952004
        KB952069_WM9
        KB952287
        KB952954
        KB954154_WM11
        KB954459
        KB954550-v5
        KB954600
        KB955069
        KB955839
        KB956572
        KB956802
        KB956803
        KB957097
        KB958644
        KB958687
        KB958690
        KB959426
        KB959772_WM11
        KB960225
        KB960715
        KB960803
        KB961118
        KB961371
        KB961373
        KB961501
        KB963027
        KB967715
        KB968537
        KB969897-IE8
        KB970238
        KB971633
        KB973346
        Q147222

Netcard queries test . . . . . . . : Passed
Per interface results:
    Adapter : Local Area Connection
        Netcard queries test . . . : Passed
        Host Name. . . . . . . . . : C175.mydomain.local
        IP Address . . . . . . . . : 192.168.6.115
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.168.6.1
        Primary WINS Server. . . . : 192.168.6.2
        Dns Servers. . . . . . . . : 192.168.6.2

        AutoConfiguration results. . . . . . : Passed
        Default gateway test . . . : Passed
        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.
        WINS service test. . . . . : Passed

Global results:
Domain membership test . . . . . . : Passed
    Dns domain name is not specified.
    Dns forest name is not specified.

NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{DEEBDA1D-0B55-4B35-A3EB-C7EBC25A42E9}
    1 NetBt transport currently configured.

Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
    [WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.

Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed

Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{DEEBDA1D-0B55-4B35-A3EB-C7EBC25A42E9}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{DEEBDA1D-0B55-4B35-A3EB-C7EBC25A42E9}
    The browser is bound to 1 NetBt transport.

DC discovery test. . . . . . . . . : Skipped
DC list test . . . . . . . . . . . : Skipped
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Skipped
LDAP test. . . . . . . . . . . . . : Skipped
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
    No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Passed
    Service status  is: Started
    Service startup is: Automatic
    IPSec service is available, but no policy is assigned or active
    Note: run "ipseccmd /?" for more detailed information


What do you think I should check next? Thanks!

Answer : WINS and NETBIOS resolution issues

Well, figured this one out with Microsoft's help. Turns out my RAS-PPTP adapter was causing some trouble, my server was responding to IP 192.168.2.66 which was the address the server assigned to the RAS adapter.  Disabling Routing and Remote Access and re-enabling fixed the issue.