Re: Catalyst 4000 and DHCP [7:62632]
Tunde, If configuring static IP addresses served as a temporary workaround, your problem is DHCP. Enabling Spanning Tree portfast on the ports to which stations directly attach will fix your problem: set spantree portfast enable - Tom On Fri, 07 Feb 2003 12:16:47 +, Tunde Kalejaiye wrote: hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Tunde Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=62702t=62632 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Catalyst 4000 and DHCP [7:62632]
Tunde, If configuring static IP addresses served as a temporary workaround, your problem is DHCP. Enabling Spanning Tree portfast on the ports to which stations directly attach will fix your problem: set spantree portfast enable - Tom On Fri, 07 Feb 2003 12:16:47 +, Tunde Kalejaiye wrote: hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Tunde Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=62695t=62632 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Catalyst 4000 and DHCP [7:62632]
the problem is dhcp...the client doesnt get an ip address hence the no domain controllererror message. i have enabled portfast on a few of the ports and i am waiting to get results on mondayi will keep u posted. regards, Tunde - Original Message - From: Priscilla Oppenheimer To: Sent: Friday, February 07, 2003 11:22 PM Subject: RE: Catalyst 4000 and DHCP [7:62632] Waters, Kristina wrote: I am curious as to whether anything else got upgraded besides the new switch. I got the impression that this wasn't a problem before the upgrade, in which case portfast could definitely be the culprit. However, you could also see this error if DNS is improperly configured in a win2k domain. Also, I'm not sure about this, but if the 4006 has a sup3 or sup4, could the problem be related to layer 3? Sure it could. He says all that he did was put a switch in, but there's a good chance he did more than that, but we may never know... Sigh. But a new switch might imply that he also put in VLANs, a L3 module, etc. When people send in questions, it would be nice if they would send in enough info so we could do more than guess. It would be nice if they would provide a follow-up also and let us know what the problem really was and what fixed it. Some people can't stand the out of the office messages. I can't stand the messages that ressemble someone calling their doctor on the phone and saying no more than, Hey doc, I'm tired. Why? Now, if you go to the doctor in person, this might be OK because then the doctor can examine you. Here the analogy falls apart. We can't examine someone else's network. However, the wise poster will communicate info to us about their examination of their network to help us help them. (This isn't targetted at the original poster specifically, who did supply at least some info.) Troubleshooting should be done systematically. It's not a guessing game. Hope we learn more about what the issue was! It could be educational for many of us. Priscilla Kris -Original Message- From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] Sent: Friday, February 07, 2003 1:24 PM To: [EMAIL PROTECTED] Subject: RE: Catalyst 4000 and DHCP [7:62632] Tunde Kalejaiye wrote: hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Your message title implies that there's a problem with DHCP, but then your message text implies that the problem is with Windows networking, specifically a client trying to reach the domain controller? (I assume you mean the Windows type domain server and not the IP Domain Name System.) So, verify for yourself and us that DHCP is working first. If the failure is with DHCP, try the stuff other folks recommended. Enable portfast so that the clients can start receiving replies to their DHCP request ASAP. Also, you may need a helper address, depending on where your DHCP server is located. Feel free to send us more info about your topology and configuration. Then, you have to get Winblows working. I did have all sorts of problems getting this to work with a consulting client who had upgraded to VLANs. Unfortunately, he fixed the problems in the end without my help, so I don't know the details, one of the frustrating things about being a consulant. (A lot of help that is. ;-) But you could look through some Group Study messages from about a month ago. A bunch of folks had ideas to help. I think the title of the thread was something about Windows Networking. Here's one message that a wise person on the list sent' I've forgotten who, sorry. Simplest solution is to put a WINS Server on the Subnet that can't find the DC. Configure it to replicate with the DC on the other Subnet, or Statically configure the Domain Name entry for the NT Domain on the WINS Server in the troubled subnet. Your DC Not Found issue should be resolved then. More Administratively intensive solution is to modify the LMHOSTS file to have the following entry on every Windows Workstation/Server in the troubled subnet. IP.ADD.RE.SS MachineName #PRE #DOM:Domain-Name Microsoft has tons of documentation on this sort of thing. Keep us posted! Thanks, Priscilla Tunde ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error
Re: Catalyst 4000 and DHCP [7:62632]
tunde kalejaiye wrote: the problem is dhcp...the client doesnt get an ip address hence the no domain controllererror message. i have enabled portfast on a few of the ports and i am waiting to get results on mondayi will keep u posted. regards, Thanks for getting back to us. This is how Group Study should work! I guess I shouldn't have gone off on a tangent with some guesses about something other than this obvious thing being wrong. :-) Sometimes when we have information about only one symptom, the obvious hypothesis is right. Often that's not the case, though, and more info should be gathered. Probably the client ends up with an address from the Microsoft Automatic Private IP Addressing scheme, 169.254.0.1 through 169.254.255.254. Depending on the OS, a lot of machines choose for themselves one of these addresses if set to receive an address dynamically and DHCP fails. That would have been the additional clue that would have helped solidify a good hypotheses. Thanks to everyone who participated. Do keep us posted! Thanks! Priscilla Tunde - Original Message - From: Priscilla Oppenheimer To: Sent: Friday, February 07, 2003 11:22 PM Subject: RE: Catalyst 4000 and DHCP [7:62632] Waters, Kristina wrote: I am curious as to whether anything else got upgraded besides the new switch. I got the impression that this wasn't a problem before the upgrade, in which case portfast could definitely be the culprit. However, you could also see this error if DNS is improperly configured in a win2k domain. Also, I'm not sure about this, but if the 4006 has a sup3 or sup4, could the problem be related to layer 3? Sure it could. He says all that he did was put a switch in, but there's a good chance he did more than that, but we may never know... Sigh. But a new switch might imply that he also put in VLANs, a L3 module, etc. When people send in questions, it would be nice if they would send in enough info so we could do more than guess. It would be nice if they would provide a follow-up also and let us know what the problem really was and what fixed it. Some people can't stand the out of the office messages. I can't stand the messages that ressemble someone calling their doctor on the phone and saying no more than, Hey doc, I'm tired. Why? Now, if you go to the doctor in person, this might be OK because then the doctor can examine you. Here the analogy falls apart. We can't examine someone else's network. However, the wise poster will communicate info to us about their examination of their network to help us help them. (This isn't targetted at the original poster specifically, who did supply at least some info.) Troubleshooting should be done systematically. It's not a guessing game. Hope we learn more about what the issue was! It could be educational for many of us. Priscilla Kris -Original Message- From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] Sent: Friday, February 07, 2003 1:24 PM To: [EMAIL PROTECTED] Subject: RE: Catalyst 4000 and DHCP [7:62632] Tunde Kalejaiye wrote: hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Your message title implies that there's a problem with DHCP, but then your message text implies that the problem is with Windows networking, specifically a client trying to reach the domain controller? (I assume you mean the Windows type domain server and not the IP Domain Name System.) So, verify for yourself and us that DHCP is working first. If the failure is with DHCP, try the stuff other folks recommended. Enable portfast so that the clients can start receiving replies to their DHCP request ASAP. Also, you may need a helper address, depending on where your DHCP server is located. Feel free to send us more info about your topology and configuration. Then, you have to get Winblows working. I did have all sorts of problems getting this to work with a consulting client who had upgraded to VLANs. Unfortunately, he fixed the problems in the end without my help, so I don't know the details, one of the frustrating things about being a consulant. (A lot of help that is. ;-) But you could look through some Group Study messages from about a month ago. A bunch of folks had ideas to help. I think the title of the thread was something about Windows Networking. Here's one message
Re: Catalyst 4000 and DHCP [7:62632]
Larry Letterman wrote: Hi Priscilla, I am reading your book that you sent me..why? :) need more info ? Yes, do tell! :-) Thanks. Priscilla Larry Letterman Network Engineer Cisco Systems - Original Message - From: Priscilla Oppenheimer To: Sent: Friday, February 07, 2003 3:22 PM Subject: RE: Catalyst 4000 and DHCP [7:62632] Waters, Kristina wrote: I am curious as to whether anything else got upgraded besides the new switch. I got the impression that this wasn't a problem before the upgrade, in which case portfast could definitely be the culprit. However, you could also see this error if DNS is improperly configured in a win2k domain. Also, I'm not sure about this, but if the 4006 has a sup3 or sup4, could the problem be related to layer 3? Sure it could. He says all that he did was put a switch in, but there's a good chance he did more than that, but we may never know... Sigh. But a new switch might imply that he also put in VLANs, a L3 module, etc. When people send in questions, it would be nice if they would send in enough info so we could do more than guess. It would be nice if they would provide a follow-up also and let us know what the problem really was and what fixed it. Some people can't stand the out of the office messages. I can't stand the messages that ressemble someone calling their doctor on the phone and saying no more than, Hey doc, I'm tired. Why? Now, if you go to the doctor in person, this might be OK because then the doctor can examine you. Here the analogy falls apart. We can't examine someone else's network. However, the wise poster will communicate info to us about their examination of their network to help us help them. (This isn't targetted at the original poster specifically, who did supply at least some info.) Troubleshooting should be done systematically. It's not a guessing game. Hope we learn more about what the issue was! It could be educational for many of us. Priscilla Kris -Original Message- From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] Sent: Friday, February 07, 2003 1:24 PM To: [EMAIL PROTECTED] Subject: RE: Catalyst 4000 and DHCP [7:62632] Tunde Kalejaiye wrote: hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Your message title implies that there's a problem with DHCP, but then your message text implies that the problem is with Windows networking, specifically a client trying to reach the domain controller? (I assume you mean the Windows type domain server and not the IP Domain Name System.) So, verify for yourself and us that DHCP is working first. If the failure is with DHCP, try the stuff other folks recommended. Enable portfast so that the clients can start receiving replies to their DHCP request ASAP. Also, you may need a helper address, depending on where your DHCP server is located. Feel free to send us more info about your topology and configuration. Then, you have to get Winblows working. I did have all sorts of problems getting this to work with a consulting client who had upgraded to VLANs. Unfortunately, he fixed the problems in the end without my help, so I don't know the details, one of the frustrating things about being a consulant. (A lot of help that is. ;-) But you could look through some Group Study messages from about a month ago. A bunch of folks had ideas to help. I think the title of the thread was something about Windows Networking. Here's one message that a wise person on the list sent' I've forgotten who, sorry. Simplest solution is to put a WINS Server on the Subnet that can't find the DC. Configure it to replicate with the DC on the other Subnet, or Statically configure the Domain Name entry for the NT Domain on the WINS Server in the troubled subnet. Your DC Not Found issue should be resolved then. More Administratively intensive solution is to modify the LMHOSTS file to have the following entry on every Windows Workstation/Server in the troubled subnet. IP.ADD.RE.SS MachineName #PRE #DOM:Domain-Name Microsoft has tons of documentation on this sort of thing. Keep us posted! Thanks, Priscilla Tunde ** This email and any files transmitted
Re: Catalyst 4000 and DHCP [7:62632]
Hi Priscilla, I am reading your book that you sent me..why? :) need more info ? Larry Letterman Network Engineer Cisco Systems - Original Message - From: Priscilla Oppenheimer To: Sent: Friday, February 07, 2003 3:22 PM Subject: RE: Catalyst 4000 and DHCP [7:62632] Waters, Kristina wrote: I am curious as to whether anything else got upgraded besides the new switch. I got the impression that this wasn't a problem before the upgrade, in which case portfast could definitely be the culprit. However, you could also see this error if DNS is improperly configured in a win2k domain. Also, I'm not sure about this, but if the 4006 has a sup3 or sup4, could the problem be related to layer 3? Sure it could. He says all that he did was put a switch in, but there's a good chance he did more than that, but we may never know... Sigh. But a new switch might imply that he also put in VLANs, a L3 module, etc. When people send in questions, it would be nice if they would send in enough info so we could do more than guess. It would be nice if they would provide a follow-up also and let us know what the problem really was and what fixed it. Some people can't stand the out of the office messages. I can't stand the messages that ressemble someone calling their doctor on the phone and saying no more than, Hey doc, I'm tired. Why? Now, if you go to the doctor in person, this might be OK because then the doctor can examine you. Here the analogy falls apart. We can't examine someone else's network. However, the wise poster will communicate info to us about their examination of their network to help us help them. (This isn't targetted at the original poster specifically, who did supply at least some info.) Troubleshooting should be done systematically. It's not a guessing game. Hope we learn more about what the issue was! It could be educational for many of us. Priscilla Kris -Original Message- From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] Sent: Friday, February 07, 2003 1:24 PM To: [EMAIL PROTECTED] Subject: RE: Catalyst 4000 and DHCP [7:62632] Tunde Kalejaiye wrote: hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Your message title implies that there's a problem with DHCP, but then your message text implies that the problem is with Windows networking, specifically a client trying to reach the domain controller? (I assume you mean the Windows type domain server and not the IP Domain Name System.) So, verify for yourself and us that DHCP is working first. If the failure is with DHCP, try the stuff other folks recommended. Enable portfast so that the clients can start receiving replies to their DHCP request ASAP. Also, you may need a helper address, depending on where your DHCP server is located. Feel free to send us more info about your topology and configuration. Then, you have to get Winblows working. I did have all sorts of problems getting this to work with a consulting client who had upgraded to VLANs. Unfortunately, he fixed the problems in the end without my help, so I don't know the details, one of the frustrating things about being a consulant. (A lot of help that is. ;-) But you could look through some Group Study messages from about a month ago. A bunch of folks had ideas to help. I think the title of the thread was something about Windows Networking. Here's one message that a wise person on the list sent' I've forgotten who, sorry. Simplest solution is to put a WINS Server on the Subnet that can't find the DC. Configure it to replicate with the DC on the other Subnet, or Statically configure the Domain Name entry for the NT Domain on the WINS Server in the troubled subnet. Your DC Not Found issue should be resolved then. More Administratively intensive solution is to modify the LMHOSTS file to have the following entry on every Windows Workstation/Server in the troubled subnet. IP.ADD.RE.SS MachineName #PRE #DOM:Domain-Name Microsoft has tons of documentation on this sort of thing. Keep us posted! Thanks, Priscilla Tunde ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments
Re: Catalyst 4000 and DHCP [7:62632]
Make sure you turn on portfast for workstation ports. set spantree portfast enable This will cause the port to start forwarding in 5 seconds as apposed to 50. Ronnie Tunde Kalejaiye wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Tunde Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=62633t=62632 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Catalyst 4000 and DHCP [7:62632]
Do yo have portfast enabled on all end user ports? Kris -Original Message- From: Tunde Kalejaiye [mailto:[EMAIL PROTECTED]] Sent: Friday, February 07, 2003 7:17 AM To: [EMAIL PROTECTED] Subject: Catalyst 4000 and DHCP [7:62632] hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Tunde ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ** Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=62634t=62632 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Catalyst 4000 and DHCP [7:62632]
Tunde Kalejaiye wrote: hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Your message title implies that there's a problem with DHCP, but then your message text implies that the problem is with Windows networking, specifically a client trying to reach the domain controller? (I assume you mean the Windows type domain server and not the IP Domain Name System.) So, verify for yourself and us that DHCP is working first. If the failure is with DHCP, try the stuff other folks recommended. Enable portfast so that the clients can start receiving replies to their DHCP request ASAP. Also, you may need a helper address, depending on where your DHCP server is located. Feel free to send us more info about your topology and configuration. Then, you have to get Winblows working. I did have all sorts of problems getting this to work with a consulting client who had upgraded to VLANs. Unfortunately, he fixed the problems in the end without my help, so I don't know the details, one of the frustrating things about being a consulant. (A lot of help that is. ;-) But you could look through some Group Study messages from about a month ago. A bunch of folks had ideas to help. I think the title of the thread was something about Windows Networking. Here's one message that a wise person on the list sent' I've forgotten who, sorry. Simplest solution is to put a WINS Server on the Subnet that can't find the DC. Configure it to replicate with the DC on the other Subnet, or Statically configure the Domain Name entry for the NT Domain on the WINS Server in the troubled subnet. Your DC Not Found issue should be resolved then. More Administratively intensive solution is to modify the LMHOSTS file to have the following entry on every Windows Workstation/Server in the troubled subnet. IP.ADD.RE.SS MachineName #PRE #DOM:Domain-Name Microsoft has tons of documentation on this sort of thing. Keep us posted! Thanks, Priscilla Tunde Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=62653t=62632 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Catalyst 4000 and DHCP [7:62632]
I am curious as to whether anything else got upgraded besides the new switch. I got the impression that this wasn't a problem before the upgrade, in which case portfast could definitely be the culprit. However, you could also see this error if DNS is improperly configured in a win2k domain. Also, I'm not sure about this, but if the 4006 has a sup3 or sup4, could the problem be related to layer 3? Kris -Original Message- From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] Sent: Friday, February 07, 2003 1:24 PM To: [EMAIL PROTECTED] Subject: RE: Catalyst 4000 and DHCP [7:62632] Tunde Kalejaiye wrote: hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Your message title implies that there's a problem with DHCP, but then your message text implies that the problem is with Windows networking, specifically a client trying to reach the domain controller? (I assume you mean the Windows type domain server and not the IP Domain Name System.) So, verify for yourself and us that DHCP is working first. If the failure is with DHCP, try the stuff other folks recommended. Enable portfast so that the clients can start receiving replies to their DHCP request ASAP. Also, you may need a helper address, depending on where your DHCP server is located. Feel free to send us more info about your topology and configuration. Then, you have to get Winblows working. I did have all sorts of problems getting this to work with a consulting client who had upgraded to VLANs. Unfortunately, he fixed the problems in the end without my help, so I don't know the details, one of the frustrating things about being a consulant. (A lot of help that is. ;-) But you could look through some Group Study messages from about a month ago. A bunch of folks had ideas to help. I think the title of the thread was something about Windows Networking. Here's one message that a wise person on the list sent' I've forgotten who, sorry. Simplest solution is to put a WINS Server on the Subnet that can't find the DC. Configure it to replicate with the DC on the other Subnet, or Statically configure the Domain Name entry for the NT Domain on the WINS Server in the troubled subnet. Your DC Not Found issue should be resolved then. More Administratively intensive solution is to modify the LMHOSTS file to have the following entry on every Windows Workstation/Server in the troubled subnet. IP.ADD.RE.SS MachineName #PRE #DOM:Domain-Name Microsoft has tons of documentation on this sort of thing. Keep us posted! Thanks, Priscilla Tunde ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ** Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=62662t=62632 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Catalyst 4000 and DHCP [7:62632]
I suppose its possible to have a L3 issue, but if the L3 card is setup for the Vlan interfaces and routing properly, and the appropriate helpers are in place on the L3 interface, the 4006 should work. Usually this issue is a result of the STP 50 second forward time on the L2 port. Larry Letterman Network Engineer Cisco Systems - Original Message - From: Waters, Kristina To: Sent: Friday, February 07, 2003 11:58 AM Subject: RE: Catalyst 4000 and DHCP [7:62632] I am curious as to whether anything else got upgraded besides the new switch. I got the impression that this wasn't a problem before the upgrade, in which case portfast could definitely be the culprit. However, you could also see this error if DNS is improperly configured in a win2k domain. Also, I'm not sure about this, but if the 4006 has a sup3 or sup4, could the problem be related to layer 3? Kris -Original Message- From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] Sent: Friday, February 07, 2003 1:24 PM To: [EMAIL PROTECTED] Subject: RE: Catalyst 4000 and DHCP [7:62632] Tunde Kalejaiye wrote: hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Your message title implies that there's a problem with DHCP, but then your message text implies that the problem is with Windows networking, specifically a client trying to reach the domain controller? (I assume you mean the Windows type domain server and not the IP Domain Name System.) So, verify for yourself and us that DHCP is working first. If the failure is with DHCP, try the stuff other folks recommended. Enable portfast so that the clients can start receiving replies to their DHCP request ASAP. Also, you may need a helper address, depending on where your DHCP server is located. Feel free to send us more info about your topology and configuration. Then, you have to get Winblows working. I did have all sorts of problems getting this to work with a consulting client who had upgraded to VLANs. Unfortunately, he fixed the problems in the end without my help, so I don't know the details, one of the frustrating things about being a consulant. (A lot of help that is. ;-) But you could look through some Group Study messages from about a month ago. A bunch of folks had ideas to help. I think the title of the thread was something about Windows Networking. Here's one message that a wise person on the list sent' I've forgotten who, sorry. Simplest solution is to put a WINS Server on the Subnet that can't find the DC. Configure it to replicate with the DC on the other Subnet, or Statically configure the Domain Name entry for the NT Domain on the WINS Server in the troubled subnet. Your DC Not Found issue should be resolved then. More Administratively intensive solution is to modify the LMHOSTS file to have the following entry on every Windows Workstation/Server in the troubled subnet. IP.ADD.RE.SS MachineName #PRE #DOM:Domain-Name Microsoft has tons of documentation on this sort of thing. Keep us posted! Thanks, Priscilla Tunde ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ** [EMAIL PROTECTED] Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=62668t=62632 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Catalyst 4000 and DHCP [7:62632]
Tunde, It sounds like your users are getting blocked by spanning tree on bootup. Since the switch is spending ~50 seconds running spanning-tree before it forwards any data, the DHCP requests aren't even getting through. PortFast bypasses the usual spanning tree thing. It allows the port to forward data almost as soon as its initialized. It a good idea to only use portfast on a port to has an end node like a PC, server, or printer. If your switch uses CatOS 7.1 or Native IOS 12.1(11)EX then it implements Rapid spanning tree (802.1w) which shortens the time spent learning the network before forwarding. You still need to use the portfast keyword to configure the port as an edge port though. Here's a link about it: http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfa.shtml Hope this helps. Karen *** REPLY SEPARATOR *** On 2/7/2003 at 12:16 PM Tunde Kalejaiye wrote: hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Tunde Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=62677t=62632 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Catalyst 4000 and DHCP [7:62632]
Waters, Kristina wrote: I am curious as to whether anything else got upgraded besides the new switch. I got the impression that this wasn't a problem before the upgrade, in which case portfast could definitely be the culprit. However, you could also see this error if DNS is improperly configured in a win2k domain. Also, I'm not sure about this, but if the 4006 has a sup3 or sup4, could the problem be related to layer 3? Sure it could. He says all that he did was put a switch in, but there's a good chance he did more than that, but we may never know... Sigh. But a new switch might imply that he also put in VLANs, a L3 module, etc. When people send in questions, it would be nice if they would send in enough info so we could do more than guess. It would be nice if they would provide a follow-up also and let us know what the problem really was and what fixed it. Some people can't stand the out of the office messages. I can't stand the messages that ressemble someone calling their doctor on the phone and saying no more than, Hey doc, I'm tired. Why? Now, if you go to the doctor in person, this might be OK because then the doctor can examine you. Here the analogy falls apart. We can't examine someone else's network. However, the wise poster will communicate info to us about their examination of their network to help us help them. (This isn't targetted at the original poster specifically, who did supply at least some info.) Troubleshooting should be done systematically. It's not a guessing game. Hope we learn more about what the issue was! It could be educational for many of us. Priscilla Kris -Original Message- From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] Sent: Friday, February 07, 2003 1:24 PM To: [EMAIL PROTECTED] Subject: RE: Catalyst 4000 and DHCP [7:62632] Tunde Kalejaiye wrote: hi all, we just upgraded our network to a switched, a catalyst 4006 to be exactsome users have been getting 'no domain server available ' error message. they usually have to try more than 4 - 6 times to successfully log on to the network. has anybody come across this problem before? what work around did u use besides configuring static ip addresses? thanks for your response(s) in advance Your message title implies that there's a problem with DHCP, but then your message text implies that the problem is with Windows networking, specifically a client trying to reach the domain controller? (I assume you mean the Windows type domain server and not the IP Domain Name System.) So, verify for yourself and us that DHCP is working first. If the failure is with DHCP, try the stuff other folks recommended. Enable portfast so that the clients can start receiving replies to their DHCP request ASAP. Also, you may need a helper address, depending on where your DHCP server is located. Feel free to send us more info about your topology and configuration. Then, you have to get Winblows working. I did have all sorts of problems getting this to work with a consulting client who had upgraded to VLANs. Unfortunately, he fixed the problems in the end without my help, so I don't know the details, one of the frustrating things about being a consulant. (A lot of help that is. ;-) But you could look through some Group Study messages from about a month ago. A bunch of folks had ideas to help. I think the title of the thread was something about Windows Networking. Here's one message that a wise person on the list sent' I've forgotten who, sorry. Simplest solution is to put a WINS Server on the Subnet that can't find the DC. Configure it to replicate with the DC on the other Subnet, or Statically configure the Domain Name entry for the NT Domain on the WINS Server in the troubled subnet. Your DC Not Found issue should be resolved then. More Administratively intensive solution is to modify the LMHOSTS file to have the following entry on every Windows Workstation/Server in the troubled subnet. IP.ADD.RE.SS MachineName #PRE #DOM:Domain-Name Microsoft has tons of documentation on this sort of thing. Keep us posted! Thanks, Priscilla Tunde ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ** Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=62678t=62632 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
