Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Setting up a router with DSL 3
- Thread starter marcvu
- Start date
More Info this PC has 2 Nics. I fooled around with the Nics and I am able to keep a constant connection. It has been up and running for 2 days with only one problem. For the first 2 days I could check my email. Now I can't, although I can ping the mail server. If I hook up my DSL modem I dont have a problem accessing mail.
Puzzled !!!!
Puzzled !!!!
otakuoverlord
Technical User
alritter- what OS are you using to check your email?
Windows 2000 server, Outlook 2000 as my mail client. Interesting...I can send with no problem. I left the router hooked up. And outlook opened over night. When I woke up I had messages in my in box. I clicked send/receive and I have the problem again. No mail being delivered but I can send.
I was beginning to wonder if any one read my posts !!!!
Alton
I was beginning to wonder if any one read my posts !!!!
Alton
otakuoverlord
Technical User
QUESTION 2-Does the send/recieve process halt on an error, or does it just cycle until it times out?
otakuoverlord
Technical User
BTW- if you want more responses, try starting a new thread- this one is ancient.
otakuoverlord
Technical User
So you can access the internet just fine, it's the mail you have problems with, eh?
This may sound stupid, and I hate to actually LISTEN to a microsoft error message, but have you relayed this particular problem to your ISP?
I get this feeling that your current situation is due to a problem on your ISP's end.
This may sound stupid, and I hate to actually LISTEN to a microsoft error message, but have you relayed this particular problem to your ISP?
I get this feeling that your current situation is due to a problem on your ISP's end.
Let me jump in with a question...
If you are using POP3 to talk with the server, the issue might be the order of mail retrival.. alot of ISP mail providers now require you to SEND mail by first RECEIVING mail then sending it. THis is to aid in cutting down spammers who are trying to relay the mail through their servers.
If you have your own server, then this probably doesnt apply at all.
But, with a sniffer on your end, you can verify the mail exchange.. move the sniffer to the remote end and verify it again. Divide and conquer the problem.
More thoughts.. if you get mail, then the server can see you.. if you do not have a route back to the server, you more then likely could not send the mail. I read somewhere in the thread you could not ping the mail server. thats a problem if it's still an issue. Run a traceroute from the workstation adn from the router. On the router, use a extended traceroute, force the router to use the port connected to the wan link. See where the packets are being droppped.
Are you configured for network browsing? If so, then try mapping the server via the "whack-whack servername" and see if the mail works that way.. if so then the issue is a name resolution problem.. WINS more then likely and/or DNS
MikeS
Find me at
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin
If you are using POP3 to talk with the server, the issue might be the order of mail retrival.. alot of ISP mail providers now require you to SEND mail by first RECEIVING mail then sending it. THis is to aid in cutting down spammers who are trying to relay the mail through their servers.
If you have your own server, then this probably doesnt apply at all.
But, with a sniffer on your end, you can verify the mail exchange.. move the sniffer to the remote end and verify it again. Divide and conquer the problem.
More thoughts.. if you get mail, then the server can see you.. if you do not have a route back to the server, you more then likely could not send the mail. I read somewhere in the thread you could not ping the mail server. thats a problem if it's still an issue. Run a traceroute from the workstation adn from the router. On the router, use a extended traceroute, force the router to use the port connected to the wan link. See where the packets are being droppped.
Are you configured for network browsing? If so, then try mapping the server via the "whack-whack servername" and see if the mail works that way.. if so then the issue is a name resolution problem.. WINS more then likely and/or DNS
MikeS
Find me at
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin
otakuoverlord, I don't think this is a problem to report to my ISP, becuase of the fact that I can retrieve mail if I use my Dsl modem.
wybnormal, My pop3 server and SMTP server are not the same.
as far as a sniffer, I'll have to download another one. The onee that I have has expired.
As far as trace route
C:\>tracert 206.46.170.10
Tracing route to mta1pub.gte.net [206.46.170.10]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms 199.198.197.1
2 30 ms 30 ms 40 ms 10.3.33.1
3 30 ms 30 ms 31 ms F0-1-0.G-RTR2.NY5030.verizon-gni.net [xxx.xxx.x.67]
4 40 ms 40 ms 30 ms p7-1.nycmny1-cr10.bbnplanet.net [4.24.189.165]
5 30 ms 30 ms 30 ms p1-0.nycmny1-nbr2.bbnplanet.net [4.24.8.169]
6 30 ms 40 ms 40 ms p9-0.phlapa1-br1.bbnplanet.net [4.24.10.177]
7 40 ms 60 ms 40 ms p9-0.iplvin1-br1.bbnplanet.net [4.24.10.182]
8 50 ms 50 ms 50 ms p15-0.iplvin1-br2.bbnplanet.net
[4.24.10.154]
9 70 ms 70 ms 61 ms p9-0.crtntx1-br1.bbnplanet.net [4.24.10.213]
10 60 ms 70 ms 80 ms p1-0.dllstx1-cr1.bbnplanet.net [4.24.5.82]
11 70 ms 70 ms 80 ms h0.verizonol.bbnplanet.net [4.25.56.42]
12 71 ms 70 ms * fa0-0-0.dfw3.cs1.gte.net [206.46.160.253]
13 70 ms * 70 ms 206.46.185.41
14 60 ms 80 ms 80 ms mta1pub.gte.net [206.46.170.10]
Trace complete.
From Router
1 10.3.33.1 44 msec 28 msec 28 msec
2 xxx.xxx.x.67 32 msec 44 msec 24 msec
3 4.24.189.165 28 msec 28 msec 36 msec
4 4.24.8.169 32 msec 32 msec 40 msec
5 4.24.10.177 24 msec 36 msec 48 msec
6 4.24.10.182 44 msec 48 msec 44 msec
7 4.24.10.154 44 msec 48 msec 44 msec
8 4.24.10.213 60 msec 60 msec 72 msec
9 4.24.5.82 56 msec 64 msec 64 msec
10 4.25.56.42 64 msec 64 msec 64 msec
11 206.46.160.253 64 msec 68 msec 76 msec
12 * * *
13 * * *
wybnormal, My pop3 server and SMTP server are not the same.
as far as a sniffer, I'll have to download another one. The onee that I have has expired.
As far as trace route
C:\>tracert 206.46.170.10
Tracing route to mta1pub.gte.net [206.46.170.10]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms 199.198.197.1
2 30 ms 30 ms 40 ms 10.3.33.1
3 30 ms 30 ms 31 ms F0-1-0.G-RTR2.NY5030.verizon-gni.net [xxx.xxx.x.67]
4 40 ms 40 ms 30 ms p7-1.nycmny1-cr10.bbnplanet.net [4.24.189.165]
5 30 ms 30 ms 30 ms p1-0.nycmny1-nbr2.bbnplanet.net [4.24.8.169]
6 30 ms 40 ms 40 ms p9-0.phlapa1-br1.bbnplanet.net [4.24.10.177]
7 40 ms 60 ms 40 ms p9-0.iplvin1-br1.bbnplanet.net [4.24.10.182]
8 50 ms 50 ms 50 ms p15-0.iplvin1-br2.bbnplanet.net
[4.24.10.154]
9 70 ms 70 ms 61 ms p9-0.crtntx1-br1.bbnplanet.net [4.24.10.213]
10 60 ms 70 ms 80 ms p1-0.dllstx1-cr1.bbnplanet.net [4.24.5.82]
11 70 ms 70 ms 80 ms h0.verizonol.bbnplanet.net [4.25.56.42]
12 71 ms 70 ms * fa0-0-0.dfw3.cs1.gte.net [206.46.160.253]
13 70 ms * 70 ms 206.46.185.41
14 60 ms 80 ms 80 ms mta1pub.gte.net [206.46.170.10]
Trace complete.
From Router
1 10.3.33.1 44 msec 28 msec 28 msec
2 xxx.xxx.x.67 32 msec 44 msec 24 msec
3 4.24.189.165 28 msec 28 msec 36 msec
4 4.24.8.169 32 msec 32 msec 40 msec
5 4.24.10.177 24 msec 36 msec 48 msec
6 4.24.10.182 44 msec 48 msec 44 msec
7 4.24.10.154 44 msec 48 msec 44 msec
8 4.24.10.213 60 msec 60 msec 72 msec
9 4.24.5.82 56 msec 64 msec 64 msec
10 4.25.56.42 64 msec 64 msec 64 msec
11 206.46.160.253 64 msec 68 msec 76 msec
12 * * *
13 * * *
::snip::
11 206.46.160.253 64 msec 68 msec 76 msec
This is the problem child... the packets from the router lose their way at this hop.
Is this yours or the ISPs? You need to verify that someone is not filtering ICMP or traceroute UDP packets to make sure it's not a red herring.
MikeS
Find me at
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin
11 206.46.160.253 64 msec 68 msec 76 msec
This is the problem child... the packets from the router lose their way at this hop.
Is this yours or the ISPs? You need to verify that someone is not filtering ICMP or traceroute UDP packets to make sure it's not a red herring.
MikeS
Find me at
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin
Your "modem" doesnt know here to go next to get to the server. Normally, the ISPs use the router as a bridge device.. ie.. completely open in both directions. Or thats is what they say 
For some reason.. when the packet gets to this "router".. it is either blocked ( firewall?, acces list ?) or there is not a route for the network you are trying to get to.
In the config you post there is this line..
access-list 1 permit 199.xxx.xxx.0 0.0.0.255
This access list permits ONLY 199.x.x.0-255 and denies everything else. Pull the access list off just for troubleshooting so there is one less variable in the way of resolution.
Another trick to do is provide a static mapped NAT entry to point all email traffic/port to as specific IP address without NATing it. Sometimes this can make a difference.
MikeS
Find me at
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin
For some reason.. when the packet gets to this "router".. it is either blocked ( firewall?, acces list ?) or there is not a route for the network you are trying to get to.In the config you post there is this line..
access-list 1 permit 199.xxx.xxx.0 0.0.0.255
This access list permits ONLY 199.x.x.0-255 and denies everything else. Pull the access list off just for troubleshooting so there is one less variable in the way of resolution.
Another trick to do is provide a static mapped NAT entry to point all email traffic/port to as specific IP address without NATing it. Sometimes this can make a difference.
MikeS
Find me at
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin
it might be interesting to see what happens with a debug of PPP... this router is configured with pppoe which is treated like a dialup connection.
I'll look the config over closer and think about it tomorrow..
MikeS Find me at
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin
I'll look the config over closer and think about it tomorrow..
MikeS Find me at
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin
MWM
MIS
- Aug 9, 2001
- 200
Alritter;
I notice one line in your config: IP route 0.0.0.0 0.0.0.0 Dialer1
The IOS does allow the interface name to be used here, but the packet is simply broadcast via the interface. The more correct way of directing traffic here, I understand, is to use the next-hop router address.
This tip came from Cicso tech support.
In the past I could ping using the interface name but not succeed with DNS until the route was changed to point directly to the next-hop router.
Best,
Mike
I notice one line in your config: IP route 0.0.0.0 0.0.0.0 Dialer1
The IOS does allow the interface name to be used here, but the packet is simply broadcast via the interface. The more correct way of directing traffic here, I understand, is to use the next-hop router address.
This tip came from Cicso tech support.
In the past I could ping using the interface name but not succeed with DNS until the route was changed to point directly to the next-hop router.
Best,
Mike
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- Question
