Re: [leaf-user] DSL troubleshooting.....
This cannot be a DNS issue. It's like saying, every time a plane flies over my house, the subway train that runs underneath it gets derailed. DSL modem sync is a Layer 2 function, whereas DNS is a Layer 7(?) function. (I'm talking about the OSI Layer Model. Layer 2 is Data Link, Layer 7 is application, though I'm too tired to place DNS accurately, so it might be in the 4-6 range.) More than likely, there's something screwy with your DSL modem and a request on port 80 is causing it to keel over. I would contact your DSL provider and request that they have the line tested - you'll need to be on hand for that - and if that doesn't turn anything up, see if they'll send you a replacement modem. Explain everything in detail to them when you call. If you want to verify that it isn't your Bering box before you call, just run the ethernet cable straight from the modem to your workstation, set whatever needs to be set for getting an IP address, and try accessing a website and see if it does the same thing. George John Mullan wrote: Can anyone give me hints about what to look for? My DSL modem (apparently) loses sync when I try to access an external web site. After it syncs back up, and I try again, I lose sync again. Ping works the same way except if I try to ping an IP rather than URL. Now this would seem to me to be a DNS problem. But can this be with my internal DNS or ISP's DNS ??? Could it be either? HISTORY: This is my home/personal network. I have Bering/Shorewall and it has been working up until yesterday. I have not made any changes in the last couple of days. I have a Win2K server (192.168.1.128) inside and it is the primary DNS of the internal network. Bering box (192.168.1.254) is secondary DNS (DNSCache). IE; Win2K will forward unresolved addresses to it (obvious!?!). Ideas please.. John (www.mullan.ca) == http://www.olgc.ca888-345-7568 ext. 2210 mailto:[EMAIL PROTECTED]416-213-2210 (direct) == If each of us have one object, and we exchange them, then each of us still has one object. If each of us have one idea, and we exchange them, then each of us now has two ideas. == KNOW YOUR LIMIT, PLAY WITHIN IT! ONTARIO PROBLEM GAMBLING HELPLINE 1 888 230-3505 DÉPASSER SES LIMITES, CE N'EST PLUS DU JEU. LA LIGNE ONTARIENNE D'AIDE SUR LE JEU PROBLÉMATIQUE1 888 230-3505 --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] DSL troubleshooting.....
At 07:41 AM 11/25/2003 -0500, John Mullan wrote: Can anyone give me hints about what to look for? My DSL modem (apparently) loses sync when I try to access an external web site. After it syncs back up, and I try again, I lose sync again. Ping works the same way except if I try to ping an IP rather than URL. Can you describe in a bit more detail what actual symptoms lie behind (apparently) loses sync and it syncs back up? Are you actually seeing the DSL modem's sync light (or whatever it is called on your device) go off, then back on? And, just to be sure, the problem is associated with *any* attempt at off-LAN DNS resolution (not just port-80 URLs), right? George's response is correct as far as it goes -- problems with a DSL modem's connectivity to your ISP are OSI layer-2, or possibly layer-1, problems, and (putting aside the possibility of some bizarre interaction deliberately introduced by your ISP, mentioned only because I don't put *anything* beyond sufficiently stupid ISPs) layer-3 (IP) and layer-4 (TCP, UDP) activities should not affect layer 2 (or 1). If your evidence for loss of sync is more indirect than what I write above, please provide additional details on the symptoms and on how you have DNS set up. If it is not more indirect, follow George's advice in the first instance. (Except focus on port 53, not port 80, if the problem occurs with pings by FQN as well as URLs). You might still want to tell us the rest of the details of your DNS setup and what sort of DSL service you have (that is, how you get your IP address ... it is PPPoE, for example). I can (just barely) imagine that your ISP is doing something silly to discourage its captives (pardon me, its customers) from bypassing its DNS forwarders. Now this would seem to me to be a DNS problem. But can this be with my internal DNS or ISP's DNS ??? Could it be either? HISTORY: This is my home/personal network. I have Bering/Shorewall and it has been working up until yesterday. I have not made any changes in the last couple of days. I have a Win2K server (192.168.1.128) inside and it is the primary DNS of the internal network. Bering box (192.168.1.254) is secondary DNS (DNSCache). IE; Win2K will forward unresolved addresses to it (obvious!?!). Ideas please.. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] DSL troubleshooting.....
OK. My evidence for 'loses sync': the lights labeled DSL and ATM on the modem go out. Flash for a while, then come back on. I can access any IP or URL that exists within the internal network. IE; a web server exists on host WWW (192.168.1.128) and I can access it via http://www or http://192.168.1.128 However, I cannot access http://www.google.com or others. If the modem is 'synced up', attempting to access an external page may start to load, but the lights again go out on the modem and the page is not displayed. DSL is PPPoE. I don't think I can be too much more specific on the DNS setup except standard DNSCache setup on the Bering box (ie; as suggested when setting up PPPoE). The Win2K machine is set as DNS server but to forward unresolved requests to the Bering box. The Bering box therefore, I believe, will be supplied DNS info from the ISP (Sympatico, by the way). Does this clarify? Ray Olszewski [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED]Subject: Re: [leaf-user] DSL troubleshooting. ceforge.net 11/25/2003 10:31 At 07:41 AM 11/25/2003 -0500, John Mullan wrote: Can anyone give me hints about what to look for? My DSL modem (apparently) loses sync when I try to access an external web site. After it syncs back up, and I try again, I lose sync again. Ping works the same way except if I try to ping an IP rather than URL. Can you describe in a bit more detail what actual symptoms lie behind (apparently) loses sync and it syncs back up? Are you actually seeing the DSL modem's sync light (or whatever it is called on your device) go off, then back on? And, just to be sure, the problem is associated with *any* attempt at off-LAN DNS resolution (not just port-80 URLs), right? George's response is correct as far as it goes -- problems with a DSL modem's connectivity to your ISP are OSI layer-2, or possibly layer-1, problems, and (putting aside the possibility of some bizarre interaction deliberately introduced by your ISP, mentioned only because I don't put *anything* beyond sufficiently stupid ISPs) layer-3 (IP) and layer-4 (TCP, UDP) activities should not affect layer 2 (or 1). If your evidence for loss of sync is more indirect than what I write above, please provide additional details on the symptoms and on how you have DNS set up. If it is not more indirect, follow George's advice in the first instance. (Except focus on port 53, not port 80, if the problem occurs with pings by FQN as well as URLs). You might still want to tell us the rest of the details of your DNS setup and what sort of DSL service you have (that is, how you get your IP address ... it is PPPoE, for example). I can (just barely) imagine that your ISP is doing something silly to discourage its captives (pardon me, its customers) from bypassing its DNS forwarders. Now this would seem to me to be a DNS problem. But can this be with my internal DNS or ISP's DNS ??? Could it be either? HISTORY: This is my home/personal network. I have Bering/Shorewall and it has been working up until yesterday. I have not made any changes in the last couple of days. I have a Win2K server (192.168.1.128) inside and it is the primary DNS of the internal network. Bering box (192.168.1.254) is secondary DNS (DNSCache). IE; Win2K will forward unresolved addresses to it (obvious!?!). Ideas please.. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE
Re: [leaf-user] DSL troubleshooting.....
At 01:30 PM 11/25/2003 -0500, John Mullan wrote: OK. My evidence for 'loses sync': the lights labeled DSL and ATM on the modem go out. Flash for a while, then come back on. Ok. Those labels don't match the lights on either of my DSL modems, but your interpretation of them sounds right. Since you use PPPoE, you actually have multiple layer 2 layers, each encapsulated in another. But these lights seem to imply either a layer-1 (physical layer) failure of some sort or a failure of the lowest layer 2 (whatever native protocol the DSL circuit itself uses, something that will encapsulate the Ethernet frames on the far side of the DSL modem and be invisible to your router). I can access any IP or URL that exists within the internal network. IE; a web server exists on host WWW (192.168.1.128) and I can access it via http://www or http://192.168.1.128 This would be true whatever the source of the proboem is. However, I cannot access http://www.google.com or others. If the modem is 'synced up', attempting to access an external page may start to load, but the lights again go out on the modem and the page is not displayed. If the page may start to load, then any DNS requests have been processed successfully. This implies that the problem is not specifically with DNS. DSL is PPPoE. I don't think I can be too much more specific on the DNS setup except standard DNSCache setup on the Bering box (ie; as suggested when setting up PPPoE). The Win2K machine is set as DNS server but to forward unresolved requests to the Bering box. The Bering box therefore, I believe, will be supplied DNS info from the ISP (Sympatico, by the way). No need for more detail here, i think. Does this clarify? Mostly. Your earlier message said, as I read it, that you had sync problems (Ping works the same way) if you ping by FQN but not if you ping by IP address. Based on the added information you just supplied about http problems, I suspect it would be worth knowing more about other services (including ping) and how they react. For example ... 1. Can you connect to an offsite Web page by IP address? 2. Can you do a traceroute by (a) FQN and (b) IP address? More generally, what *can* you do with any reliability over this connection? More and more, this sounds like a line problem ... either a physical problem with the line or the DSL modem, or something at the ISP end ... but one that only manifests itself when you use more than a trivial amount of bandwidth. That is, George's initial guess appears to have been on target (except perhaps for the pat that associates the problem with port 80). [old stuff deleted] --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] DSL troubleshooting.....
Hmmm. Physical line problems?? Perhaps this should have been my first line of attack :-( since it seemed to happen suddenly. I will go around and make sure nobody fiddled with any of the filters! Of course, this will have to wait until I get home in an hour or two. As one of my tech teachers used to say NEVER OVERLOOK THE OBVIOUS. Ray Olszewski [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED]Subject: Re: [leaf-user] DSL troubleshooting. ceforge.net 11/25/2003 13:58 At 01:30 PM 11/25/2003 -0500, John Mullan wrote: OK. My evidence for 'loses sync': the lights labeled DSL and ATM on the modem go out. Flash for a while, then come back on. Ok. Those labels don't match the lights on either of my DSL modems, but your interpretation of them sounds right. Since you use PPPoE, you actually have multiple layer 2 layers, each encapsulated in another. But these lights seem to imply either a layer-1 (physical layer) failure of some sort or a failure of the lowest layer 2 (whatever native protocol the DSL circuit itself uses, something that will encapsulate the Ethernet frames on the far side of the DSL modem and be invisible to your router). I can access any IP or URL that exists within the internal network. IE; a web server exists on host WWW (192.168.1.128) and I can access it via http://www or http://192.168.1.128 This would be true whatever the source of the proboem is. However, I cannot access http://www.google.com or others. If the modem is 'synced up', attempting to access an external page may start to load, but the lights again go out on the modem and the page is not displayed. If the page may start to load, then any DNS requests have been processed successfully. This implies that the problem is not specifically with DNS. DSL is PPPoE. I don't think I can be too much more specific on the DNS setup except standard DNSCache setup on the Bering box (ie; as suggested when setting up PPPoE). The Win2K machine is set as DNS server but to forward unresolved requests to the Bering box. The Bering box therefore, I believe, will be supplied DNS info from the ISP (Sympatico, by the way). No need for more detail here, i think. Does this clarify? Mostly. Your earlier message said, as I read it, that you had sync problems (Ping works the same way) if you ping by FQN but not if you ping by IP address. Based on the added information you just supplied about http problems, I suspect it would be worth knowing more about other services (including ping) and how they react. For example ... 1. Can you connect to an offsite Web page by IP address? 2. Can you do a traceroute by (a) FQN and (b) IP address? More generally, what *can* you do with any reliability over this connection? More and more, this sounds like a line problem ... either a physical problem with the line or the DSL modem, or something at the ISP end ... but one that only manifests itself when you use more than a trivial amount of bandwidth. That is, George's initial guess appears to have been on target (except perhaps for the pat that associates the problem with port 80). [old stuff deleted] --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net
