RE: VLSM Problem
I should have added more info. All the clients are configured in our org properly. Some clients are on diff subnets with diff masks, others are on the same vlsm with its appropriate subnet mask. some stations ping the clients while others cannot, however the clients can be ping'd from other stations. and I did search the archives, any help would be appreciated Ted Byerly System Support Analyst San Bernardino County Sheriff 909-387-3749 -Original Message- From: Irwin Lazar [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 24, 2000 9:27 AM To: 'Byerly, Ted'; '[EMAIL PROTECTED]' Subject: RE: VLSM Problem Most times that I've seen this type of thing, it ends being a mis-configured subnet mask on the remote workstation. Verify that the machine that you are trying to ping is properly configured. irwin -- Irwin Lazar, Senior Consultant The Burton Group - http://www.tbg.com/ e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] phone: 703-742-9659 "The Ultimate Resource For Network Architects" -Original Message- From: Byerly, Ted [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 24, 2000 12:16 PM To: '[EMAIL PROTECTED]' Subject: VLSM Problem Ok at the risk of being flamed I will post this question. We have implemented a VLSM and also have some subnets left over from our previous config. We are having intermittent problems reaching hosts both within and outside the vlsm. During troubleshooting if I ping a client by IP I get a time out error, if I try from another machine on the same or different subnet it also times out. But going to a third client , they are able to ping this machine. This occurs to different machines at different times and different subnets. The client is functioning properly for the user. My major question is are there known problems with vlsm and connectivity issues or could our router be not configured properly. I am the lowly server guy and the "network" guy refuses to believe the problem is related to vlsm, however we have never experienced this before Ted _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: VLSM Problem
You need to be more specific... We would need to know what the masks are on the various subnets, both working, and not working... what are the addresses and masks on the WS that are able to communicate... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Byerly, Ted Sent: Tuesday, October 24, 2000 12:49 PM To: '[EMAIL PROTECTED]' Subject: RE: VLSM Problem I should have added more info. All the clients are configured in our org properly. Some clients are on diff subnets with diff masks, others are on the same vlsm with its appropriate subnet mask. some stations ping the clients while others cannot, however the clients can be ping'd from other stations. and I did search the archives, any help would be appreciated Ted Byerly System Support Analyst San Bernardino County Sheriff 909-387-3749 -Original Message- From: Irwin Lazar [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 24, 2000 9:27 AM To: 'Byerly, Ted'; '[EMAIL PROTECTED]' Subject: RE: VLSM Problem Most times that I've seen this type of thing, it ends being a mis-configured subnet mask on the remote workstation. Verify that the machine that you are trying to ping is properly configured. irwin -- Irwin Lazar, Senior Consultant The Burton Group - http://www.tbg.com/ e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] phone: 703-742-9659 "The Ultimate Resource For Network Architects" -Original Message- From: Byerly, Ted [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 24, 2000 12:16 PM To: '[EMAIL PROTECTED]' Subject: VLSM Problem Ok at the risk of being flamed I will post this question. We have implemented a VLSM and also have some subnets left over from our previous config. We are having intermittent problems reaching hosts both within and outside the vlsm. During troubleshooting if I ping a client by IP I get a time out error, if I try from another machine on the same or different subnet it also times out. But going to a third client , they are able to ping this machine. This occurs to different machines at different times and different subnets. The client is functioning properly for the user. My major question is are there known problems with vlsm and connectivity issues or could our router be not configured properly. I am the lowly server guy and the "network" guy refuses to believe the problem is related to vlsm, however we have never experienced this before Ted _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: VLSM Problem
Ted you cant troubleshoot vlsm without configs. Some things to remember are subnets are different networks, and need a router. VLSM is just a way to effectively use available address space. But they are still subnets and need to be routed. 1. Find out if you can ping local addresses. 2. Find out if you can ping remote addresses and which ones. 2a. Routes have to be coming and going. 3. Also which type of routes do you have. Static/Default/Dynamic 4. Which type of routing protocols are you using. Distance Vector won't work. 5. What do you care! If you are just the "Server Guy" if your services are running then your done. Let the "Networking Guy" figure it out. You ain't getting paid to do it. We on the list are not getting paid to trouble shoot major VLSM problems either. This is more a group study/help site. Duck - Original Message - From: Byerly, Ted [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, October 24, 2000 9:49 AM Subject: RE: VLSM Problem I should have added more info. All the clients are configured in our org properly. Some clients are on diff subnets with diff masks, others are on the same vlsm with its appropriate subnet mask. some stations ping the clients while others cannot, however the clients can be ping'd from other stations. and I did search the archives, any help would be appreciated Ted Byerly System Support Analyst San Bernardino County Sheriff 909-387-3749 -Original Message- From: Irwin Lazar [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 24, 2000 9:27 AM To: 'Byerly, Ted'; '[EMAIL PROTECTED]' Subject: RE: VLSM Problem Most times that I've seen this type of thing, it ends being a mis-configured subnet mask on the remote workstation. Verify that the machine that you are trying to ping is properly configured. irwin -- Irwin Lazar, Senior Consultant The Burton Group - http://www.tbg.com/ e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] phone: 703-742-9659 "The Ultimate Resource For Network Architects" -Original Message- From: Byerly, Ted [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 24, 2000 12:16 PM To: '[EMAIL PROTECTED]' Subject: VLSM Problem Ok at the risk of being flamed I will post this question. We have implemented a VLSM and also have some subnets left over from our previous config. We are having intermittent problems reaching hosts both within and outside the vlsm. During troubleshooting if I ping a client by IP I get a time out error, if I try from another machine on the same or different subnet it also times out. But going to a third client , they are able to ping this machine. This occurs to different machines at different times and different subnets. The client is functioning properly for the user. My major question is are there known problems with vlsm and connectivity issues or could our router be not configured properly. I am the lowly server guy and the "network" guy refuses to believe the problem is related to vlsm, however we have never experienced this before Ted _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: VLSM Problem
Most times that I've seen this type of thing, it ends being a mis-configured subnet mask on the remote workstation. Verify that the machine that you are trying to ping is properly configured. irwin -- Irwin Lazar, Senior Consultant The Burton Group - http://www.tbg.com/ e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] phone: 703-742-9659 "The Ultimate Resource For Network Architects" -Original Message- From: Byerly, Ted [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 24, 2000 12:16 PM To: '[EMAIL PROTECTED]' Subject: VLSM Problem Ok at the risk of being flamed I will post this question. We have implemented a VLSM and also have some subnets left over from our previous config. We are having intermittent problems reaching hosts both within and outside the vlsm. During troubleshooting if I ping a client by IP I get a time out error, if I try from another machine on the same or different subnet it also times out. But going to a third client , they are able to ping this machine. This occurs to different machines at different times and different subnets. The client is functioning properly for the user. My major question is are there known problems with vlsm and connectivity issues or could our router be not configured properly. I am the lowly server guy and the "network" guy refuses to believe the problem is related to vlsm, however we have never experienced this before Ted _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: VLSM Problem
If you ping the clients by hostname are the name-servers responding with the correct ip addresses, even though they are timing out finding them? Sounds like a name resolution or browser related issue based on what little info you have posted. More info like whether you are using switches or hubs, what client OS is running, are there multiple VLANS and your name resolution methods would be helpful. From: "Byerly, Ted" [EMAIL PROTECTED] Reply-To: "Byerly, Ted" [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" [EMAIL PROTECTED] Subject: VLSM Problem Date: Tue, 24 Oct 2000 09:16:23 -0700 Ok at the risk of being flamed I will post this question. We have implemented a VLSM and also have some subnets left over from our previous config. We are having intermittent problems reaching hosts both within and outside the vlsm. During troubleshooting if I ping a client by IP I get a time out error, if I try from another machine on the same or different subnet it also times out. But going to a third client , they are able to ping this machine. This occurs to different machines at different times and different subnets. The client is functioning properly for the user. My major question is are there known problems with vlsm and connectivity issues or could our router be not configured properly. I am the lowly server guy and the "network" guy refuses to believe the problem is related to vlsm, however we have never experienced this before Ted _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
