SuSE 9.2 Slow Internet (Samba PDC)
I'm experiencing very slow internet speeds on network. SuSE Pro 9.2 as Samba PDC Smoothwall Express 2.0 Firewall (DHCP Server) (3) Windows XP Pro workstations (1) Windows 98 SE workstation D-Link 16 port switch Verizon DSL connection Browsing speeds on the SuSE server are very slow. The initial page loading takes several seconds and sometimes I get a time out error. When trying to do online updates through YOU, I often get errors stating YOU was unable to connect. Eventually after trying several times, it will go through. Prior to the XP boxes joining the domain, web browsing from the XP boxes was very fast. I don't think this is a problem with the Smoothwall Firewall, since the XP boxes were going through Smoothwall prior to joining the domain. Since joining the domain, the XP boxes are now exhibiting the same symptoms as the server (extremely slow speeds and occassional time out errors). My thoughts are that this is a problem with the SuSE server since I have slow internet when logging in as a user on the server, and since after joining the domain, the XP boxes now have slow internet access. I'm not sure what's going on. Any advice would be greatly appreciated. If you need more info, let me know. Thanks! Mike
On Apr 7, 2005 9:05 AM, Lake-Wind
I'm experiencing very slow internet speeds on network.
SuSE Pro 9.2 as Samba PDC
Smoothwall Express 2.0 Firewall (DHCP Server)
(3) Windows XP Pro workstations
(1) Windows 98 SE workstation
D-Link 16 port switch
Verizon DSL connection
Browsing speeds on the SuSE server are very slow. The initial page loading takes several seconds and sometimes I get a time out error. When trying to do online updates through YOU, I often get errors stating YOU was unable to connect. Eventually after trying several times, it will go through.
Prior to the XP boxes joining the domain, web browsing from the XP boxes was very fast. I don't think this is a problem with the Smoothwall Firewall, since the XP boxes were going through Smoothwall prior to joining the domain. Since joining the domain, the XP boxes are now exhibiting the same symptoms as the server (extremely slow speeds and occassional time out errors).
My thoughts are that this is a problem with the SuSE server since I have slow internet when logging in as a user on the server, and since after joining the domain, the XP boxes now have slow internet access.
I'm not sure what's going on. Any advice would be greatly appreciated. If you need more info, let me know.
Thanks! Mike
Are you using the SuSE box for dns also? If so, stop using it and point your boxes to an external dns (your isp), preferably mutilple dns servers, and see if this speeds things up. If so, verify the configuration. Also, have you sniffed your network yet to check for problems? John
On Fri, 8 Apr 2005 23:09:48 -0400, you wrote:
On Apr 7, 2005 9:05 AM, Lake-Wind
wrote: I'm experiencing very slow internet speeds on network.
SuSE Pro 9.2 as Samba PDC
Smoothwall Express 2.0 Firewall (DHCP Server)
(3) Windows XP Pro workstations
(1) Windows 98 SE workstation
D-Link 16 port switch
Verizon DSL connection
Browsing speeds on the SuSE server are very slow. The initial page loading takes several seconds and sometimes I get a time out error. When trying to do online updates through YOU, I often get errors stating YOU was unable to connect. Eventually after trying several times, it will go through.
Prior to the XP boxes joining the domain, web browsing from the XP boxes was very fast. I don't think this is a problem with the Smoothwall Firewall, since the XP boxes were going through Smoothwall prior to joining the domain. Since joining the domain, the XP boxes are now exhibiting the same symptoms as the server (extremely slow speeds and occassional time out errors).
My thoughts are that this is a problem with the SuSE server since I have slow internet when logging in as a user on the server, and since after joining the domain, the XP boxes now have slow internet access.
I'm not sure what's going on. Any advice would be greatly appreciated. If you need more info, let me know.
Thanks! Mike
Are you using the SuSE box for dns also? If so, stop using it and point your boxes to an external dns (your isp), preferably mutilple dns servers, and see if this speeds things up. If so, verify the configuration.
My $0.02 - Verizon DNS servers are VERY slow - look into setting up a local caching dns server. Mike- -- Mornings: Evolution in action. Only the grumpy will survive. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments.
On Apr 9, 2005 5:12 PM, Michael W Cocke
On Fri, 8 Apr 2005 23:09:48 -0400, you wrote:
On Apr 7, 2005 9:05 AM, Lake-Wind
wrote: I'm experiencing very slow internet speeds on network.
SuSE Pro 9.2 as Samba PDC
Smoothwall Express 2.0 Firewall (DHCP Server)
(3) Windows XP Pro workstations
(1) Windows 98 SE workstation
D-Link 16 port switch
Verizon DSL connection
Browsing speeds on the SuSE server are very slow. The initial page loading takes several seconds and sometimes I get a time out error. When trying to do online updates through YOU, I often get errors stating YOU was unable to connect. Eventually after trying several times, it will go through.
Prior to the XP boxes joining the domain, web browsing from the XP boxes was very fast. I don't think this is a problem with the Smoothwall Firewall, since the XP boxes were going through Smoothwall prior to joining the domain. Since joining the domain, the XP boxes are now exhibiting the same symptoms as the server (extremely slow speeds and occassional time out errors).
My thoughts are that this is a problem with the SuSE server since I have slow internet when logging in as a user on the server, and since after joining the domain, the XP boxes now have slow internet access.
I'm not sure what's going on. Any advice would be greatly appreciated. If you need more info, let me know.
Thanks! Mike
Are you using the SuSE box for dns also? If so, stop using it and point your boxes to an external dns (your isp), preferably mutilple dns servers, and see if this speeds things up. If so, verify the configuration.
My $0.02 - Verizon DNS servers are VERY slow - look into setting up a local caching dns server.
Mike-
-- Mornings: Evolution in action. Only the grumpy will survive. --
Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments.
Agree about Verizon. My father-in-law does dsl and the name resolution bites. Get more than two boxes sharing the connection and somebody isn't going to be happy. Another of my in-laws uses Verizon for business dsl and he isn't real happy with that either. Pays twice the residential price and Verizon can't keep the link up to his site. He has to reboot his Westell modem a few times a day. I think I'll stay with cable for now. Agree about setting up a caching dns, that'll help speed up the name resolution process. John
On Sat, 2005-04-09 at 23:06 -0400, John Scott wrote:
On Apr 9, 2005 5:12 PM, Michael W Cocke
wrote:
Agree about Verizon. My father-in-law does dsl and the name resolution bites. Get more than two boxes sharing the connection and somebody isn't going to be happy.
Another of my in-laws uses Verizon for business dsl and he isn't real happy with that either. Pays twice the residential price and Verizon can't keep the link up to his site. He has to reboot his Westell modem a few times a day. Sounds like he is cross-connected with someone else. I had the same problem at one point with my DSL and a tech had to go to the CO and put me on a different connection. Just a thought.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Sat, 9 Apr 2005 23:06:27 -0400, you wrote:
On Apr 9, 2005 5:12 PM, Michael W Cocke
wrote: On Fri, 8 Apr 2005 23:09:48 -0400, you wrote:
On Apr 7, 2005 9:05 AM, Lake-Wind
wrote: I'm experiencing very slow internet speeds on network.
SuSE Pro 9.2 as Samba PDC
Smoothwall Express 2.0 Firewall (DHCP Server)
(3) Windows XP Pro workstations
(1) Windows 98 SE workstation
D-Link 16 port switch
Verizon DSL connection
Browsing speeds on the SuSE server are very slow. The initial page loading takes several seconds and sometimes I get a time out error. When trying to do online updates through YOU, I often get errors stating YOU was unable to connect. Eventually after trying several times, it will go through.
Prior to the XP boxes joining the domain, web browsing from the XP boxes was very fast. I don't think this is a problem with the Smoothwall Firewall, since the XP boxes were going through Smoothwall prior to joining the domain. Since joining the domain, the XP boxes are now exhibiting the same symptoms as the server (extremely slow speeds and occassional time out errors).
My thoughts are that this is a problem with the SuSE server since I have slow internet when logging in as a user on the server, and since after joining the domain, the XP boxes now have slow internet access.
I'm not sure what's going on. Any advice would be greatly appreciated. If you need more info, let me know.
Thanks! Mike
Are you using the SuSE box for dns also? If so, stop using it and point your boxes to an external dns (your isp), preferably mutilple dns servers, and see if this speeds things up. If so, verify the configuration.
My $0.02 - Verizon DNS servers are VERY slow - look into setting up a local caching dns server.
Mike-
-- Mornings: Evolution in action. Only the grumpy will survive. --
Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments.
Agree about Verizon. My father-in-law does dsl and the name resolution bites. Get more than two boxes sharing the connection and somebody isn't going to be happy.
Another of my in-laws uses Verizon for business dsl and he isn't real happy with that either. Pays twice the residential price and Verizon can't keep the link up to his site. He has to reboot his Westell modem a few times a day.
I think I'll stay with cable for now.
Agree about setting up a caching dns, that'll help speed up the name resolution process.
John
I've tried to use cable modems with 4 different providers, from NW Pennsylvania to Long Island. They all want to _sell_ the service, but none of them want you to actually _use_ the service. Bandwidth caps, blocked ports, yada yada. Screw that. I'm on an AT&T dsl here, and fairly happy. I have a client on verizon business dsl, and aside from needing a dns they're in good shape. The Westell is a pain to set up properly but after that it's pretty solid - sounds like your in-laws have a hardware problem. Mike- -- Mornings: Evolution in action. Only the grumpy will survive. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments.
participants (4)
-
John Scott
-
Ken Schneider
-
Lake-Wind
-
Michael W Cocke