P
PavanGayakwad
Guest
Re: Failure to connect to ADSL Router and thence Internet
All set and done in my Dell Inspiron 1501 AMD Turion X2 64 Bit machine
(loaded with Win XP 64 bit edition) when I connect ADSL 2+ UTStarcom
Modem/Router with model numbered UT300R2U through USB, it just failed to
install driver since it is not available. When I checked modem manufacturer's
website (http://www.utstar.com/) no clue of driver download. ( this is first
worst vendor web site I saw which doesn't have driver download link for their
above device). Please let me know if you know any alternatives to fix this
problem.
Thanks in advance.
"Colin Nowell" wrote:
> Bob?
>
> What is it you mean by "I've set them up using the wizard etc and
> transferred the setup data from one to the other via a floppy." ? What data
> precisely?
>
> I hope that you are only referring to setting up your NICs since that's all
> you needed to do! Using the wizard was a bad idea too. Not needed and only
> leads to confusion mostly.
>
> You have an SMC Barricade Router. Is that one with the inbuilt ADSL modem or
> not? (I also had both at various times). As Dominic has already said, this
> has a built-in DHCP server that is totally automatic. ***All you needed to
> do in the first place was to hook one PC's ethernet port up to it and then
> wait. Whilst waiting it's useful to have the "Network Connections" folder
> open and just watch (this is assuming that your NIC card was properly
> initialised by the OS). If all is as it should be, you will see the card go
> to "enable" and at this point, if you highlight it by clicking on it, you
> will see what's going on lower left in the Network Connections window. The
> next thing you see should be "acquirring network address" with 0.0.0.0 below
> it or to the side. Eventually, when the router has sorted it, you will see a
> private address pop-up of the form 192.168.2.xxx (SMC's usually default to
> 192.168.2.1 for the default gateway and subnet) and at that point your PC
> will be connected to the router's switch at usually 100Mbps. Also, the MS
> wizard will pop-up in a tooltip from the system tray telling you it has
> found a network. Either close it (cancel) or ignore it.***
>
> At this point, you should be able to login to the router with Internet
> Explorer using http://192.168.2.1 and the admin/admin, user/password
> combination. If you can see this, you have a network connection that will
> work. Since you didn't specify what model Barricade you have, I have no clue
> whether your ADSL connection is on the end of a modem ethernet cable or
> whether it is built in to the Barricade. If it's from a ADSL modem, simply
> plug it in to the WAN socket on the Barricade, and the Barricade and modem
> will do the rest and give you an Internet connection. If it has an internal
> ADSL modem built-in, you'll have to navigate to the Router's ADSL setup page
> in order to put your account details in for your ISP so that the Router can
> login.
>
> If you've got this far, you should have the Internet on that one PC. Try
> http://www.bbc.co.uk first since it is the most reliable page on the
> internet.
>
> Now the 2nd PC. Simple, repeat from *** to *** above. Check you can access
> the internet on that one too as above. (NOTE: each PC's internet connection
> is independant of the other - I hope you didn't start dabbling with
> "Internet Connection Sharing "?)
>
> Next, local networking. I take it that both the XP32 and XP64 were left as
> setup from standard? In which case their workgroup name should be the same
> and their names unique and hopefully you know the administrator passwords of
> both right? Go to one machine (doesn't matter which) and assuming you now
> have a live network icon in your system tray of both systems, open Windows
> Explorer by RIGHT clicking on "My Computer" and choosing "Explore" (you need
> a split window with folders in the left pane). Click on the + sign to the
> left of "My Network Places" so that the folder expands and you should see
> "Entire Network". If you don't, don't click anything, just hit F5 on your
> keyboard to refresh the window (Windows Networking can be slow at times...).
> When you see it, click it's + sign to the left aswell and you should see 3
> icons expand out. Click the + to the left of "Microsoft Windows Network" and
> you should see your workgroup come up. Now click on the name itself and
> check that you can see both of your PCs in the right hand pane. Back to the
> left pane. Click the + next to the workgroup's name. Check that your 2 PCs
> expand out. Click on the OTHER machine from the one you are on. A login box
> will popup. Enter "Administrator" for the ID and the associated password for
> the other PC and hopefully that machine's drives should pop up. You did
> share them of course? (new shares - the default is no good).
>
> At this point, hopefully you will detect some kind of background activity
> going on in the explorer window, random "refreshes" etc... Go onto one of
> the other PC's drives in the right pane and drill down to a low ordered
> folder. Nip back and forth from folder to folder. Why am I getting you to do
> this? To hurry MS networking up that's why! Historically, it is very slow
> and beaurocratic during it's connection and discovery process. I've seen a
> machine take a full 10 minutes before it wakes up to the fact that "hey!
> there's another PC in my local network! doh!" Don't blame me, blame MS. I
> could bore you with a story about being on the MS beta team for WFWGv3.11 in
> another life long ago and a certain VERY useful little auxiliary mouse
> "busy" icon that represented background network activity, that got removed
> from the build. Why? "Cause it makes our networking look slow..."
>
> If you've stuck with me this far, you are either already connected or
> getting bored with my rambling so I'll shut up now
Suffice to say, (and
> others have already alluded to it) when you first connect two windows PCs on
> a local LAN it can take an absolute AGE for all to settle down and to be
> able to see each other. (in terms of simple workgroup networking as opposed
> to being on a full domain)
>
> Colin
>
>
>
All set and done in my Dell Inspiron 1501 AMD Turion X2 64 Bit machine
(loaded with Win XP 64 bit edition) when I connect ADSL 2+ UTStarcom
Modem/Router with model numbered UT300R2U through USB, it just failed to
install driver since it is not available. When I checked modem manufacturer's
website (http://www.utstar.com/) no clue of driver download. ( this is first
worst vendor web site I saw which doesn't have driver download link for their
above device). Please let me know if you know any alternatives to fix this
problem.
Thanks in advance.
"Colin Nowell" wrote:
> Bob?
>
> What is it you mean by "I've set them up using the wizard etc and
> transferred the setup data from one to the other via a floppy." ? What data
> precisely?
>
> I hope that you are only referring to setting up your NICs since that's all
> you needed to do! Using the wizard was a bad idea too. Not needed and only
> leads to confusion mostly.
>
> You have an SMC Barricade Router. Is that one with the inbuilt ADSL modem or
> not? (I also had both at various times). As Dominic has already said, this
> has a built-in DHCP server that is totally automatic. ***All you needed to
> do in the first place was to hook one PC's ethernet port up to it and then
> wait. Whilst waiting it's useful to have the "Network Connections" folder
> open and just watch (this is assuming that your NIC card was properly
> initialised by the OS). If all is as it should be, you will see the card go
> to "enable" and at this point, if you highlight it by clicking on it, you
> will see what's going on lower left in the Network Connections window. The
> next thing you see should be "acquirring network address" with 0.0.0.0 below
> it or to the side. Eventually, when the router has sorted it, you will see a
> private address pop-up of the form 192.168.2.xxx (SMC's usually default to
> 192.168.2.1 for the default gateway and subnet) and at that point your PC
> will be connected to the router's switch at usually 100Mbps. Also, the MS
> wizard will pop-up in a tooltip from the system tray telling you it has
> found a network. Either close it (cancel) or ignore it.***
>
> At this point, you should be able to login to the router with Internet
> Explorer using http://192.168.2.1 and the admin/admin, user/password
> combination. If you can see this, you have a network connection that will
> work. Since you didn't specify what model Barricade you have, I have no clue
> whether your ADSL connection is on the end of a modem ethernet cable or
> whether it is built in to the Barricade. If it's from a ADSL modem, simply
> plug it in to the WAN socket on the Barricade, and the Barricade and modem
> will do the rest and give you an Internet connection. If it has an internal
> ADSL modem built-in, you'll have to navigate to the Router's ADSL setup page
> in order to put your account details in for your ISP so that the Router can
> login.
>
> If you've got this far, you should have the Internet on that one PC. Try
> http://www.bbc.co.uk first since it is the most reliable page on the
> internet.
>
> Now the 2nd PC. Simple, repeat from *** to *** above. Check you can access
> the internet on that one too as above. (NOTE: each PC's internet connection
> is independant of the other - I hope you didn't start dabbling with
> "Internet Connection Sharing "?)
>
> Next, local networking. I take it that both the XP32 and XP64 were left as
> setup from standard? In which case their workgroup name should be the same
> and their names unique and hopefully you know the administrator passwords of
> both right? Go to one machine (doesn't matter which) and assuming you now
> have a live network icon in your system tray of both systems, open Windows
> Explorer by RIGHT clicking on "My Computer" and choosing "Explore" (you need
> a split window with folders in the left pane). Click on the + sign to the
> left of "My Network Places" so that the folder expands and you should see
> "Entire Network". If you don't, don't click anything, just hit F5 on your
> keyboard to refresh the window (Windows Networking can be slow at times...).
> When you see it, click it's + sign to the left aswell and you should see 3
> icons expand out. Click the + to the left of "Microsoft Windows Network" and
> you should see your workgroup come up. Now click on the name itself and
> check that you can see both of your PCs in the right hand pane. Back to the
> left pane. Click the + next to the workgroup's name. Check that your 2 PCs
> expand out. Click on the OTHER machine from the one you are on. A login box
> will popup. Enter "Administrator" for the ID and the associated password for
> the other PC and hopefully that machine's drives should pop up. You did
> share them of course? (new shares - the default is no good).
>
> At this point, hopefully you will detect some kind of background activity
> going on in the explorer window, random "refreshes" etc... Go onto one of
> the other PC's drives in the right pane and drill down to a low ordered
> folder. Nip back and forth from folder to folder. Why am I getting you to do
> this? To hurry MS networking up that's why! Historically, it is very slow
> and beaurocratic during it's connection and discovery process. I've seen a
> machine take a full 10 minutes before it wakes up to the fact that "hey!
> there's another PC in my local network! doh!" Don't blame me, blame MS. I
> could bore you with a story about being on the MS beta team for WFWGv3.11 in
> another life long ago and a certain VERY useful little auxiliary mouse
> "busy" icon that represented background network activity, that got removed
> from the build. Why? "Cause it makes our networking look slow..."
>
> If you've stuck with me this far, you are either already connected or
> getting bored with my rambling so I'll shut up now
Suffice to say, (and > others have already alluded to it) when you first connect two windows PCs on
> a local LAN it can take an absolute AGE for all to settle down and to be
> able to see each other. (in terms of simple workgroup networking as opposed
> to being on a full domain)
>
> Colin
>
>
>
