Login or Register to Ask a Question and Join Our Community


Web Development

Getting access of my project kept in one 121.12.12.125 node

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums Web Development Getting access of my project kept in one 121.12.12.125 node
# 1  
Old 11-26-2009
CPU & Memory Getting access of my project kept in one 121.12.12.125 node
sir.. i am working in a WAN......
i am getting the login screen for an application by typing the address of the location and the file name "http:/121.12.12.111/xyz.html" from the node 121.12.12.125.

now i had my web applicatioon at 121.12.12.125 for which i have taken the source code of the above .html document and modified the parameters to my requirement and renamed the html document as pqr.html and tried to access the same from another node..121.12.12.140.....by typing the address as http:/121.12.12.125/pqr.html...................

and i am getting page cannot be displayed msg....
i have kept the pqr.html at c:

whether i am correct?
pl.. guide for getting access of my project kept in one 121.12.12.125 node
from another node 121.12.12.140
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. HP-UX

Mount FIle systems from node-1 onto node-2

Hi, We have HP UX service guard cluster on OS 11.23. Recently 40+ LUNs presented to both nodes by SAN team but I was asked to mount them on only one node. I created required VGs/LVs, created VxFS and mounted all of them and they are working fine. Now client requested those FS on 2nd node as... (4 Replies)
Discussion started by: prvnrk
4 Replies

2. Homework & Coursework Questions

Accessing one UNIX node from another node of the same server

Hi Experts, I am in need of running a script from one node say node 1 via node 2. My scheduling tool dont have access to node2 , so i need to invoke the list file from node1 but the script needs to run from node2. because the server to which i am hitting, is having access only for the node... (5 Replies)
Discussion started by: arun1377
5 Replies

3. Solaris

Probem is nfs folder access from root/users on another node

Hi all I am try NFS on node1 & node2 servers. On node1, when I am using # share -F nfs -o rw,anon=0 /abc On node2, when I am using # mount -f nfs node1:/abc /a in /a folder, root user is able to create files but any other user from node2 is not able to create files, please... (1 Reply)
Discussion started by: sb200
1 Replies

4. IP Networking

getting access of my project kept in one node

sir.. i am working in a WAN...... i am getting the login screen for an application by typing the address of the location and the file name "http:/121.12.12.111/xyz.html" from the node 121.12.12.125. now i had my web applicatioon at 121.12.12.125 for which i have taken the source code of the... (0 Replies)
Discussion started by: KANNI786
0 Replies

5. Shell Programming and Scripting

#? 0,1,2,,,,,,,125 ?

The return value of the #? returns status of the executed command, i.e If it is 0 then SUCCESS, If it is non-zero value the it means FAILURE. My doubt is how does the return status defined? 1,2,3,,,,,125. Exp: if it returns 125,, how does it relates to failure? (1 Reply)
Discussion started by: praveen_b744
1 Replies

6. AIX

pg: 0652-121

Hello, Whenever a non-root user try to run any cmd with |pg on a AIX 5.1 system it returns: pg: 0652-121 Cannot create the temporary file. Does anyone knows what this is about? This doesn't occur with root account. Obrigado (2 Replies)
Discussion started by: maraquez
2 Replies
Login or Register to Ask a Question

LEARN ABOUT CENTOS

ng_rfc1490

NG_RFC1490(4)						   BSD Kernel Interfaces Manual 					     NG_RFC1490(4)

NAME

     ng_rfc1490 -- RFC 1490 netgraph node type

SYNOPSIS

     #include <netgraph/ng_rfc1490.h>

DESCRIPTION

     The rfc1490 node type performs protocol encapsulation, de-encapsulation, and multiplexing according to RFC 1490 (which has since been updated
     by RFC 2427).  This particular type of encapsulation is often used on top of frame relay DLCI channels.

     The downstream hook is used to transmit and receive encapsulated frames.  On the other side of the node, the inet and ppp hooks are used to
     transmit and receive raw IP frames and PPP frames, respectively.  PPP frames are transmitted and received according to RFC 1973; in particu-
     lar, frames appearing on the ppp hook begin with the PPP protocol number.	The ethernet hook can be used to transmit and receive Ethernet
     frames (without a checksum) in RFC 1490's bridging format.

     Typically the inet hook is connected to the inet hook of an ng_iface(4) node.

HOOKS

     This node type supports the following hooks:

     downstream   Connects to the RFC 1490 peer entity.

     ethernet	  Transmits and receives bridged raw Ethernet frames, without a checksum.

     inet	  Transmits and receives raw IP frames.

     ppp	  Transmits and receives PPP frames.

CONTROL MESSAGES

     This node type supports the generic control messages, plus the following:

     NGM_RFC1490_SETENCAP
	     This command sets encapsulation method for the node.  The desired method must be passed as a string message argument, and must be one
	     of the following supported encapsulation modes:

	     "ietf-ip"	  IP packets are sent using simple RFC1490/2427 encapsulation.

	     "ietf-snap"  IP packets are sent inside SNAP frames.  Also conforms to RFC1490/2427.

	     "cisco"	  IP packets are sent and received using proprietary Cisco encapsulation method.

     NGM_RFC1490_GETENCAP
	     This command returns current encapsulation method on the node.

SHUTDOWN

     This node shuts down upon receipt of a NGM_SHUTDOWN control message, or when all hooks have been disconnected.

SEE ALSO

     netgraph(4), ng_frame_relay(4), ng_iface(4), ngctl(8)

     C. Brown and A. Malis, Multiprotocol Interconnect over Frame Relay, RFC 2427.

     W. Simpson, PPP in Frame Relay, RFC 1973.

     http://www.cisco.com/warp/public/121/frf8modes.pdf

HISTORY

     The ng_rfc1490 node type was implemented in FreeBSD 4.0.

AUTHORS

     Julian Elischer <julian@FreeBSD.org>

BUGS

     Not all of RFC 1490 is implemented.

BSD
								 January 19, 1999							       BSD