Login or Register to Ask a Question and Join Our Community


IP Networking

Lack of IP Connectivity

Login to Discuss or Reply to this Discussion in Our Community

 
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.
Login or Register to Ask a Question

Previous Thread | Next Thread

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
Login or Register to Ask a Question

LEARN ABOUT MOJAVE

shutdown

SHUTDOWN(2)						      BSD System Calls Manual						       SHUTDOWN(2)

NAME

     shutdown -- shut down part of a full-duplex connection

SYNOPSIS

     #include <sys/socket.h>

     int
     shutdown(int socket, int how);

DESCRIPTION

     The shutdown() call causes all or part of a full-duplex connection on the socket associated with socket to be shut down.  If how is SHUT_RD,
     further receives will be disallowed.  If how is SHUT_WR, further sends will be disallowed.  If how is SHUT_RDWR, further sends and receives
     will be disallowed.

RETURN VALUES

     The shutdown() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indi-
     cate the error.

ERRORS

     The call succeeds unless:

     [EBADF]		Socket is not a valid descriptor.

     [EINVAL]		The how argument is invalid.

     [ENOTCONN] 	The specified socket is not connected.

     [ENOTSOCK] 	Socket is a file, not a socket.

SEE ALSO

     connect(2), connectx(2), disconnectx(2), socket(2)

HISTORY

     The shutdown() function call appeared in 4.2BSD.

4.2 Berkeley Distribution					  March 18, 2015					 4.2 Berkeley Distribution