I am having a problem connecting two locations via frame relay. The problem
I am having is being able to see/ping the machines on the internal/nic 1 of
the nt servers. Below is a diagram. Any help would be appreciated
nic1-192.168.15.1 to hubs nic1-192.168.18.101 to hubs
nic2-192.168.1.10 to, nic2 - 192.168.16.10 to,
cisco2524-192.168.1.1 ---- f/r--- cisco2524 192.168.16.1
IP forwarding is enabled on both sides
Using cisco ip unnumbered for serial/circuit
rip is enabled on cisco and installed on the NTs
From either side I can ping the nic2 card
i.e.: from nt-metro I can ping all the way to 192.168.16.10
from nt-hacky I can ping all the way to 18.104.22.168
I can also map to each machines devices.
Where do I set the routing to enable the 192.168.15.x machines
to ping the 192.168.18.x and visa versa
I CAN FIX THE NAT HERE GIVE SOLUTION ASAP THANKS
A 6ya expert can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
The service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones). click here to download the app (for users in the US for now) and get all the help you need. Good luck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
1) Open a command prompt (or terminal, under System Tools)
2) Verify your system default route (route -n)
a) Does route 0.0.0.0/0 exist?
1) Does it have a gateway IP address similar to that of your cable company? If so, try 'ping 22.214.171.124'
2) Is the gateway IP address similar to 192.168.x.x? If so, you have a local router. Verify that you can 'ping 126.96.36.199'. If not, try to ping your router IP address.
3) If still unsuccessful, verify your IP address.
on my machine. This is only a service provider I believe and not an end website. Have you checked and verified the ip address with the contact organization? Just because you can run a trace route on an ip address does not make accessible.
The cisco could also be blocking the outbound connection at your end.
non public ips mean the 192.168.x.x. addresses you are referring to ... since they form a virtual private network it is normal .. see if ping protocol is disabled ..the other router just discarding the ping packets... you may have to check the route a packet is taking without VPN ...it can be complex without a network diagram.
pl set the ips , thn connect the ethernet, see if the net icon says ethernet connected,ping the ips including self ping,if unsuccessful chech ips , if successful, ping modem , if unsuccessful check router, ifsuccessful , connect to internet.
How this works:
Restoring the PocketPrintServer to Factory Defaults
In most cases, the best way to restore the PocketPrintServer to
factory defaults is through "telnet". However, if you are unable to
connect to the device because of a configuration error, use the
following method which does not require a network connection.
To restore the PocketPrintServer to factory defaults, complete
the following steps:
1. Disconnect the PocketPrintServer from the network and
power cycle it. When it powers up, the LED will rapidly
blink orange for five seconds.
2. Power down the device during the rapid orange blink
period. Power up the device and power it down during
that orange blink period two more times.
3. Reconnect the network cable and power up the
PocketPrintServer. It will have restored itself to factory
defaults and will rapidly blink green as it searches for a
RARP or BOOTP server to find an IP address.
If an IP address has not been permanently assigned when the
PocketPrintServer is powered on or reset, it will look for a "ping"
packet on the network. If the PocketPrintServer receives a "ping"
packet within two minutes, it will accept the IP address in the
"ping" packet as its own address.
To use Gleaning, you must have super-user privileges on a UNIX
system. Gleaning also works under Windows 95 and Windows NT.
1. Add an entry in the ARP table that assigns an IP address to the
Ethernet address of the PocketPrintServer. To do this, use the
arp -s temp
arp -s 192.168.42.24 00:02:16:00:00:01 temp
2. Start a continuous "ping" to the PocketPrintServer.
Example: ping 192.168.42.24
On some systems, this may require an additional parameter.
Some implementations of "ping" only send out one "ping"
packet which could get lost in transit. Check your system
documentation for more information.
3. Connect power to the PocketPrintServer.
The PocketPrintServer will "glean" its IP address from the "ping"
packet. This IP address will remain in effect until the
PocketPrintServer is power cycled or reset. Therefore, a permanent
IP address should be assigned by running the ExtendView TCP/IP
utility or via "telnet".