- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Networking
- >
- procurve switch 2524
Networking
1753741
Members
4532
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2002 12:31 AM
тАО05-06-2002 12:31 AM
Is there a known problem about printing from a Novell server to a HP print server? The rest of network is working good (with sw 2524).any idea ?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2002 08:37 AM
тАО05-06-2002 08:37 AM
Solution
Yep. Spanning tree kills you.
http://www.hp.com/rnd/support/faqs/23xx_25xx.htm
Q: When I power on my PC, I get the message "a file server could not be found." How do I fix that?
This is a well-known issue given the following situation:
The PC is directly connected to a switch
The PC is running Novell's VLMs or Client32
The switch has Spanning Tree Protocol (STP) enabled
In this situation, when the directly connected PC is powered on, the switch senses linkbeat on that port. This causes the switch to go through the four Spanning Tree states: blocking, listening, learning, and forwarding. It takes 30 seconds for the switch to complete that sequence and begin forwarding packets to and from that port. During those 30 seconds, Novell sends 3 requests for a server, then stops looking. By the time Spanning Tree completes its job, Novell reports that "a file server could not be found."
There are several workarounds available:
Disable Spanning Tree on the switch (if Spanning Tree is not needed, i.e. no loops in the network topology).
For VLMs, add a "pause" just after calling VLM.EXE in STARTNET.BAT. When the user reboots a PC, have them wait at least 30 seconds before continuing the sequence. This workaround is documented on Novell's Knowledgebase (www.support.novell.com, search for document 2920460).
For Client32, add a registry entry in the PC, as documented on Novell's Knowledgebase (search for document 2925582).
In the Fall of 1998, HP released switch firmware (version C.05.07 or greater) with an enhancement to resolve this timing problem between Novell and STP. The enhancement allows users to configure Spanning Tree so that it does not go through the 4 states, on a port-by-port basis. Instead, for those configured ports, Spanning Tree will immediately begin forwarding packets to and from the port. This allows Novell clients to communicate with the server as soon as the network card (NIC) is enabled. After that, the switch continues to listen for and send Spanning Tree packets on those configured ports. This protects the user who might inadvertently connect a hub or switch to that port and create a network loop???Spanning Tree will detect the loop after a short time, since the port listens for and sends STP packets on that port.
Ron
http://www.hp.com/rnd/support/faqs/23xx_25xx.htm
Q: When I power on my PC, I get the message "a file server could not be found." How do I fix that?
This is a well-known issue given the following situation:
The PC is directly connected to a switch
The PC is running Novell's VLMs or Client32
The switch has Spanning Tree Protocol (STP) enabled
In this situation, when the directly connected PC is powered on, the switch senses linkbeat on that port. This causes the switch to go through the four Spanning Tree states: blocking, listening, learning, and forwarding. It takes 30 seconds for the switch to complete that sequence and begin forwarding packets to and from that port. During those 30 seconds, Novell sends 3 requests for a server, then stops looking. By the time Spanning Tree completes its job, Novell reports that "a file server could not be found."
There are several workarounds available:
Disable Spanning Tree on the switch (if Spanning Tree is not needed, i.e. no loops in the network topology).
For VLMs, add a "pause" just after calling VLM.EXE in STARTNET.BAT. When the user reboots a PC, have them wait at least 30 seconds before continuing the sequence. This workaround is documented on Novell's Knowledgebase (www.support.novell.com, search for document 2920460).
For Client32, add a registry entry in the PC, as documented on Novell's Knowledgebase (search for document 2925582).
In the Fall of 1998, HP released switch firmware (version C.05.07 or greater) with an enhancement to resolve this timing problem between Novell and STP. The enhancement allows users to configure Spanning Tree so that it does not go through the 4 states, on a port-by-port basis. Instead, for those configured ports, Spanning Tree will immediately begin forwarding packets to and from the port. This allows Novell clients to communicate with the server as soon as the network card (NIC) is enabled. After that, the switch continues to listen for and send Spanning Tree packets on those configured ports. This protects the user who might inadvertently connect a hub or switch to that port and create a network loop???Spanning Tree will detect the loop after a short time, since the port listens for and sends STP packets on that port.
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2002 10:46 PM
тАО05-06-2002 10:46 PM
Re: procurve switch 2524
Mrs. Ron Kinner hello.
Tanks for your help, I will try it.
Shimon
Tanks for your help, I will try it.
Shimon
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP