Windows XP shares

[revil]

my new catch phase, "How the F*ck" works nicely here.

i set up a samba server listening on port 139, which is how windows used to work (i believe). but now windows xp uses port 445 for some reason. I confirmed this through some other docs and then I did a tcpdump which shows my xp box only trying to connect to port 445.

so what I want to know is how to get windows to use the old method of connecting to port 139.

anyone know?

[GilbertsGrape]

what is a somba server

[revil]

Originally posted by GilbertsGrape
what is a somba server
haha. sorry. i meant a samba (http://us1.samba.org/samba/samba.html) server.

[Joshua]

Ummm, you open up port 445 and tell windows to pretend it's on the other one. :)

[Joshua]

Here is your answer: Turn on Netbios.

http://support.microsoft.com/default.aspx?scid=kb;en-us;315267

The Advantages of Direct Hosting of SMB over TCP/IP
The information in this article applies to:
Microsoft Windows XP Home Edition
Microsoft Windows XP Professional
Microsoft Windows XP 64-Bit Edition

This article was previously published under Q315267
SUMMARY
This article discusses the advantages of the Windows XP strategy of removing NetBIOS transport for file and printer sharing traffic.

Windows XP supports file and printer sharing traffic by using the Server Message Block (SMB) protocol directly hosted on TCP. In earlier operating systems, SMB traffic requires the NetBIOS over TCP (NBT) protocol to work on a TCP/IP transport.
MORE INFORMATION
Removing the NetBIOS transport has several advantages, including:
Simplifying the transport of SMB traffic.
Removing WINS and NetBIOS broadcast as a means of name resolution.
Standardizing name resolution on DNS for file and printer sharing.
If both the direct-hosted and NBT interfaces are enabled, both methods are tried at the same time, and the first to respond is used. This allows Windows to function properly with operating systems that do not support direct hosting of SMB traffic. NetBIOS over TCP traditionally uses the following ports:
nbname 137/UDP
nbname 137/TCP
nbdatagram 138/UDP
nbsession 139/TCP

Direct hosted "NetBIOS-less" SMB traffic uses port 445 (TCP and UDP). In this situation, a 4-byte header precedes the SMB traffic. The first byte of this header is always 0x00, and the next three bytes are the length of the remaining data.

Use the following steps if you want to disable NBT and force all SMB traffic to be direct-hosted. However, be careful about implementing this setting because the Windows-based computer will be unable to communicate with earlier operating systems using SMB traffic:
Click Start, click Control Panel, and then double-click Network and Dial-up Connection.
Right-click Local Area Connection, and then click Properties.
Click Internet Protocol (TCP/IP), and then click Properties.
Click Advanced.
Click the WINS tab, and then click Disable NetBIOS over TCP/IP.
Click OK, click OK, and then click Close.
You can also disable NBT by using a DHCP server with Microsoft vendor-specific option code 1 ("Disable NetBIOS over TCP/IP"). Setting this option to a value of 2 disables NBT. For more information about using this method, refer to the DHCP Server Help file in Windows.

To determine whether NBT is enabled on a Windows-based computer, run a net config redirector or net config server command at a command prompt. The output shows bindings for the NetbiosSmb device (which is the "NetBIOS-less" transport) and for the NetBT_Tcpip device (which is the NBT transport). For example, the following sample output shows both the direct-hosted and the NBT transport bound to the adapter:
Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{610E2A3A-16C7-4E66-A11D-A483A5468C10} (02004C4F4F50)
NetBT_Tcpip_{CAF8956D-99FB-46E3-B04B-D4BB1AE93982} (009027CED4C2)

NetBT_Tcpip is bound to each adapter individually; an instance of NetBT_Tcpip is shown for each network adapter that it is bound to. NetbiosSmb is a global device and is not bound on a per-adapter basis. This means that direct-hosted SMBs cannot be disabled in Windows without completely disabling File and Printer Sharing for Microsoft Networks.

[revil]

um.... ya, i had already figured this out... but i forgot to say i did. whoops. but thanks for the help.