Welcome to Networking. TIPS inside.

[Byte 2.0]

Ok, i am in the process of cleaning up the sticky threads in Networking. This process is going to take a little bit of time as I carefully review them and copy then over here.

LINKS

Sync no surf, can't connect to your Router? simple test

Default Router IP address/logins

Router setups and tutorials

How to Secure a Network

[Byte 2.0]

Sync no surf, can't connect to your Router? simple test
________________________________________
OK, as many of you know I deal with several ADSL modems and Cable modems in my line of work. I deal with allot of the Tough cases at work and some of the most difficult ones are when everything is OK, on the NSP/ISP side.

Some of the tough ones are with several types of Winsock damage, some of which LSPfix is even unable to correct.


Example, you have your router connected to your NIC and you can pull an IP address from the router but are unable to surf into the interface of the router.

Example 2, you have a PPPoE (DSL Connection that users a user name and password to connect) you are able to connect pull an IP address but still can't surf.

Example 3, you have a cable connection, pull an IP from your provider but are unable to surf.

Here is a simple test to get started to see if the problem is on your side.

Go to the ms dos prompt inside windows.
Windows 2000/xp
Start > Run cmd
Windows 98/ME
Start > Run >command

type in ftp 127.0.0.1

What you are looking for is the error message you get back.

If you get a Socket 0, Socket 10047, or Socket 10093 then you have a damaged winsock and you will not be able to surf pages on the INTERNET or even surf into your own Router.

There are several Fixes available, depending on OS/Error combo and I would like to try to build a bit more of a check list and suggested fix, however time is a limiting factor.


Also, there are other ways to find out if you have a damaged winsock.
If you are connected but can't surf, pulling IP from your ISP.

If you can ping IP but not Host, Example

from command prompt
ping 216.239.41.104 (google)
and you get your replys

ping www.google.com gives you an error like unknown host.

IF both of those are true and you try an FTP command you will most likely get a socket 10047 which means you will not be able to surf, until it is repaired.


On my current, prefectly working connection, when I do that command I get connection refused.

If you get error 10047 it is to run a winsock repair program.

WinsockXPFix is currently the best program I know of to repair this type of Damage.

[Byte 2.0]

I want to make a post and list as many of the routers/modems as I can here. I want to include the default IP address to surf into them from computers

3Com 192.168.1.1 default password admin

Linksys 192.168.1.1
Linksys default user - (blank), password - admin
or default user admin Password is "password"

* Some of the new Linksys routers are 192.168.1.1 with the full word "administrator" as the log in and a blank password

Broadmax UHP ADSL modem - 172.16.0.254

DLink 192.168.0.1
D-Link default user - admin, password - (blank)

Netgear 192.168.0.1 default user/password admin / password

Homeportal DSL modem 172.16.0.1

Westell DSL 2100 modem 192.168.1.254

SMC barricade SMC7004ABR although it should be the same accross the range
ip: 192.168.2.1
no user name
password = blank by default

Motorola Surfboard 4100 and 3100 ip: 192.168.100.1

USR 8000A broadband router ip 192.168.123.254

Belkin router the access IP is 192.168.2.1 with a default user name "admin" and a blank password.

Compaq CP-2W
username= admin
password= (blank)
IP address 192.168.1.1
IP range 192.168.1.11 -254

wanadoo livebox 192.168.1.1 default password admin

Airlink: def admin un/pw: admin/admin
def. ip 192.168.1.1


Special thanks to GLC, Allanv, Nuclear Krusader, QuickSilver, videobruce, lil Jimmie, RacybabeUK, PC_Master, & DynamicTech for helping with the list.