SmartSniff provides 3 methods for capturing TCP/IP packets: Raw Sockets (Only for Windows 2000/XP or greater): Allows you to capture TCP/IP packets on your network without installing a capture driver. This method has some limitations and problems. Xerox TCP/IP Port Monitor for Windows NT 4.x and 2000. Windows XP Windows 2000. Windows and Mac OS Compatible. Click the Run button in the Windows Start Menu. Type cmd in the Open prompt of the Run menu and click OK to launch a command prompt window. Type ipconfig /all at the command prompt to check the network card settings. The IP number and MAC address are listed by ipconfig under IP Address and Physical Address.

I was unable to get this to work to access (from a WIN XP machine) my Epson C80 that is connected to my Airport Extreme.
I notice this procedure was used to set up an Epson Stylus 760. However in step 6, it is indicated that a 'Hewlet Packard Jet Direct' is seleted. What does a H.P. device have to do with loading an Epson printer.

The HP bit is purely how the system interprates the bridge between the Ethernet and USB ports on the base station. It doesn't matter what sort of printer you're using, the JetDirect should still work.
The C80 is listed in Apple's compatibility table so all I can suggest is that you make sure 1)The printer shows up in the airport status page and 2)you're using the latest drivers.
If you're still having trouble, you can email me at duncan[at]itswakeling[dot]com and I'll see if I can come up woth anything ese to help.

This will only work under NT based systems (ie, NT, 2000, XP) not under w32 systems (ie, 95, 98, ME)
some times you are lucky to find on your printer software cd something that will allow you to access this from 98. Lexmark ship one and i THINK it can be downloaded off there web page
jameso
---
'The time has come,' the walrus said. 'To talk of many things..'

for 95,98,me
this is coming from memory and i havent used windows in years.. so i may be muddying it a bit..
add a printer..
tell it to use lpt1
then go to the printer control panel open the printer and in the ports section choose create new port, in the same way you created the port on xp/2k create the port here. check the box next to this port..
i think this works..

I am from Southamerica Chile, sorry for my bad english
I have a Ibook g4 OSX 10.3 whit Airport and win98 PC hooked to Ethernet entrance.
I can share correct my ADSL connection, but when I tried to see my printer Epson C82 from PC side I can't.
I go to printers, network, examine , I can see the Ibook but when I click in it, It's ask for the password I put all the password I have and none of it work.
How can I print in my Epson C82 connected to the USB port in Airport Extreme from my Win98 PC hooked by Ethernet to Airport Extreme?
Thanks for your help
Luis

