I have a wierd problem...when attempting to use outlook with exchange, i enter the users name in the Microsoft Exchange setup in outlook and hit check name. It comes back and tells me that Outlook cannot communicate with the address book and the name cannot be resolved. On a laptop right next to...
my windows 2000 machine is connecting to a cisco router. Its a VPN connection and the cisco router is handing out the IP addresses. Since they are dynamic, trying to access a 192.168.100.0 network, the machines tries and goes through the gateway but of course fails. If I set the VPN connection...
Any chance someone knows how to do an Route Add for a dynamic IP address...
I have a VPN connection that keeps pulling an address (dynamic) and the only way I can make it work is if the IP is static and I add a Route Add statement to tell the PC that all 19.168.100.0 traffic to use that static...
The domain 'tdshetler.com' is an invalid Internet domain name. Message was
undeliverable.
Message originally to:
but if i do nslookup through the net it comes up with right IP
Due to a recent ISP change, I had to change the IP Address of my server..I got all the obvious IP references but mail is still getting bounced back to the sender when trying to send to me...anyone have any ideas??
I think I figured out my problem....my second DSL line isn't working and I think it has something to do with this line...
ip nat inside source route-map nonat interface Ethernet0/1 overload
If i change it to Ether0/2 then my second interface will work....
any ideas??
when setting up the route...does the 100 come before or after the 0.0.0.0 's???
I currently have them setup like this
ip route 0.0.0.0 0.0.0.0 <next hop>
ip route 0.0.0.0 0.0.0.0 <next hop> 100
interface Ethernet0/1
description AT&T
ip address <address withheld>
no ip proxy-arp
ip accounting output-packets
ip nat outside
no ip route-cache
no ip mroute-cache
ip policy route-map static
half-duplex
no cdp enable
crypto map cntmap
!
interface Ethernet0/2
description UUNet
ip...
I am using an internal dns server and I have eliminated the DNS possibility by shuting down the one interface and doing a ping..This is the result..
Pinging 65.2.208.61 with 32 bytes of data:
Reply from 192.168.100.28: Destination host unreachable.
Request timed out.
Request timed out.
Request...
Gateway of last resort did what you thought it would do when I shutdown the one device, but I couldn't get out through the net...any ideas why the traffic didnt go anywhere??
how come if I try to ping e0/2 (which correspondes to my secondary route statement) I don't get any reply....also, how long does it take for the secondary IP Route to take over when the first route fails??
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.