Visit Our UNIX and Linux User Community


Lack of IP Connectivity


 
Thread Tools Search this Thread
Special Forums IP Networking Lack of IP Connectivity
# 1  
Old 03-05-2012
Lack of IP Connectivity

Hi

Can any one please help identify the issue in scenario 2:

Connectivity Diagram:
1) Distribution Switch----Int_Switch----LabSwitch(Fa1/0)----Terminal Ser
2) Distribution Swtich----Int_Swtich----LabSwitch(Fa2/0)----3640 Router

---all links are access links

Distribution Switch (int vlan 10 = 10.1.96.251/26)
Int_Switch (int vlan 10 = 10.1.96.196/26)
LabSwitch (int vlan 10 = 10.1.96.234/26)
Termial Ser (Int Eth0 = 10.1.96.254/26)
3640 Router (int Fa1/0 = 10.1.96.245/26)

Scenario1: I could able to successfully ping/telent Termianal server from my pc.

Scenario2: Can able to ping Distribution switch ip from 3640 router and vice versa. But cannot able to ping/telnet from my pc. I have also confiured a default router on router as 0.0.0.0 0.0.0.0 10.1.96.251 but still cannot able to ping. i have a default-gate 10.1.96.251 configured.

Can any one please help in scenario2, if I am missing some thing.

Thanks in advance.

Previous Thread | Next Thread
Test Your Knowledge in Computers #511
Difficulty: Medium
Many programming languages do not allow you to begin a variable name with a number as it would make it more difficult for a compiler or interpreter to parse a program's source code.
True or False?

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Practice using Unix and lack of knowledge

So I have a Networking class at my university that involves learning the basic commands of unix (i.e. Chmod, cat, cp, ls, mv, rm, mkdir, rmdir, pwd, etc) and my professor had us download and install Solaris and PuTTY as a means of...I suppose practicing using/executing commands. However due to... (7 Replies)
Discussion started by: bo74
7 Replies

2. Shell Programming and Scripting

lack of understanding > annoying error

I'm working on a script I wrote called backup.sh when I run it like this: . ./backup.sh I get this error: ksh: ./backup.sh: no closing quote when I run it this way: backup.shI get this error: backup.sh: 28: Syntax error: end of file unexpected (expecting "fi")I looked through the code over... (21 Replies)
Discussion started by: jzacsh
21 Replies

3. What is on Your Mind?

Lack of Solaris Engineers?

Are more and more companies moving away from Solaris? I am currently helping a company search for a Sr. Solaris Engineer near Philadelphia and it seems as if more candidates are in other UNIX flavors. Is this correct? Where is the best place to search for Solaris Engineers? Thank you for your... (1 Reply)
Discussion started by: nickcrocemisi
1 Replies

4. Solaris

Lack of Solaris Engineers?

Are more and more companies moving away from Solaris? I am currently helping a company search for a Sr. Solaris Engineer near Philadelphia and it seems as if more candidates are in other UNIX flavors. Is this correct? Where is the best place to search for Solaris Engineers? Thank you for... (2 Replies)
Discussion started by: nickcrocemisi
2 Replies

5. Linux

postfix configuration issues...specifically masquerading (lack of )

postfix configuration issues...specifically masquerading (lack of ) Mail sent to our intranet arrives correctly (me@domain.com). Mail sent to our intranet arrives correctly (me@domain.com). Anything going outside does not, so my tests get rejected (me@hostname.com) :( any assistance... (5 Replies)
Discussion started by: mr_manny
5 Replies
CLRI(8) 						    BSD System Manager's Manual 						   CLRI(8)

NAME
clri -- clear an inode SYNOPSIS
clri special_device inode_number ... DESCRIPTION
Clri is obsoleted for normal file system repair work by fsck(8). Clri zeros out the inodes with the specified inode number(s) on the filesystem residing on the given special_device. The fsck(8) utility is usually run after clri to reclaim the zero'ed inode(s) and the blocks previously claimed by those inode(s). Both read and write permission are required on the specified special_device. The primary purpose of this routine is to remove a file which for some reason is not being properly handled by fsck(8). Once removed, it is anticipated that fsck(8) will be able to clean up the resulting mess. SEE ALSO
fsck(8), fsdb(8), icheck(8), ncheck(8) BUGS
If the file is open, the work of clri will be lost when the inode is written back to disk from the inode cache. 4th Berkeley Distribution April 19, 1994 4th Berkeley Distribution

Featured Tech Videos