reptilicus Posted November 16, 2012 Posted November 16, 2012 Hi. I've been using a modified version of Win7 for over two years now, being able to perfectly connect via DSL modem. But now i have to set up a wireless router (my girlfriend needs internet in her cell phone) and I'm having trouble setting up the device.Would someone help me eliminate (or confirm) a component removed with WinToolkit as the source of the problem? This is the list of things that I've removed in "Networking":- Active Directory application mode- BranchCache- HomeGroup- Offlines files- Peer networking infrastructure- RAS Connection Manager Administration Kit (CMAK)- Remote assistance- Remote desktop services (3 components)- Remote differential compression- Remote FX (2 components)- RIP Listener- Simple network managment protocol (SNMP)- Simple TCP Services- Subsystem for UNIX bases Applicactions- Telnet client- Telnet server- TFTP Client- WMI SNMP ProviderThanks in advance, and excuse my English -- not my native language. Quote
yogurt Posted November 16, 2012 Posted November 16, 2012 (edited) I dont think removing network components is going to solve your problem. It sounds like the problem may lie within your routers configuration. Can you provide more details about the connection issues you are having? Have you tried calling your Internet Service Provider for help? You may want to request that your question be moved to The Hardware Field Fourm. Edited November 16, 2012 by dotfusion Quote
Eric666 Posted November 16, 2012 Posted November 16, 2012 Repticilus,I've removed most of the components you mention on my own installation except for these 4:- Remote assistance- Remote desktop services (3 components)- Remote differential compression- Remote FX (2 components).Wireless networking works fine with me. Your problem is probably not the absence of those components, but as Dotfusion already said something in your router's configuration. It may even be broken.... Note that to configure a router properly you need to make a wired connection first. And your NIC needs to be set to obtain an IP address automatically. If you also have a wireless NIC in your computer, use inSSIDer to check if the router is doing anything wireless at all.Regards, Eric666 Quote
reptilicus Posted November 16, 2012 Author Posted November 16, 2012 (edited) Have you tried calling your Internet Service Provider for help?I thought about it, but I wanted to be sure about the "components removed factor" first. I'm afraid that If I say to my ISP tech support that I have a "customized Windows", they wouldn't help me at all.I've removed most of the components you mention on my own installation except for these 4:That give me something to sart with. I'll plug the router again tonight and give it a try. I will also try that tool you mentioned.Eric & dotfussion, thanks for the help. I'll post the solution, only to rule out (or confirm) those removed components as a problem to wireless connections. Edited November 16, 2012 by reptilicus Quote
reptilicus Posted November 18, 2012 Author Posted November 18, 2012 Sorry, no luck. Put some services in Automatic (Automatic WLAN/WWAN configuration), but didn't work. Error given is "Chek the WAN connection", but that is another forum's theme. One thing I did was retrieving Windows Services to default, and the software I used ("ServicesSuite") said that it couldn't find Net.MSMQ - Net.Pipe & Net.TCP. Ring a bell?I think the best thing to do is a normal Win7 installation, so I can eliminate the "missing components/services" theory. Quote
yogurt Posted November 19, 2012 Posted November 19, 2012 Error given is "Chek the WAN connection"Have you tried checking your routers WAN settings? Sounds like your router is having problems making a connection with your ISP's gateway. Does the LAN (Local Area Network) work? What is the model # of your router? Quote
reptilicus Posted November 19, 2012 Author Posted November 19, 2012 Router is TL-WR740N.Just connected it again following the on-screen instructions from the installer assistant.The LED Indicator Description part seems OK.- WLAN light flashing: wireless function enabled.- WAN & LAN fixed, but they'll start flashing later: sending or receiving data (this happens when I try to load a webpage, but I get a "Server not found" error in browser."Check Router's Connectivity" screen: OK for "Network adapter enabled".After chosing WAN type (PPPoE), security and WIFI name, comes the "Configure Router" screen...and the error.- "1) Please check the WAN connection type and parameters"- "2) Please check your network connectivity and retry"I wouldn't know about errors in the WAN settings. I think I'm doing it all by the book.How do I check if LAN is working ok?Thanks for the help, dotfusion. Quote
yogurt Posted November 19, 2012 Posted November 19, 2012 (edited) @reptilicusThese lights will typicaly flash even if you are receiving errors. At least it shows that their is some sort of trafic passing thru. The "Server not found" error is most likely occuring because something on the WAN (ISP) side of the network is not configured right. Hence, this is why you are getting the "Check Router's Connectivity" error form your routers setup wizard.WAN type (PPoE) is for DSL / ADSL Connections. With this type of connection you need to enter your DSL user name and password from your ISP in to the routers configuration. Also, you need to verify that only one device (Modem or Router) is actincg as a DHCP server. Not both. DHCP is what gives all computers connected to the LAN an IP adddress. Having DHCP enabled on both devices will cause the types of errors you are experiencing.On the other hand if you have a Cable connection (Non-DSL) then your WAN type has to be set to Cable or DHCP and does not require you to enter a user name or password to access the WAN (Internet Gateway). Also only one device can act as a DHCP server.LAN connection can be tested by sending a ping to any known IP address that is connected to the LAN (example the IP address of your router), but i would'nt worry about the LAN until you have the WAN sorted out. What happens when you try to ping a WAN address for example "ping microsoft.com"Can you bring up a command prompt and type this "ipconfig /all" without the quotation marks and post the results. It would realy help in pin pointing the problem. Also what is the Model # of your ISP's Modem? Edited November 19, 2012 by dotfusion Quote
reptilicus Posted November 20, 2012 Author Posted November 20, 2012 (edited) @ dotfusionOk, let's see...- DLS username & password are ok. Check that.- ISP Modem is an Alcatel Speed Touch 510- I'm pasting ipconfig results. In Spanish, I'm afraid. Feel free to ask for clarification when needed.PS: DHCP seems only enabled in "Adaptador de Ethernet Conexión de área local" (Local area Ethernet Adapter, I think is the translation)Configuración IP de WindowsNombre de host. . . . . . . . . : win7pc11Sufijo DNS principal . . . . . :Tipo de nodo. . . . . . . . . . : híbridoEnrutamiento IP habilitado. . . : noProxy WINS habilitado . . . . . : noAdaptador de Ethernet Conexión de área local:Sufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : Realtek PCIe FE Family ControllerDirección física. . . . . . . . . . . . . : 00-25-22-45-D0-BDDHCP habilitado . . . . . . . . . . . . . : síConfiguración automática habilitada . . . : síVínculo: dirección IPv6 local. . . : fe80::29c9:c230:8b04:4aa0%11(Preferido)Dirección IPv4. . . . . . . . . . . . . . : 192.168.0.100(Preferido)Máscara de subred . . . . . . . . . . . . : 255.255.255.0Concesión obtenida. . . . . . . . . . . . : lunes, 19 de noviembre de 2012 11:30:08 p.m.La concesión expira . . . . . . . . . . . : martes, 20 de noviembre de 2012 01:30:08 a.m.Puerta de enlace predeterminada . . . . . : 192.168.0.1Servidor DHCP . . . . . . . . . . . . . . : 192.168.0.1IAID DHCPv6 . . . . . . . . . . . . . . . : 234890530DUID de cliente DHCPv6. . . . . . . . . . : 00-01-00-01-16-01-47-E7-00-25-22-45-D0-BDServidores DNS. . . . . . . . . . . . . . : 192.168.0.1NetBIOS sobre TCP/IP. . . . . . . . . . . : habilitadoAdaptador de Ethernet VirtualBox Host-Only Network:Sufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : VirtualBox Host-Only Ethernet AdapterDirección física. . . . . . . . . . . . . : 08-00-27-00-C0-CADHCP habilitado . . . . . . . . . . . . . : noConfiguración automática habilitada . . . : síVínculo: dirección IPv6 local. . . : fe80::e04a:8caa:34d0:c5cc%17(Preferido)Dirección IPv4. . . . . . . . . . . . . . : 192.168.56.1(Preferido)Máscara de subred . . . . . . . . . . . . : 255.255.255.0Puerta de enlace predeterminada . . . . . :IAID DHCPv6 . . . . . . . . . . . . . . . : 336068647DUID de cliente DHCPv6. . . . . . . . . . : 00-01-00-01-16-01-47-E7-00-25-22-45-D0-BDServidores DNS. . . . . . . . . . . . . . : fec0:0:0:ffff::1%1fec0:0:0:ffff::2%1fec0:0:0:ffff::3%1NetBIOS sobre TCP/IP. . . . . . . . . . . : habilitadoAdaptador de túnel isatap.{F27B041F-9E10-498C-AC94-CD210487CC40}:Estado de los medios. . . . . . . . . . . : medios desconectadosSufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : Adaptador ISATAP de MicrosoftDirección física. . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0DHCP habilitado . . . . . . . . . . . . . : noConfiguración automática habilitada . . . : síAdaptador de túnel isatap.{4CA98274-B946-4ACD-B84B-7271B21EF1E0}:Estado de los medios. . . . . . . . . . . : medios desconectadosSufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : Adaptador ISATAP de Microsoft #2Dirección física. . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0DHCP habilitado . . . . . . . . . . . . . : noConfiguración automática habilitada . . . : síAdaptador de túnel Teredo Tunneling Pseudo-Interface:Estado de los medios. . . . . . . . . . . : medios desconectadosSufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : Teredo Tunneling Pseudo-InterfaceDirección física. . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0DHCP habilitado . . . . . . . . . . . . . : noConfiguración automática habilitada . . . : sí Edited November 20, 2012 by reptilicus Quote
yogurt Posted November 20, 2012 Posted November 20, 2012 it looks like your router is not communicating with the WAN connection. It also appears that your Modem is not on the same Subnet as your modem.Can you plug the modem directly to your PC without going thru the router and run "ipconfig /all" This will allow us to determine if your modem is infact on the same subnet at your router. Do you know how to access your routers configuration page? For this you would need to plug the modem directly to your PC and access it's local IP address with a web browser example http://192.168.0.1. I strongly beleive that your problem lies within a conflicting DHCP setting on your Alcatel Modem. Quote
reptilicus Posted November 20, 2012 Author Posted November 20, 2012 (edited) ipconfig /all with modem-to-pc. Where can I identify the subnet?Edit: Got it, in Máscara de subred . . . . . . . . . . . . : 255.255.255.255When I did ipconfig with router plugged in, it was 255.255.255.0Do you know how to access your routers configuration page? For this you would need to plug the modem directly to your PC and access it's local IP address with a web browser example http://192.168.0.1I'm a little confuse. You mean the router, not the modem, right? Yes, I've being digging around in the configuration page, even take de config to default from there, just to be sure.Configuración IP de WindowsNombre de host. . . . . . . . . : win7pc11Sufijo DNS principal . . . . . :Tipo de nodo. . . . . . . . . . : híbridoEnrutamiento IP habilitado. . . : noProxy WINS habilitado . . . . . : noAdaptador PPP ADSL:Sufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : ADSLDirección física. . . . . . . . . . . . . :DHCP habilitado . . . . . . . . . . . . . : noConfiguración automática habilitada . . . : síDirección IPv4. . . . . . . . . . . . . . : 186.52.47.142(Preferido)Máscara de subred . . . . . . . . . . . . : 255.255.255.255Puerta de enlace predeterminada . . . . . : 0.0.0.0Servidores DNS. . . . . . . . . . . . . . : 200.40.220.245200.40.30.245NetBIOS sobre TCP/IP. . . . . . . . . . . : deshabilitadoAdaptador de Ethernet Conexión de área local:Sufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : Realtek PCIe FE Family ControllerDirección física. . . . . . . . . . . . . : 00-25-22-45-D0-BDDHCP habilitado . . . . . . . . . . . . . : síConfiguración automática habilitada . . . : síVínculo: dirección IPv6 local. . . : fe80::29c9:c230:8b04:4aa0%11(Preferido)Dirección IPv4 de configuración automática: 169.254.74.160(Preferido)Máscara de subred . . . . . . . . . . . . : 255.255.0.0Puerta de enlace predeterminada . . . . . :IAID DHCPv6 . . . . . . . . . . . . . . . : 234890530DUID de cliente DHCPv6. . . . . . . . . . : 00-01-00-01-16-01-47-E7-00-25-22-45-D0-BDServidores DNS. . . . . . . . . . . . . . : fec0:0:0:ffff::1%1fec0:0:0:ffff::2%1fec0:0:0:ffff::3%1NetBIOS sobre TCP/IP. . . . . . . . . . . : habilitadoAdaptador de Ethernet VirtualBox Host-Only Network:Sufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : VirtualBox Host-Only Ethernet AdapterDirección física. . . . . . . . . . . . . : 08-00-27-00-C0-CADHCP habilitado . . . . . . . . . . . . . : noConfiguración automática habilitada . . . : síVínculo: dirección IPv6 local. . . : fe80::e04a:8caa:34d0:c5cc%17(Preferido)Dirección IPv4. . . . . . . . . . . . . . : 192.168.56.1(Preferido)Máscara de subred . . . . . . . . . . . . : 255.255.255.0Puerta de enlace predeterminada . . . . . :IAID DHCPv6 . . . . . . . . . . . . . . . : 336068647DUID de cliente DHCPv6. . . . . . . . . . : 00-01-00-01-16-01-47-E7-00-25-22-45-D0-BDServidores DNS. . . . . . . . . . . . . . : fec0:0:0:ffff::1%1fec0:0:0:ffff::2%1fec0:0:0:ffff::3%1NetBIOS sobre TCP/IP. . . . . . . . . . . : habilitadoAdaptador de túnel isatap.{F27B041F-9E10-498C-AC94-CD210487CC40}:Estado de los medios. . . . . . . . . . . : medios desconectadosSufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : Adaptador ISATAP de MicrosoftDirección física. . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0DHCP habilitado . . . . . . . . . . . . . : noConfiguración automática habilitada . . . : síAdaptador de túnel isatap.{4CA98274-B946-4ACD-B84B-7271B21EF1E0}:Estado de los medios. . . . . . . . . . . : medios desconectadosSufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : Adaptador ISATAP de Microsoft #2Dirección física. . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0DHCP habilitado . . . . . . . . . . . . . : noConfiguración automática habilitada . . . : síAdaptador de túnel 6TO4 Adapter:Sufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : Adaptador 6to4 de MicrosoftDirección física. . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0DHCP habilitado . . . . . . . . . . . . . : noConfiguración automática habilitada . . . : síDirección IPv6 . . . . . . . . . . : 2002:ba34:2f8e::ba34:2f8e(Preferido)Puerta de enlace predeterminada . . . . . : 2002:c058:6301::c058:6301Servidores DNS. . . . . . . . . . . . . . : 200.40.220.245200.40.30.245NetBIOS sobre TCP/IP. . . . . . . . . . . : deshabilitadoAdaptador de túnel isatap.{0E475A27-6402-4F7A-9BA4-8DE24C4E0040}:Estado de los medios. . . . . . . . . . . : medios desconectadosSufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : Adaptador ISATAP de Microsoft #3Dirección física. . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0DHCP habilitado . . . . . . . . . . . . . : noConfiguración automática habilitada . . . : síAdaptador de túnel Teredo Tunneling Pseudo-Interface:Estado de los medios. . . . . . . . . . . : medios desconectadosSufijo DNS específico para la conexión. . :Descripción . . . . . . . . . . . . . . . : Teredo Tunneling Pseudo-InterfaceDirección física. . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0DHCP habilitado . . . . . . . . . . . . . : noConfiguración automática habilitada . . . : si Edited November 20, 2012 by reptilicus Quote
yogurt Posted November 20, 2012 Posted November 20, 2012 (edited) Bingo! This is where your problem is. The problem is with DHCP and DNS.Dirección IPv4 de configuración automática: 169.254.74.160(Preferido)This sort of problem can be verry difficult to troubleshoot via forums, But I am sure if you speak to your ISP and provide the technician with the same information you posted. They will know and tell you how to configure your modem and router to work with their network.Your modem needs to be configured to be be on the same subnet as your router and DHCP needs to be disabled on the modem. Your modem has a built in router, so when you plug your Alcatel Modem which is also a router in the WAN port of your TL-WR740N, both devices start to conflict with each other because they are both acting as DHCP servers (Routers). This is why you are getting the 169.x.x.x IP and a conflicting subnet. Not to mention DNS errors.Trust me, call your ISP and they will help you setup both devices to play nice. Why are you using two routers. I assume one provides Wireless and the other does not. Edited November 20, 2012 by dotfusion Quote
reptilicus Posted November 20, 2012 Author Posted November 20, 2012 Wow, thanks. I'll look for tech support, but i'll do a little googling first and see if I come up with something.I didn't know my modem had a built in router, I'm looking for some tech info about it. Best part of this is that, if it works, I'm not modifying my WinToolkit settings for leaving those components alone. I'm a kind of a "slim down" fanatic.If it works, I'll post result and give some kind of closure for the case. Thanks again for your time and help! Quote
yogurt Posted November 20, 2012 Posted November 20, 2012 (edited) FYI: Removing components from a Windows image can cause problems for you in the future. For example you may have problems when a new Service Pack is released and you try to install it. Anyhow, just my opinion on Component Removal. Here are a couple of links for your review and consideration.SpeedTouchReview and Technical Specs Edited November 20, 2012 by dotfusion Quote
reptilicus Posted November 20, 2012 Author Posted November 20, 2012 (edited) @dotfusionI've looking around for Speed Touch 510 specs, and several models came up in Google. This is more like the one I have:http://www.ovislink..../SpeedTouch.asphttps://service.symp...content_id=1256Sorry if I missguided you, but there is a label in the bottom that clearly says "SpeedTouch 510".Edit: I'm trying to find out about compatibility issues between modem and router. Will report leater. Edited November 20, 2012 by reptilicus Quote
yogurt Posted November 20, 2012 Posted November 20, 2012 I know this model well also. The setup for this model is pretty straight forward. As I said, your ISP well surely be able to assist you in getting your modem to work with your reouter. This thread seems to have gotten off topic. I you need any further help, you can send me a PM and I'll reply if I can. Or you can move your question to the hardware field forum where someone may be able to assist us further. Best regards. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.