- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
If the IP address pool has much more resources than needs of clients, the following two reasons may cause address exhaustion:
1. An attacker keeps changing the CHADDR field and sending DHCP Discover packets to exhaust addresses. If so, contact Huawei engineers to deploy DHCP snooping to protect the IP address pool.
2. The DHCP server ping function is enabled on the DHCP server. This function tries to ping the allocated addresses before responding to DHCP Offer packets. If a client responds to any ping packet, the DHCP server considers that there are address conflicts and addresses are exhausted. To solve this problem, two methods are available:
1. Capture packets on the ports connected to the DHCP server. If a client responds to ping packets, prohibit the client.
2. Disable the DHCP server ping function using the undo dhcp server ping packet command.
3. Such as S5700, S6700
<p><span>Some days before I have done a job on Windows Server 2003 Enterprise edition & Client XP. It is departmental food court. In the office room of the restaurant have a system which will be Server system and main domain. There was another 8 system in every department of food <span> </span>with printer for billing.I</SPAN><br>
<p><span>Windows Server 2003 includes a mission critical Windows Server operating system, such as security, reliability, availability, and scalability.</SPAN><br>
<p><span>You have to install DNS server for DC without DNS the client computers wouldn't know which one is DC.You can host DNS on a different server than DC.</SPAN><br>
<p><span>Before Starting the DC installation process you need to make sure the <span> </SPAN>following points</SPAN><br>
<p><span>1)You have installed Basic windows server 2003 installation</SPAN><br>
<p><span>2)Make sure you have assigned a static ip address to your server</SPAN><br>
<p><span><span> </SPAN>Now start DC and DNS Setup process</SPAN><span></SPAN><br>
<span>Active Directory is a huge topic in itself. While DCPROMO is easy to run, planning of both the physical and the logical structure is the key to a trouble free active directory. </SPAN>
<p><span>Domain controllers do not have to be your most powerful machines, however they must be reliable and always available to answer logon requests. </SPAN><br>
<a><span>DNS (Domain Name System)</SPAN></A><span><span> </SPAN></SPAN><span>Role</SPAN>
<p><span>Once DNS is setup, it runs itself thanks to the new dynamic component hence DDNS. TCP/IP knowledge plus understanding of how DNS works is essential when troubleshooting connectivity problems.</SPAN><br>
<p><span>DNS enables client machines to resolve servers IP addresses. Once the client finds the server, Active Directory uses LDAP to locate services like Kerberos, Global Catalog that clients request.</SPAN><br>
<a><span>Print Server Role</SPAN></A><span></SPAN>
<p><span>In my experience there is a contrast between the software settings which are easy to configure and the hardware which constantly need for attention e.g. paper jam, 'out of toner'. Check list for print server:</SPAN><br>
<p><b><span>Client Configuration :- </SPAN></B><span>After</SPAN><span><span> Installation of Windows Xp give the IP Add on TCP/IP of IPV4.If you want to manually configure DNS server addresses, click</SPAN></SPAN><span><span> </SPAN></SPAN><b><span>Use the following DNS server addresses</SPAN></b><span><b><span>,</SPAN></B></SPAN><span><span> and then type the preferred DNS server and alternate DNS server IP addresses in the</SPAN></SPAN><span><span> </SPAN></SPAN><b><span>Preferred DNS server</SPAN></b><span><span> </SPAN></SPAN><span><span>and</SPAN></SPAN><span><span> </SPAN></SPAN><b><span>Alternate DNS server</SPAN></b><span><span> </SPAN></SPAN><span><span>boxes. After all job try to ping each other. I'm trying this and it also pinging. Files and data also can be shared through it.</SPAN></SPAN>
This is an excerpt from a MS Technet page for error 53:
Resolutions:1) if it is domain environment, check your WINS; 2) if it is peer-to-peer workgroup, enable NetBIOS over TCP/IP; 3) make sure the machine is running; 4) make sure file and Printer Share enabled on remote computer; 5) make sure client for ms networks is enabled on local computer; 6) make sure you type the correct name. 7) Make sure no firewall running or any security setting.
Pay close attention to #s 4 and 5 - I suspect XP pro might not be open enough.
Can you provide the topology of your setup? Can you provide also the following:
- running configuration of the ASA
- ip address of the server (what kind of server is this? what tcp/udp port does it use)
- show xlate
- show con
- show log
Just a quick try, have you tried clearing the translation and the arp table?
commands to do it:
Let me know and if it still doesn't work, try to ping the server from the pc clients and see if ping does work. (you need to allow icmp to pass thru in case you are denying it for testing purposes) Just send me the additional information given above.
I am assuming that you are referring to the tower (desktop) as the server while the laptop is the client. While the client can access the server's CD drive, you can not ping the server. A couple of ideas: 1. verify that both server and client belong to the same Workgroup; 2. verify that both server and client have the same Subnet Mask and that their satic IP adds are near each other; 3. Server's firewall settings/configurations does not allow/prevents ping response; and/or 4. the server might be using Zonelab, McAfee Firewall, Microsoft ICF SP2 or some other form of port blocking.
Hope this be of initial help/idea. Pls post back how things turned up or should you need additional information.
Your DHCP server will keep track of which MAC Addresses have been given what IP addresses. From there, find the IP address of your Print Server. Ping the IP address to confirm IP connectivity between your computer and the print server. You should then be able to upgrade the firmware.