<div>
sounds like a DNS issue, how fast is the log in using a local user?
</div>


sounds like a DNS issue, how fast is the log in using a local user?

<div>
It takes 5 minutes to login.<br />

</div>


<div>
but my questions, does it take just as long to log in locally versus logging in to the domain?
</div>


but my questions, does it take just as long to log in locally versus logging in to the domain?

<div>
is your spanning tree set to port fast?
</div>


<div>
Your question was &quot;is your spanning tree set to port fast?&quot;<br />
I have no idea, how do I check that?<br />

</div>


Your question was "is your spanning tree set to port fast?"
I have no idea, how do I check that?


<div>
Login locally to workstation is quick, login to the server is about 5 minutes, is Windows 2003 SBS.
</div>


Login locally to workstation is quick, login to the server is about 5 minutes, is Windows 2003 SBS.

<div>
Sounds like a DNS issue, are you using the server as the DNS for the workstation or the ISP? if you are using the ISP then just change it to the server and that should resolve your issue.
</div>


Sounds like a DNS issue, are you using the server as the DNS for the workstation or the ISP? if you are using the ISP then just change it to the server and that should resolve your issue.

<div>
<div class="content wysiwyg-content">
Windows 2003 SBS environment and workstations are taking a long time to login. Takes 3 to 5 minutes.<br />
This is a 12 user network.<br />
I ran Wireshark. Seems like there are a lot of Broadcast ARP requests during login as well as Spanning-tree-(for-bridges<wbr />)_00 in my packet analysis.<br />
How can I limit or eliminate these at login to see if login is quicker.<br />
<br />
&nbsp;
</div>
</div>


Windows 2003 SBS environment and workstations are taking a long time to login. Takes 3 to 5 minutes.
This is a 12 user network.
I ran Wireshark. Seems like there are a lot of Broadcast ARP requests during login as well as Spanning-tree-(for-bridges)_00 in my packet analysis.
How can I limit or eliminate these at login to see if login is quicker.

 

Workstation takes a long time to log in - packet analysis lots of arp requests and spanning tree

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.

Networking Protocols

Networking hardware includes the physical devices facilitating the use of a computer network. Typically, networking hardware includes gateways, routers, network bridges, modems, wireless access points, networking cables, line drivers, switches, hubs, and repeaters. But it also includes hybrid network devices such as multilayer switches, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, ISDN terminal adapters and other related hardware.

Networking Hardware-Other

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).