I am having problems with this configuration. Instead of having the printer connected to the Airport via USB, we have it connected via ethernet (it's and old Apple LaserWriter). We have two Mac's connected and one Windows XP Box, The Mac's print fine to the printer, but the XP Box can not print to it, I have tried the instructions listed above, and variations on them, and it does not work. Does any body have any pointers for Getting the XP Box to print to the AppleLaser Writer, which is hooked up to an Airport Extreme via Ethernet?
thanks

I followed the instructions half-a-dozen times only to have the print fail each and every time. Now I have to hang my head in shame as I just realized that I had changed the IP address on my BaseStation.
Now printing from my XP laptop and Win2K tower works like magic.
Thank you waked1!

I followed the 7 points of your instructions exactly .. (except the ip of my airport extreme base station is 192.168.1.1, i just substituted this instead of 10.0.1.1) .. and i can not print from my PC as much as i try.
I have a winxp machine but am using an Epson Stylus Color 740 connected to my base station .. should this make any difference?
I can print to my epson from the ibook and powerbook i have over the airport network .. so i'm almost at a loss!!!

X force keygen autocad 2009 64 bit. Hi!
I followed the instructions precisely - and it just won't work. Not that I am surprised since it is Windows.. I am us a HP OfficeJet 5000 series - and I only want to use the printer from windows. Oh, and although it is not officially supported, printing from any mac works like a charm. There must be SOMEWAY to get this thing to print from Windows.
Anyone have any other ideas?
BB

This hint works great for most network-capable printers. But some printers that were never designed for network use (such as my HP photosmart 7960) may not appear on the list Windows offers you, even if the drivers are correctly installed. Here is another approach you can use:
1. Connect the printer directly to the Windows box and set it up.
2. Disconnect the printer from the Windows box.
3. Turn off your AE base station (disconnect power cord).
4. Plug the printer into the base station.
5. Turn the base station back on.
6. Begin the process of creating a new printer in Windows. Create a new port as described above (IP_10.0.1.1 or equivalent, with device type HP JetDirect). But don't actually perform the last step to create the printer. Instead, cancel once you have successfully created the port.
7. Return to the Windows printer list and select your printer. (It will be grayed out because it is offline.) Right-click and choose Properties. Choose the 'Ports' tab in the Properties dialog. Select the IP port you just created instead of the USB port that was originally selected. Exit the Properties dialog.
8. Right-click the printer and choose 'Take Online.' Now you should be able to print through your AEBS just fine. (At least I can with my photosmart.)
--
dal20402

I've tried all of the suggestions here (thanks very much!) but none of them work (argh!). I've got a PowerBook G4 running 10.4, with both an Airport Extreme and an Airport Express. I'm trying to print wirelessly from my XP notebook through the Airport Express. The IP of the Airport Express is 10.0.1.4, and I can ping this from the XP, so all is well there, but I just can't print to my Brother MFC-8640D!! Very frustrating. As with other forum members, I can print from my Mac to the printer through the Airport Express, but just not from my XP.

Thank you for this idea, Once the printer is connected via USB, simply disconnect it from the PC and re-connect it back to the AE
On your PC change the printer properties, select the ports tab and click on the port created (i,e., IP_10.10..)
Voilá
Problem solved - many thanks

This tip isn't working for me. I have a Deskjet 882C connected to the AirPort Extreme base station. I can print to it via my iBook, but the best I can do from XP is a stream of junk. I've followed the directions religiously and tried a few variations. I wonder if some update has broken this support.
---
--
John Faughnan
jfaughnan@spamcop.net
www.faughnan.com

Thanks to everybody who's posted hints on here to get me going! I had to do a slight variation mixing a few of them to get my XP laptop printing via Airport Express (G4 and Powerbook were both printing fine already).
-connect all the cables to airport express and turn it on, verify that all computers can access it - i.e. they should all have internet connectivity at this point
-open printers and faxes in XP Start menu
-click add printer
-select 'local printer attached to this computer' and deselect 'automatically detect..'
-click create a new port, choose standard TCP/IP
-enter 10.0.1.1 for printer name/IP address
(yes, to this point the instructions were exactly the same as the airport express doco)
-select Custom instead of standard device type
-select Raw LPR to port 9100
-select next, choose your appropriate printer when prompted (and name it), select finish
Sort of a combo of some of the other responses on this thread that finally worked for me. Good luck!

Just to make sure, you're using LPR, right? If so, what are you using as your queue name?

As of Apple Base Station 5.5.1 it seems the RAW port has changed to 9101.

I had problems connecting from Win 2000 to an Epson Color 740, and guessed port 9101 out of frustration. Then I found this article Print via Rendezvous and AirPort from Windows

(I also used the method where you connect the printer directly to Windows via USB, set it up, then re-connect the printer to airport and change the port settings in Windows. Don't know if this is required)

Thanks so much for posting this. I was going out of my mind. I got a new printer today and I was trying to use the old port (which had been working with my old printer) but it wasn't working. I changed it to 9101 and it worked immediately!

Hello-
Man, am I glad you posted! I've been pulling out my hair trying to get XP to print to my new HP printer connected via USB to Airport Extreme. I just upgraded to airport hardware 5.7. Never in a millon years would I have guessed that the setting changed from 9100 to 9101. I went into the printer properties/port/configure and manually changed 9100 to 9101 and I was able to print instantly! Two days I've been trying to get this to work. Thanks a MILLION!
By the way, I got Bonjour to work (used to be called Rendevous), but there is some kind of conflict between it and the Windows service SSDP that causes my task bar to hang for about 2 minutes when I first start Windows. I needed SSDP to detect my wireless internet, so I had to un-install Bonjour. Your post saved me, as I was finally able to set up the printer the old fashioned way. Thanks again.

WOW! It is 5 years later and this post comes out of no where to solve my problem instantly. Switching the port number did the trick on our Epson NX300 printing to an Airport Express.
Are we getting to see a pattern on printer manufacturers? I spend several days on and off trying to solve this on my own and with Apple and Epson.
I have book marked this site.
Thanks.

Thanks waked1 !
I found your post while on the road and in need..it works like a charm..
fhussar

If ur having trouble. Try this modification to the original instructions:
1. Make sure the printer is recognized by the base station.
2. Select 'Add a new printer' in Windows
3. Select 'Local Printer' in the dialog box (auto detect and install should be off), click next.
4. Choose 'Create a new port' and 'Standard TCP/IP Port'. Click next.
5. For the printer IP address, enter the address of the base station ie. 10.0.1.1. The port name will be filled automatically. Click next.
Here is where things needed to change..
6. Click the 'Custom' radio button
7. Click the 'Settings' radio button
8. Change the port from 9100 to 9101
9. click Ok to close the custom dialog box
10. click next to begin the process of selecting your printer
11. Choose your printer from the list and follow the rest of the prompts to install and configure the driver.
This worked like a charm for me with XP and a Samsung Laser ML-2010 on my AE.
Seems as if the port was the issue and changing it from 9100 to 9101 fixed everything.
Good luck!

Thanks millions. Worked for me! ..er.. I love you..

Many thanks.
Changing the port to 9101 worked a treat for XP to Canon iP4200 via Airport Extreme ('Apple Base Station V5.7')

This is an amazing tip! It worked for me! After 2 years of having to manually plug the printer USB cable from the Airport Extreme station to the PC (running Windows XP) USB port and back, I can now FINALLY just keep the USB cable plugged into my Airport Extreme station. And I can print via Airport Extreme, both from Windows XP, and from my Mac Laptop running Mac OS X Tiger. Argh.. why are such essentialls hidden somewhere in the hints page.. should be IN THE MANUAL. Yeah, yeah, I know, Windows and Mac come from two different companies and forces of the market cause them to inevitably hamper each other's products.

Earlier comments mention that you may need to update your port on your tcp/ip port for the printer. I couldn't figure out why this was failing. Turns out, for printing via RAW (like HP JetDirect) the port is now 9202.

Works perfectly now with XP and Parallels.

Thanks for the initial post

Do these settings work in conjunction with or override Bonjour? Bonjour seems to work very well when I connect my Windows XP machines to our two USB-connected HP LaserJet printers. I actually had to uninstall and reinstall Bonjour on one of those PCs, but it worked perfectly after that (evidently some kind of quirky conflict, which makes sense because I need to clean out that cluttered machine). In any event, please comment if someone knows whether these settings are essentially the same as Bonjour, whether they override those Bonjour settings, or whether they are totally separate (and if so, would there be a conflict?). Thank you.
Kind regards,
Jason Havens
Destin, FL

This all seems way too complicated. 90% of connection problems can be solved by installing Apples Bonjour for Windows.
http://support.apple.com/downloads/Bonjour_for_Windows

Has anyone gotten this to work via Windows Vista or Windows 7? They ask a couple more things in the last few steps.

Super! Worked fine on my Lenovo XP and Airport Express. I was looking for this solution for several months. Thank you!

I just followed the instructions for a Windows Vista laptop to connect to a HP printer on an Airport Express and it worked perfectly! Thanks!

No luck getting my HP Inkjet 5150 to print from my PC (Windows XP) via Airport Extreme. First downloaded Bonjour for Windows and went through the steps. When that didn't work, went through the steps described above in original post, changing the port from 9100 to 9101. My PC can see the printer and has it selected as the default printer, but no print jobs from PC are getting printed. I can print just fine through the Airport with my Mac laptop.

Even easier solution to print from windows. Navigate to Apple's support site, download Bonjour Print Services for Windows, install it, Run the Bonjour printer services for windows app that was installed into the Start menu, and select the printer you want to add/connect to.
The print services presents all the shared printers from AirPort/Mac systems in simple terms, and make installing the required printer ports seamless.

This article defines all the registry parameters that are used to configure the protocol driver, Tcpip.sys. Tcpip.sys implements the standard TCP/IP network protocols.

Original product version: Windows XP
Original KB number: 314053

Introduction

The TCP/IP protocol suite implementation for Windows XP reads all its configuration data from the registry. This information is written to the registry by the Network tool in Control Panel as part of the Setup process. Some of this information is also supplied by the Dynamic Host Configuration Protocol (DHCP) Client service if the DHCP Client service is enabled.

The implementation of the protocol suite should perform correctly and efficiently in most environments by using only the configuration information that is gathered by DHCP and by the Network tool in Control Panel. Optimal default values for all other configurable aspects of the protocols have been encoded in the drivers.

There may be some unusual circumstances in customer installations where changes to certain default values are appropriate. To handle these cases, optional registry parameters can be created to modify the default behavior of some parts of the protocol drivers.

Note

The Windows XP TCP/IP implementation is largely self-tuning. Adjusting registry parameters without careful study may reduce your computer's performance.

How to change parameters

Important

This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.

To change these parameters, follow these steps:

1. Click Start, click Run, and then type regedit in the Open box.
2. Locate the following registry key:
   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices
3. Click Add Value on the Edit menu, type the value that you want, and then set the value type under Data Type.
4. Click OK.
5. Quit Registry Editor.
6. Restart the computer to make the change take effect.

All the TCP/IP parameters are registry values that are located under one of two different subkeys of HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices:

• TcpipParameters
• TcpipParametersInterfacesID for Adapter

Windows Xp Tcp Ip Driver For Mac Windows 7

Note

ID for Adapter is the network adapter that TCP/IP is bound to. To determine the relationship between an Adapter ID and a network connection, view HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlNetwork{4D36E972-E325-11CE-BFC1-08002BE10318}<ID for Adapter>Connection. The Name value in these keys provides the friendly name for a network connection that is used in the Network Connections folder. Values under these keys are specific to each adapter. Parameters that have a DHCP configured value and a statically configured value may or may not exist. Their existence depends on whether the computer or the adapter is DHCP configured and whether static override values are specified. You must restart the computer for a change to take effect.

Standard TCP/IP parameters that you can configure by using Registry Editor

The following parameters are installed with default values by the Network tool in Control Panel during the installation of the TCP/IP components. You can use Registry Editor to modify them.

• DatabasePath

  • Key: TcpipParameters
  • Value type: REG_EXPAND_SZ - Character string
  • Valid range: A valid Windows NT file path
  • Default: %SystemRoot%System32DriversEtc
  • Description: This parameter specifies the path of the standard Internet database files (HOSTS, LMHOSTS, NETWORKS, PROTOCOLS). It is used by the Windows Sockets interface.

• ForwardBroadcasts

  • Key: TcpipParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0 or 1 (False or True)
  • Default: 0 (False)
  • Description: Forwarding of broadcasts is not supported. This parameter is ignored.

• UseZeroBroadcast

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_DWORD - Boolean
  • Valid range: 0 or 1 (False or True)
  • Default: 0 (False)
  • Description: If this parameter is set to 1 (True), the IP will use zeros-broadcasts (0.0.0.0) instead of ones-broadcasts (255.255.255.255). Most computers use ones-broadcasts, but some computers that are derived from BSD implementations use zeros-broadcasts. Computers that use different broadcasts do not interoperate well on the same network.

Optional TCP/IP parameters that you can configure by using Registry Editor

Generally, these parameters do not exist in the registry. You can create them to modify the default behavior of the TCP/IP protocol driver.

• ArpAlwaysSourceRoute

  • Key: TcpipParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0,1 (False or True)
  • Default: 0 (False)
  • Description: If you set this parameter to 1, TCP/IP transmits ARP queries with source routing enabled on Token Ring networks. By default, the stack transmits ARP queries without source routing first and retries with source routing enabled if no reply was received.

• ArpUseEtherSNAP

  • Key: TcpipParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0,1 (False or True)
  • Default: 0 (False)
  • Description: If you set this parameter to 1, TCP/IP transmits Ethernet packets using 802.3 SNAP encoding. By default, the stack transmits packets in DIX Ethernet format. It will always receive both formats.

• DefaultTTL

  • Key: TcpipParameters
  • Value type: REG_DWORD - Number of seconds/hops
  • Valid range: 1-255
  • Default: 128 for Windows XP
  • Description: This parameter specifies the default Time To Live (TTL) value that is set in the header of outgoing IP packets. The TTL determines the maximum time that an IP packet can live in the network without reaching its destination. It is effectively a limit on the number of routers an IP packet can pass through before it is discarded.

• EnableDeadGWDetect

  • Key: TcpipParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0,1 (False, True)
  • Default: 1 (True)
  • Description: If you set this parameter to 1, TCP uses the Dead Gateway Detection feature. With this feature, TCP requests IP to change to a backup gateway if it retransmits a segment several times without receiving a response. Backup gateways may be defined in the Advanced section of the TCP/IP configuration dialog box in the Network Control Panel.

• EnablePMTUBHDetect Mac 3200 chainsaw parts manual.

  • Key: TcpipParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0,1 (False, True)
  • Default: 0 (False)
  • Description: If you set this parameter to 1 (True), TCP tries to detect 'Black Hole' routers while doing Path MTU Discovery. A 'Black Hole' router does not return ICMP Destination Unreachable messages when it must fragment an IP datagram with the Don't Fragment bit set. TCP must receive these messages to perform Path MTU Discovery. With this feature enabled, TCP will try to send segments without the Don't Fragment bit set if several retransmissions of a segment are unacknowledged. If the segment is acknowledged, the MSS will be decreased and the Don't Fragment bit will be set in future packets on the connection. Enabling black hole detection increases the maximum number of retransmissions that are performed for a particular segment.

• EnablePMTUDiscovery

  • Key: TcpipParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0,1 (False, True)
  • Default: 1 (True)
  • Description: If you set this parameter to 1 (True), TCP tries to discover the Maximum Transmission Unit (MTU or largest packet size) over the path to a remote host. By discovering the Path MTU and limiting TCP segments to this size, TCP can eliminate fragmentation at routers along the path that connect networks with different MTUs. Fragmentation adversely affects TCP throughput and causes network congestion. If you set this parameter to 0, an MTU of 576 bytes is used for all connections that are not to computers on the local subnet.

• ForwardBufferMemory

  • Key: TcpipParameters
  • Value type: REG_DWORD - Number of bytes
  • Valid range: network MTU - some reasonable value smaller than 0xFFFFFFFF
  • Default: 74240 (sufficient for fifty 1480-byte packets, rounded to a multiple of 256)
  • Description: This parameter determines how much memory IP allocates to store packet data in the router packet queue. When this buffer space is filled, the router starts to discard packets at random from its queue. Packet queue data buffers are 256 bytes in length. Therefore, the value of this parameter must be a multiple of 256. Multiple buffers are chained together for larger packets. The IP header for a packet is stored separately. This parameter is ignored and no buffers are allocated if the IP router is not enabled.

• IGMPLevel

  • Key: TcpipParameters
  • Value type: REG_DWORD - Number
  • Valid range: 0,1,2
  • Default: 2
  • Description: This parameter determines how well the computer supports IP multicasting and participates in the Internet Group Management Protocol. At level 0, the computer provides no multicast support. At level 1, the computer can only send IP multicast packets. At level 2, the computer can send IP multicast packets and fully participate in IGMP to receive multicast packets.

• KeepAliveInterval

  • Key: TcpipParameters
  • Value type: REG_DWORD - Time in milliseconds
  • Valid range: 1 - 0xFFFFFFFF
  • Default: 1000 (one second)
  • Description: This parameter determines the interval that separates keepalive retransmissions until a response is received. After a response is received, KeepAliveTime again controls the delay until the next keepalive transmission. The connection is aborted after the number of retransmissions that are specified by TcpMaxDataRetransmissions are unanswered.

• KeepAliveTime

  • Key: TcpipParameters
  • Value type: REG_DWORD - Time in milliseconds
  • Valid range: 1 - 0xFFFFFFFF
  • Default: 7,200,000 (two hours)
  • Description: The parameter controls how frequently TCP tries to verify that an idle connection is still intact by sending a keepalive packet. If the remote computer is still reachable and functioning, the remote computer acknowledges the keepalive transmission. By default, keepalive packets are not sent. A program can turn on this feature on a connection.

• MTU

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_DWORD Number
  • Valid range: 68 - the MTU of the underlying network
  • Default: 0xFFFFFFFF
  • Description: This parameter overrides the default Maximum Transmission Unit (MTU) for a network interface. The MTU is the maximum packet size in bytes that the transport transmits over the underlying network. The size includes the transport header. An IP datagram can span multiple packets. Values larger than the default value for the underlying network cause the transport to use the network default MTU. Values smaller than 68 cause the transport to use an MTU of 68.

• NumForwardPackets

  • Key: TcpipParameters
  • Value type: REG_DWORD Number
  • Valid range: 1 - some reasonable value smaller than 0xFFFFFFFF
  • Default: 50
  • Description: This parameter determines the number of IP packet headers that are allocated for the router packet queue. When all headers are in use, the router begins to discard packets at random from the queue. This value should be at least as large as the ForwardBufferMemory value divided by the maximum IP data size of the networks that are connected to the router. This value must be no larger than the ForwardBufferMemory value divided by 256 because at least 256 bytes of forward buffer memory are used for each packet. The optimal number of forward packets for a particular ForwardBufferMemory size depends on the type of traffic that is carried on the network and will be somewhere between these two values. This parameter is ignored and no headers are allocated if the router is not enabled.

• TcpMaxConnectRetransmissions

  • Key: TcpipParameters
  • Value type: REG_DWORD - Number
  • Valid range: 0 - 0xFFFFFFFF
  • Default: 2
  • Description: This parameter determines the number of times that TCP retransmits a connect request (SYN) before aborting the attempt. The retransmission timeout is doubled with each successive retransmission in a particular connect attempt. The initial timeout value is three seconds.

• TcpMaxDataRetransmissions

  • Key: TcpipParameters
  • Value type: REG_DWORD - Number
  • Valid range: 0 - 0xFFFFFFFF
  • Default: 5
  • Description: This parameter controls the number of times that TCP retransmits an individual data segment (non-connect segment) before it aborts the connection. The retransmission timeout is doubled with each successive retransmission on a connection. It is reset when responses resume. The base timeout value is dynamically determined by the measured round-trip time on the connection.

• TcpNumConnections

  • Key: TcpipParameters
  • Value type: REG_DWORD - Number
  • Valid range: 0 - 0xfffffe
  • Default: 0xfffffe
  • Description: This parameter limits the maximum number of connections that TCP can have open at the same time.

• TcpTimedWaitDelay

  • Key: TcpipParameters

  • Value type: REG_DWORD - Time in seconds

  • Valid range: 30-300 (decimal)

  • Default: 0x78 (120 decimal)

  • Description: This parameter determines the time that a connection stays in the TIME_WAIT state when it is closing. As long as a connection is in the TIME_WAIT state, the socket pair cannot be re-used. This is also known as the '2MSL' state. According to RFC793, the value should be two times the maximum segment lifetime on the network. See RFC793 for more information.

    Note

    In Microsoft Windows 2000, the default value is 240 seconds. For Windows XP and Microsoft Windows Server 2003, the default was changed to 120 seconds for the IPv4 stack to increase performance. The default value for the IPv6 stack is 240 seconds.

• TcpUseRFC1122UrgentPointer

  • Key: TcpipParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0,1 (False, True)
  • Default: 0 (False)
  • Description: This parameter determines whether TCP uses the RFC 1122 specification for urgent data or the mode that is used by BSD-derived computers. The two mechanisms interpret the urgent pointer in the TCP header and the length of the urgent data differently. They are not interoperable. By default, Windows XP uses the BSD mode.

• TcpWindowSize

  • Key: TcpipParameters
  • Value type: REG_DWORD - Number of bytes
  • Valid range: 0 - 0xFFFF
  • Default: The smaller of 0xFFFF OR the larger of four times the maximum TCP data size on the network OR 8192 rounded up to an even multiple of the network TCP data size.
  • Ethernet default: 8760
  • Description: This parameter determines the maximum TCP receive window size of the computer. The receive window specifies the number of bytes a sender can transmit without receiving an acknowledgment. Generally, larger receive windows improve performance over high (delay * bandwidth) networks. For highest efficiency, the receive window must be an even multiple of the TCP Maximum Segment Size (MSS).

TCP/IP parameters that are configurable from the properties of a network connection

The following parameters are created and modified automatically by the connection properties interface through user-supplied information. You do not have to configure them directly in the registry.

• DefaultGateway

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_MULTI_SZ - List of dotted decimal IP addresses
  • Valid range: Any set of valid IP addresses
  • Default: None
  • Description: This parameter specifies the list of gateways to route packets that are not destined for a subnet that the computer is directly connected to and that do not have a more specific route. This parameter overrides the DhcpDefaultGateway parameter.

• Domain

  • Key: TcpipParameters
  • Value type: REG_SZ - Character string
  • Valid range: Any valid DNS domain name
  • Default: None
  • Description: This parameter specifies the DNS domain name of the computer. It is used by the Windows Sockets interface.

• EnableDhcp

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_DWORD - Boolean
  • Valid range: 0 or 1 (False or True)
  • Default: 0 (False)
  • Description: If this parameter is set to 1 (True), the DHCP client service tries to use DHCP to configure the first IP interface on the adapter.

• Hostname

  • Key: TcpipParameters
  • Value type: REG_SZ - Character string
  • Valid range: Any valid DNS hostname
  • Default: The computer name of the computer
  • Description: This parameter specifies the DNS hostname of the computer that will be returned by the hostname command.

• IPAddress

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_MULTI_SZ - List of dotted- decimal IP addresses
  • Valid range: Any set of valid IP addresses
  • Default: None
  • Description: This parameter specifies the IP addresses of the IP interfaces to be bound to the adapter. If the first address in the list is 0.0.0.0, the primary interface on the adapter will be configured from DHCP. A computer with more than one IP interface for an adapter is known as 'logically multihomed.' There must be a valid subnet mask value in the SubnetMask parameter for each IP address that is specified in this parameter.

• IPEnableRouter

  • Key: TcpipParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0 or 1 (False or True)
  • Default: 0 (False)
  • Description: Setting this parameter to 1 (True) causes the computer to route IP packets between the networks that it is connected to.

• NameServer

  • Key: TcpipParameters
  • Value type: REG_SZ - A space delimited list of dotted decimal IP addresses
  • Valid range: Any set of valid IP address
  • Default: None (Blank)
  • Description: This parameter specifies the DNS name servers to be queried by Windows Sockets to resolve names.

• SearchList

  • Key: TcpipParameters
  • Value type: REG_SZ - Delimited list of DNS domain name suffixes
  • Valid range: Any set of valid DNS domain name suffixes
  • Default: None
  • Description: This parameter specifies a list of domain name suffixes to append to a name to be resolved by the DNS if resolution of the unadorned name fails. By default, the value of the Domain parameter is appended only. This parameter is used by the Windows Sockets interface.

• SubnetMask

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_MULTI_SZ - List of dotted decimal IP addresses
  • Valid range: Any set of valid IP addresses.
  • Default: None
  • Description: This parameter specifies the subnet masks to be used with the IP interfaces bound to the adapter. If the first mask in the list is 0.0.0.0, the primary interface on the adapter will be configured by DHCP. There must be a valid subnet mask value in this parameter for each IP address that is specified in the IPAddress parameter.

Non-configurable TCP/IP parameters

The following parameters are created and used internally by the TCP/IP components. They should never be modified by using Registry Editor. They are listed here for reference only.

• DhcpDefaultGateway

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_MULTI_SZ - List of dotted decimal IP addresses
  • Valid range: Any set of valid IP addresses
  • Default: None
  • Description: This parameter specifies the list of default gateways to route packets that are not destined for a subnet that the computer is directly connected to, and that do not have a more specific route. This parameter is written by the DHCP client service, if enabled. This parameter is overridden by a valid DefaultGateway parameter value.

• DhcpIPAddress

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_SZ - Dotted decimal IP address
  • Valid range: Any valid IP address
  • Default: None
  • Description: This parameter specifies the DHCP-configured IP address for the interface. If the IPAddress parameter contains a first value other than 0.0.0.0, that value will override this parameter.

• DhcpNameServer

  • Key: TcpipParameters
  • Value type: REG_SZ - A space delimited list of dotted decimal IP addresses
  • Valid range: Any set of valid IP address
  • Default: None
  • Description: This parameter specifies the DNS name servers to be queried by Windows Sockets to resolve names. It is written by the DHCP client service, if enabled. The NameServer parameter overrides this parameter.

• DhcpServer

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_SZ - Dotted decimal IP address
  • Valid range: Any valid IP address
  • Default: None
  • Description: This parameter specifies the IP address of the DHCP server that granted the lease on the IP address in the DhcpIPAddress parameter.

• DhcpSubnetMask

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_SZ - Dotted decimal IP subnet mask
  • Valid range: Any subnet mask that is valid for the configured IP address
  • Default: None
  • Description: This parameter specifies the DHCP-configured subnet mask for the address that is specified in the DhcpIPAddress parameter.

• IPInterfaceContext

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_DWORD
  • Valid range: 0 - 0xFFFFFFFF
  • Default: None
  • Description: This parameter is written by the TCP/IP driver for use by the DHCP client service.

• Lease

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_DWORD - Time in seconds
  • Valid range: 1 - 0xFFFFFFFF
  • Default: None
  • Description: This parameter is used by the DHCP client service to store the time (in seconds) that the lease on the IP address for this adapter is valid for.

• LeaseObtainedTime

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_DWORD - Absolute time in seconds since midnight of 1/1/70
  • Valid range: 1 - 0xFFFFFFFF
  • Default: None
  • Description: This parameter is used by the DHCP client service to store the time that the lease on the IP address for this adapter obtained.

• LeaseTerminatesTime

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_DWORD - Absolute time in seconds since midnight of 1/1/70
  • Valid range: 1 - 0xFFFFFFFF
  • Default: None
  • Description: This parameter is used by the DHCP client service to store the time that the lease on the IP address for this adapter expires.

• LLInterface

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_SZ - NT device name
  • Valid range: A valid NT device name
  • Default: Empty string (Blank)
  • Description: This parameter is used to direct IP to bind to a different link-layer protocol than the built-in ARP module. The value of the parameter is the name of the Windows NT-based device that IP should bind to. This parameter is used in conjunction with the RAS component, for example.

• T1

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_DWORD - Absolute time in seconds since midnight of 1/1/70
  • Valid range: 1 - 0xFFFFFFFF
  • Default: None
  • Description: This parameter is used by the DHCP client service to store the time that the service will first try to renew the lease on the IP address for the adapter. To renew the lease, he service contacts the server that granted the lease.

• T2

  • Key: TcpipParametersInterfacesID for Adapter
  • Value type: REG_DWORD - Absolute time in seconds since midnight of 1/1/70
  • Valid range: 1 - 0xFFFFFFFF
  • Default: None
  • Description: This parameter is used by the DHCP client service to store the time that the service will try to renew the lease on the IP address for the adapter. To renew the lease, the service broadcasts a renewal request. Time T2 should be reached only if the service was not able to renew the lease with the original server.

All the NBT parameters are registry values that are located under one of two different subkeys of HKEY_LOCAL_MACHINEcomputerCurrentControlSetServices:

Windows Xp Tcp Ip Driver For Mac 64-bit

• NetbtParameters
• NetbtParametersInterfacesTcpip_ID for Adapter

where ID for Adapter represents the network adapter that NBT is bound to. The relationship between an Adapter ID and Network Connection can be determined by examining HKEY_LOCAL_MACHINEcomputerCurrentControlSetControlNetwork{4D36E972-E325-11CE-BFC1-08002BE10318}ID for AdapterConnection. The Name value in these keys provides the name that is used for a network connection used in the Network Connections folder. Values under the latter keys are specific to each adapter. If the computer is configured through DHCP, a change in parameters takes effect if the command ipconfig /renew is issued in a command shell. Otherwise, you must restart the computer for a change in any of these parameters to take effect.

Windows Xp Tcp Ip Driver For Mac Os

Standard NBT parameters configurable from Registry Editor

The following parameters are installed with default values by the Network tool in Control Panel during the installation of the TCP/IP components. They may be modified by using Registry Editor (Regedit.exe).

• BcastNameQueryCount

  • Key: NetbtParameters
  • Value type: REG_DWORD - Count
  • Valid range: 1 to 0xFFFF
  • Default: 3
  • Description: This value determines the number of times NetBT broadcasts a query for a particular name without receiving a response.

• BcastQueryTimeout

  • Key: NetbtParameters
  • Value type: REG_DWORD - Time in milliseconds
  • Valid range: 100 to 0xFFFFFFFF
  • Default: 0x2ee (750 decimal)
  • Description: This value determines the time interval between successive broadcast name queries for the same name.

• CacheTimeout

  • Key: NetbtParameters
  • Value type: REG_DWORD - Time in milliseconds
  • Valid range: 60000 to 0xFFFFFFFF
  • Default: 0x927c0 (600000 milliseconds = 10 minutes)
  • Description: This value determines the time interval that names are cached for in the remote name table.

• NameServerPort

  • Key: NetbtParameters
  • Value type: REG_DWORD - UDP port number
  • Valid range: 0 - 0xFFFF
  • Default: 0x89
  • Description: This parameter determines the destination port number that NetBT sends packets to that are related to name service, such as name queries and name registrations to WINS. The Microsoft WINS listens on port 0x89. NetBIOS name servers from other vendors can listen on different ports.

• NameSrvQueryCount

  • Key: NetbtParameters
  • Value type: REG_DWORD - Count
  • Valid range: 0 - 0xFFFF
  • Default: 3
  • Description: This value determines the number of times NetBT sends a query to a WINS server for a specified name without receiving a response.

• NameSrvQueryTimeout

  • Key: NetbtParameters
  • Value type: REG_DWORD - Time in milliseconds
  • Valid range: 100 - 0xFFFFFFFF
  • Default: 1500 (1.5 seconds)
  • Description: This value determines the time interval between successive name queries to WINS for a particular name.

• SessionKeepAlive

  • Key: NetbtParameters
  • Value type: REG_DWORD - Time in milliseconds
  • Valid range: 60,000 - 0xFFFFFFFF
  • Default: 3,600,000 (1 hour)
  • Description: This value determines the time interval between keepalive transmissions on a session. Setting the value to 0xFFFFFFF disables keepalives.

• Size/Small/Medium/Large

  • Key: NetbtParameters
  • Value type: REG_DWORD
  • Valid range: 1, 2, 3 (Small, Medium, Large)
  • Default: 1 (Small)
  • Description: This value determines the size of the name tables that are used to store local and remote names. Generally, Small is adequate. If the computer is acting as a proxy name server, the value is automatically set to Large to increase the size of the name cache hash table. Hash table buckets are sized as follows: Large: 256 Medium: 128 Small: 16

Optional NBT parameters configurable from Registry Editor

Windows Xp Tcp Ip Driver For Mac Installer

These parameters generally do not exist in the registry. They may be created to modify the default behavior of the NetBT protocol driver.

• BroadcastAddress

  • Key: NetbtParameters
  • Value type: REG_DWORD - Four bytes, little- endian encoded IP address
  • Valid range: 0 - 0xFFFFFFFF
  • Default: The ones-broadcast address for each network.
  • Description: This parameter can be used to force NetBT to use a specific address for all broadcast name-related packets. By default, NetBT uses the ones-broadcast address that is appropriate for each net (that is, for a network of 11.101.0.0 with a subnet mask of 255.255.0.0, the subnet broadcast address would be 11.101.255.255). This parameter would be set, for example, if the network uses the zeros-broadcast address (set by using the UseZeroBroadcast TCP/IP parameter). The appropriate subnet broadcast address would then be 11.101.0.0 in the earlier example. This parameter would then be set to 0x0b650000. This parameter is global and is used on all subnets that NetBT is bound to.

• EnableProxy

  • Key: NetbtParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0 or 1 (False or True)
  • Default: 0 (False)
  • Description: If this value is set to 1 (True), the computer acts as a proxy name server for the networks that NBT is bound to. A proxy name server answers broadcast queries for names that it has resolved through WINS. With a proxy name server, a network of B-node implementations can connect to servers on other subnets that are registered with WINS.

• EnableProxyRegCheck

  • Key: NetbtParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0 or 1 (False or True)
  • Default: 0 (False)
  • Description: If this parameter is set to 1 (True), the proxy name server sends a negative response to a broadcast name registration if the name is already registered with WINS or is in the proxy's local name cache with a different IP address. The hazard of enabling this feature is that it prevents a computer from changing its IP address as long as WINS has a mapping for the name. Therefore, it is disabled by default.

• InitialRefreshT.O.

  • Key: NetbtParameters
  • Value type: REG_DWORD - Time in milliseconds
  • Valid range: 960000 - 0xFFFFFFF
  • Default: 960000 (16 minutes)
  • Description: This parameter specifies the initial update timeout used by NBT during name registration. NBT tries to contact the WINS servers at 1/8th of this time interval when it is first registering names. When it receives a successful registration response, that response contains the new update interval to use.

• LmhostsTimeout

  • Key: NetbtParameters
  • Value type: REG_DWORD - Time in milliseconds
  • Valid range: 1000 - 0xFFFFFFFF
  • Default: 6000 (6 seconds)
  • Description: This parameter specifies the timeout value for LMHOSTS and DNS name queries. The timer has a granularity of the timeout value. Therefore, the actual timeout might be as much as two times the value.

• MaxDgramBuffering

  • Key: NetbtParameters
  • Value type: REG_DWORD - Count of bytes
  • Valid range: 0 - 0xFFFFFFFF
  • Default: 0x20000 (128 Kb)
  • Description: This parameter specifies the maximum memory that NetBT dynamically allocates for all outstanding datagram sends. After this limit is reached, additional sends will fail because the available resources are not sufficient resources.

• NodeType

  • Key: NetbtParameters
  • Value type: REG_DWORD - Number
  • Valid range: 1,2,4,8 (B-node, P-node, M-node, H-node)
  • Default: 1 or 8 based on the WINS server configuration
  • Description: This parameter determines what methods NetBT uses to register and resolve names. A B-node computer uses broadcasts. A P-node computer uses only point- to-point name queries to a name server (WINS). An M-node computer broadcasts first, and then queries the name server. An H-node computer queries the name server first, and then broadcasts. Resolution through LMHOSTS or DNS follows these methods. If this key is present, it will override the DhcpNodeType key. If neither key is present, the computer uses B-node if there are no WINS servers configured for the network. The computer uses H-node if there is at least one WINS server configured.

• RandomAdapter

  • Key: NetbtParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0 or 1 (False or True)
  • Default: 0 (False)
  • Description: This parameter applies to a multihomed host only. If it is set to 1 (True), NetBT will randomly select the IP address to put in a name query response from all its bound interfaces. Frequently, the response contains the address of the interface that the query arrived on. This feature would be used by a server with two interfaces on the same network for load balancing.

• RefreshOpCode

  • Key: NetbtParameters
  • Value type: REG_DWORD - Number
  • Valid range: 8, 9
  • Default: 8
  • Description: This parameter forces NetBT to use a specific opcode in name update packets. The specification for the NetBT protocol is somewhat ambiguous in this area. Although the default of 8 that is used by Microsoft implementations appears to be the intended value, some other implementations, such as those by Ungermann-Bass, use the value 9. Two implementations must use the same opcode to interoperate.

• SingleResponse

  • Key: NetbtParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0 or 1 (False or True)
  • Default: 0 (False)
  • Description: This parameter applies to a multihomed host only. If this parameter is set to 1 (True), NBT will only supply an IP address from one of its bound interfaces in name query responses. By default, the addresses of all bound interfaces are included.

• WinsDownTimeout

  • Key: NetbtParameters
  • Value type: REG_DWORD - Time in milliseconds
  • Valid range: 1000 - 0xFFFFFFFF
  • Default: 15,000 (15 seconds)
  • Description: This parameter determines the time that NBT waits before again trying to use WINS after it does not contact any WINS server. With this feature, computers that are temporarily disconnected from the network can proceed through boot processing without waiting to time out each WINS name registration or query individually.

NBT parameters configurable from the Connection Properties

The following parameters can be set through the Connection Properties from the Network Connections folder. You do not have to configure them directly.

• EnableDns

  • Key: NetbtParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0 or 1 (False or True)
  • Default: 0 (False)
  • Description: If this value is set to 1 (True), NBT queries the DNS for names that cannot be resolved by WINS, broadcast, or the LMHOSTS file.

• EnableLmhosts

  • Key: NetbtParameters
  • Value type: REG_DWORD - Boolean
  • Valid range: 0 or 1 (False or True)
  • Default: 1 (True)
  • Description: If this value is set to 1 (True), NBT searches the LMHOSTS file, if it exists, for names that cannot be resolved by WINS or broadcast. By default, there is no LMHOSTS file database directory (specified by TcpipParametersDatabasePath). Therefore, NBT takes no action. This value is written by the Advanced TCP/IP configuration under the Network tool in Control Panel.

• NameServer

  • Key: NetbtParametersInterfacesTcpip_ID for Adapter
  • Value type: REG_SZ - Dotted decimal IP address (for example,11.101.1.200)
  • Valid range: Any valid IP address
  • Default: blank (no address)
  • Description: This parameter specifies the IP address of the primary WINS server. If this parameter contains a valid value, it overrides the DHCP parameter of the same name.

• NameServerBackup

  • Key: NetbtParametersInterfacesTcpip_ID for Adapter
  • Value type: REG_SZ - Dotted decimal IP address (for example, 11.101.1.200)
  • Valid range: Any valid IP address.
  • Default: blank (no address)
  • Description: This parameter specifies the IP address of the backup WINS server. If this parameter contains a valid value, it overrides the DHCP parameter of the same name.

• ScopeId

  • Key: NetbtParameters
  • Value type: REG_SZ - Character string
  • Valid range: Any valid DNS domain name consisting of two dot-separated parts, or a '*'.
  • Default: None
  • Description: This parameter specifies the NetBIOS name scope for the node. This value must not start with a period. If this parameter contains a valid value, it will override the DHCP parameter of the same name. A blank value (empty string) will be ignored. Setting this parameter to the value '*' indicates a null scope and will override the DHCP parameter.

Non-configurable NBT parameters

The following parameters are created and used internally by the NetBT components. They should never be modified by using Registry Editor. They are listed here for reference only.

• DhcpNameServer

  • Key: NetbtParametersInterfacesTcpip_ID for Adapter
  • Value type: REG_SZ - Dotted decimal IP address (for example, 11.101.1.200)
  • Valid range: Any valid IP address
  • Default: None
  • Description: This parameter specifies the IP address of the primary WINS server. It is written by the DHCP client service, if enabled. A valid NameServer value will override this parameter.

• DhcpNameServerBackup

  • Key: NetbtParametersInterfacesTcpip_ID for Adapter
  • Value type: REG_SZ - Dotted decimal IP address (for example, 11.101.1.200)
  • Valid range: Any valid IP address
  • Default: None
  • Description: This parameter specifies the IP address of the backup WINS server. It is written by the DHCP client service, if enabled. A valid BackupNameServer value will override this parameter.

• DhcpNodeType

  • Key: NetbtParameters
  • Value type: REG_DWORD - Number
  • Valid range: 1 - 8
  • Default: 1
  • Description: This parameter specifies the NBT node type. It is written by the DHCP client service, if enabled. A valid NodeType value will override this parameter. See the entry for NodeType for a complete description.

• DhcpScopeId

  • Key: NetbtParameters
  • Value type: REG_SZ - Character string
  • Valid range: a dot-separated name string such as microsoft.com
  • Default: None
  • Description: This parameter specifies the NetBIOS name scope for the node. It is written by the DHCP client service, if enabled. This value must not start with a period. See the entry for ScopeId for more information.

• NbProvider

  • Key: NetbtParameters
  • Value type: REG_SZ - Character string
  • Valid Range: _tcp
  • Default: _tcp
  • Description: This parameter is used internally by the RPC component. The default value should not be changed.

• TransportBindName

  • Key: NetbtParameters
  • Value type: REG_SZ - Character string
  • Valid range: N/A
  • Default: Device
  • Description: This parameter is used internally during product development. The default value should not be changed.