On Mon, 14 Jan 2008 18:56:48 -0600, dvilimek
<dvilimek.338c8b@no.email.invalid> wrote:
>
>Hello,
>
>Having issues with my broadband LAN connection, and even my ISP has
>given up. I’ve recently moved from Bell Sympatico to Rogers Hi-Speed –
>I’ve never got my PC to work with the Rogers modem, but my fiancée’s Mac
>works fine with the modem. Here are the details:
>
>• PC is plugged directly into modem; there are no issues with limited
>on no connectivity – it says the LAN is “connected”
Ok, I ask a bit about this below just to clarify but
basically this just means a network connection is
established between the two but not much else.
>• ISP was able to detect connection, but could not explain lack of
>Internet activity
By connection they probably mean the modem, possibly a host
connected to it (though in my experience they usually mean
the modem)?
>• ipconfig release and renew have done nothing – according to ISP, the
>IP address is fine (ie. It is not starting with “169.254”
>• TCP/IP protocol set to obtain IP and DNS server addresses
>automatically
>• I’m seeing very low packet volume received
>• Norton Firewall is disabled/Windows XP firewall is off as well
>• Network card is Broadcom 440x 10/100 Integrated Controller
>• Driver edition is 4.25.0.0
Have you otherwise been able to use this network adapter to
connect to anything? I mean the broadcom ethernet one
specifically not the wireless.
>• OS is Windows XP Home Edition Version 2002 Service Pack 2
>• Model: Dell Inspiron 6000
>
>It is evident to me that something is blocking the connection – I’ve
>had this happen to me before when I would try to use broadband wired
>connections in various hotels. Wireless connections always worked
>though.
Frankly, I would not troubleshoot this if I were you, I
would buy a wifi router as it not only provides wireless
access which is very desirable with a laptop, but it also
provides an extra layer of security over having a windows
system directly connected to the internet. Granted wifi is
also a security risk in itself, but online networking
tutorials can show how to mitigate that risk, and if it
still seems too large a risk you could always connect the
systems using ethernet and disable the wireless feature of a
router. It need not be an expensive router, a basic
802.11g can be found occasionally for as cheap as free to
$10-20 after a rebate. Especially having multiple systems
on the premises it is a good piece of hardware to have.
If you are convinced to get a router, please let us know and
hold off on the following troubleshooting steps. Instead
after having the router connected if you need to give your
ISP the MAC address of the router, or go to a special
webpage to register it (a CSR from your ISP can tell you
that, even if they say they don't support 3rd party routers
they should still be able to relay to you the most basic of
requirements their service depends upon, instead of just
telling you to insert some CD and run it which is not what
you need to do with a new router installation except if it
were only to uninstall some software they had already had
you install). If you bought a router then after registering
it with the ISP if it didn't then work, the following listed
items would again be a method to resolve that issue.
First, check your laptop's power management application to
be sure the wired ethernet port is enabled/powered. This
assumes you are connected by ethernet not USB (you are
leaving out a lot of info).
Next take a systematic approach to seeing where the
connectivity stops... It will help a lot if you
systematically reply to each of these items, directly under
each item instead of a summary reply, to help us see where
your connectivity issue lies.
- Are you able to network with other systems can can use
the internet through the modem?
- Are there link lights between the (ethernet?) system
and/or modem and if so are they lit indicating a connection?
- If you go to a command prompt (Start Button -> Run ->
(type) "cmd", then at the command prompt type "ping
127.0.0.1", hitting enter of course, does this work?
- Next at the command prompt type "ipconfig /all"
What is the IP Address, subnet mask, default gateway, DHCP
server and DNS server numbers?
- Next at command prompt type "ping (the IP address from
above)". Does this work?
- Does your LAN depend on DHCP IP address assignment? If
you don't know the answer is likely "yes". Is the gateway
IP # in the same range as your system's IP address? Try
"ping (the default gateway's IP address)" at the command
prompt. Does this work?
- Are you familiar with accessing the modem's HTTP
interface? Typically using a web browser and accessing
something like
http://192.168.100.1 will do this. You can
use google to research what the proper IP number is for your
modem, assuming yours does have this feature. What make and
model is your modem?
- Can you access the modem's *webpage* as mentioned above?
If so, what do the various screens state about connectivity?
Consult your modem manual also if necessary, what do any
LEDs on the modem show as to the connected status?
- Did your ISP require you to register a MAC address when
you initiated service? If so, was it the MAC address of the
modem only or a system connected to it, and if a system was
it the other system that does work with the modem?
- The results of the above questions tend to make the rest
a shot in the dark, so more feedback on those may help but
at the command prompt can you get a response if you "ping
yahoo.com"? If not, next try "ping 216.109.112.135". Does
that result in a reply or not? That IP number is just one
system resolving to the yahoo.com domain name, having it
work but not yahoo.com would tend to mean a DNS server
related problem.
When the other system is connected to the modem and the
internet is working, also go to a command prompt and do
"ipconfig /all" and write down all the items asked about
above, the IP Address, subnet mask, default gateway, DHCP
server and DNS server numbers. All the values should be the
same for both systems, except the IP address should have the
last number different. For example if one were 192.168.0.4,
the other should be 192.168.0.(n). Likewise these should
both be in the same range as the gateway IP number which is
also a 192.168.0.(n) number. Likewise with the DHCP server
IP number, but the DNS IP numbers will be different, outside
of your LAN.
LAN Connection Issue 
Linear Mode
