Sharing files between XP house and W98 workshop?

T

Terry Pinnell

I have an old W98 PC in my shed/workshop. When using it I can get
access to the internet via the wireless router connected to my main XP
PC in the house. So I definitely have a network connection. I'm afraid
networks remain largely a black art to me, but on the W98 PC there's a
USB-based Netgear MA111 'Wireless USB Adapter' that my son fitted. The
network adapter card he installed on the XP Home PC is a 'Linksys
EtherFast 10/100 LAN'.

But I've been trying in vain for days to *share* files between the two
PCs. I actually did manage it once, a year or so ago, but I'm darned
if I can recover that happy state. A book I borrowed this morning from
the local library has a couple of good chapters on networking, so I
was optimistic about sorting it. But there's something fundamentally
amiss. Most of the instructions in the book revolve around the
'Network Neighborhood icon on the W98 desktop. Usually they start by
r-clicking it. But I don't have one! And searching my HD etc didn't
find one. The in-built W98 Help also relies heavily on that tool, but
nowhere can I find any suggestion as to why it might go AWOL or how to
get it back!

Any ideas would be greatly welcomed please. Or a pointer to an article
that will tell me precisely what steps are needed on both PCs to get a
shared files established between them.
 
T

Terry Pinnell

Brian A. said:
Asked/answered in win98_gen_discussion

Well, asked, yes, but no one has yet come up with a practical
solution!

Do you have any input please?
 
T

Terry Pinnell

Sorted!

I thought I'd try one other thing, despite it obviously being a waste
of time. It worked!

A key question the Network Setup wizard asks at the outset is:
"Select the statement that best describes this computer:

* This computer connects directly to the Internet. The other
computers on my network connect to the Internet through this computer.

* This computer connects to the Internet through another computer on
my network or through a residential gateway.

* Other"

I had always chosen the first, which seemed obvious beyond question.
But choosing the second did the trick! So the wireless router is a
'residential gateway' I gather. Go figure...

I have yet to check out the shed W98, and set up the file sharing, but
am now very optimistic!
 
T

Trevor L.

Terry said:
Sorted!

I thought I'd try one other thing, despite it obviously being a waste
of time. It worked!

A key question the Network Setup wizard asks at the outset is:
"Select the statement that best describes this computer:

* This computer connects directly to the Internet. The other
computers on my network connect to the Internet through this computer.

* This computer connects to the Internet through another computer on
my network or through a residential gateway.

* Other"

I had always chosen the first, which seemed obvious beyond question.
But choosing the second did the trick! So the wireless router is a
'residential gateway' I gather. Go figure...

I have yet to check out the shed W98, and set up the file sharing, but
am now very optimistic!

Hi Terry,

I didn't join the discussion, but if it makes you feel any better, I had to think about it when I connected my 2-PC network with a
router.

Yes, a router is a "residential gateway". I think the MS help on installing a network uses this phrase. Actaully the router is a
computer in its own right. It probably has more power than the first PCs released way back (when Adam was a boy), but it is a
specific purpose rather than a general purpose computer.
 
B

Brian A.

Terry Pinnell said:
Well, asked, yes, but no one has yet come up with a practical
solution!

Do you have any input please?

My understanding as to what you posted went in the same lines as those who answered
in the 98 group. It appears that the NN icon missing on the desktop was the main
issue/concern, without it being there (unless hidden) there won't be a network
because the proper components/protocols aren't installed. You have not mentioned
that you completed what was suggestions and/or elaborated any other issue and on the
matter.

I'm not trying to be an A-hole or anything of the such, but without proper
communication, proper help can not be provided. Mindreaders we are not, nor are we
sitting at your machine to see your setup.


--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 
T

Terry Pinnell

Brian A. said:
My understanding as to what you posted went in the same lines as those who answered
in the 98 group. It appears that the NN icon missing on the desktop was the main
issue/concern, without it being there (unless hidden) there won't be a network
because the proper components/protocols aren't installed. You have not mentioned
that you completed what was suggestions and/or elaborated any other issue and on the
matter.

I'm not trying to be an A-hole or anything of the such, but without proper
communication, proper help can not be provided. Mindreaders we are not, nor are we
sitting at your machine to see your setup.

OK Brian, fair points. When posting a fairly complex query I sometimes
find it hard to strike the right balance on detail level. Risk boring
the socks of most readers by spelling out every detail of what I've
done and not done? Or hope that readers will assume I've done the
basics and a fair bit of research beforehand?

Experience shows that long posts on average get fewer responses than
short ones, so I also sometimes try to split different aspects of the
same issue into separate threads. And/or different newsgroups, to
increase my chances of finding the 'right' expert.

This particular problem has evolved. So I'll probably be posting about
the current status again. So, what would *you* do, given that you want
to focus on specific aspects without repeating all the previous stuff?
A new post? Or continue in this thread?

BTW, nicely apt sig!
 
T

Terry Pinnell

Trevor L. said:
Hi Terry,

I didn't join the discussion, but if it makes you feel any better, I had to think about it when I connected my 2-PC network with a
router.

Yes, a router is a "residential gateway". I think the MS help on installing a network uses this phrase. Actaully the router is a
computer in its own right. It probably has more power than the first PCs released way back (when Adam was a boy), but it is a
specific purpose rather than a general purpose computer.

Thanks Trevor. I suppose it seems obvious now, especially as the wire
into the phone socket comes from the router, not the back of my PC!

Unfortunately this wasn't the breakthrough that I first thought though
;-(

It did temporarily let me share specified folders, from the shed W98
PC to the house XP PC. So that does show that a network was in place.
But, apparently but mystifyingly as a consequence, when I went down to
the shed I had lost its broadband connection. Far too high a price to
pay!

So I fiddled around with settings, re-installed the Net gear MA111
Wireless USB Adapter, kicked the bench a few times, etc, and somehow
eventually got the connection via my router back again. (BTW, one
complication/confusion is that the 'signal strength' shown by the
MA111 is always around 46-51%, with a 'quality' figure a bit higher.
So I'm never quite certain whether some of the negative behaviour I
see isn't caused by *that*.)

So the status right now is that the W98, TERRY-SHED, has a broadband
connection but is no longer letting me share the files on TERRY (my XP
PC) via the common workgroup name MSHOME.

On TERRY, I've lost track of which of those options was the last I
entered into the wizard. (I think I reverted to trying option #1 as
part of my attempt to see if it would get the shed connection back
again, with the usual message from the wizard that setup had failed.)
Does anyone know how can you tell? IOW, is there some easy but
definitive way of seeing
- if you have a network at all?
- if yes, what 'type' is it, in the context of those choices I listed?

As further info, if I open Network Places on TERRY, the only relevant
entry I see is 'Entire Network'. If I *did* currently have a network,
should I immediately see the name of the other PC (TERRY-SHED)?

If I open Entire Network, and then Microsoft Windows Network, after a
wait I see 'Mshome'. But when I d-click that, after a very long wait,
I get:
"Mshome is not accessible. You might not have permission to use this
network resource. Contact the administrator of this server to find out
if you have access permissions.
The list of servers for this workgroup is not currently available"

So, in summary, I'm still floundering! And any/all advice would be
very welcome please.

(BTW, Trevor, is your word-wrap setting OK? As you may be able to see
from the quoted section above, I'm seeing an odd effect here.)
 
B

Brian A.

Brian A. said:
OK Brian, fair points. When posting a fairly complex query I sometimes
find it hard to strike the right balance on detail level. Risk boring
the socks of most readers by spelling out every detail of what I've
done and not done? Or hope that readers will assume I've done the
basics and a fair bit of research beforehand?

Posting can be seen as an art, yet not rocket science. Always give thought as to
what is specifically involved in the issue and include it in the post, if something
is missing/needed you will be asked to supply it. Give it time and feel of the
proper balance specific to you will grow as time goes on.
Experience shows that long posts on average get fewer responses than
short ones, so I also sometimes try to split different aspects of the
same issue into separate threads. And/or different newsgroups, to
increase my chances of finding the 'right' expert.

True that ramblers have a higher percentage for being ignored than those of few
words. IMHO both are bad, even if the lesser gets a response, pulling teeth is no
fun either and can also be left on the roadside.
As well, those that multi-post instead of cross-posting can take a beating. The
problem with mp is those in one group do not see responses from other groups, the
responses then are redundant and a waste of time to those that can be helping others.
One thing to keep in mind is to veer from muli cross-posting, keep the posts to
specific groups without posting to mutiple specific groups. In short, don't
cross-post to (3) XP general groups and (5) 98 hardware groups and etc., I think you
get it.
This particular problem has evolved. So I'll probably be posting about
the current status again. So, what would *you* do, given that you want
to focus on specific aspects without repeating all the previous stuff?
A new post? Or continue in this thread?

Start a new thread cross-posted.
Include:
Number of machines.
OS of each.
How they're connected to your LAN/WAN. (Through a local or residential gateway)
Network components/protocols installed.
Issue. (stated before or after other included mentionings)
BTW, nicely apt sig!

~[|8o)


--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 
B

Brian A.

Right click My Network Places on the Desktop.
Click Properties.
Right click Local Area Connection.
Click Properties.

Under "This connection uses....."
Click "Client for MS Networks".
Click Properties.
Select "Windows Locator" from the dropdown box.
Click Ok.

Scroll to and select Internet Protocol (TCP/IP).
Click Properties.

Under the General tab make sure "Obtain an IP address automatically" is selected.
Click the Advanced button.

Under the DNS tab:
Selected "Append Primary and Parent DNS suffixes.
Register this connections address in DNS"

Under the WINS tab > NetBIOS:
Selected Default.
Ok out of MNP.

Reboot if required.
Open a command prompt, click Start > Run, type in: cmd and press Enter.
At the prompt type each command below and press Enter after each.
**Note: Command noted by =, Space noted by ^. Do not type the = or ^.

=ping ^ 192.168.1.1 *Routers IP, change as necessary.
If it times out then there is no communication between the router and machine.
If not then the machine communicates with the router.

=ping ^ google.com
If it times out then there is no connection to the net.
If not then net connection is established and all is well.

ping 127.0.0.1
If it fails it may be a TCP/IP stack problem.

Ping each computer from the other using the UNC:
=ping ^ computername
If it fails either way there's an IP or Name resolution problem.

If pinging times out on any address, to see if the machines IP is correct along with
other settings.
= ipconfig ^ /all
If anything isn't correct, at the prompt type and press Enter after each command (98
may be different):

=ipconfig ^ /release
=ipconfig ^ /flushdns
=ipconfig ^ /renew
=ipconfig ^ /registerdns
=exit
If that fails reopen the command prompt, run release and flushdns only and exit.

Shut down the machine.
Pull the power from the router.
Pull the power from the modem.
Wait approx 30 secs.
Apply power to the modem and wait for it to finish synchronizing with the cable.
Apply power to the router and wait for it to finish synchronizing with the modem.
Power up the machine.
The machine should now be assigned a new IP from the router.
Run ipconfig or attempt net connection to test.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 
T

Terry Pinnell

Thanks for coming back on this. Greatly appreciate your expert help.
Right click My Network Places on the Desktop.
Click Properties.
Right click Local Area Connection.
Click Properties.

Under "This connection uses....."
Click "Client for MS Networks".
Click Properties.
Select "Windows Locator" from the dropdown box.
Click Ok.

Scroll to and select Internet Protocol (TCP/IP).
Click Properties.

Under the General tab make sure "Obtain an IP address automatically" is selected.
Click the Advanced button.

Under the DNS tab:
Selected "Append Primary and Parent DNS suffixes.
Register this connections address in DNS"

Under the WINS tab > NetBIOS:
Selected Default.
Ok out of MNP.
[TCP/IP]

Thanks, already checked all those defaults. All OK.
Reboot if required.
Open a command prompt, click Start > Run, type in: cmd and press Enter.
At the prompt type each command below and press Enter after each.
**Note: Command noted by =, Space noted by ^. Do not type the = or ^.

=ping ^ 192.168.1.1 *Routers IP, change as necessary.

OK, mine is the same. (Obviously not coincidence; are they all
identical?)
If it times out then there is no communication between the router and machine.
If not then the machine communicates with the router.

OK, that gave 3 lines, all identical. Times varied each time I ran it,
but typically around 1-2ms.
=ping ^ google.com
If it times out then there is no connection to the net.
If not then net connection is established and all is well.

No problem with net connection anyway - I have an 'always on'
broadband connection. Tested OK. (And connection was working fine from
shed too, an hour ago.)
ping 127.0.0.1
If it fails it may be a TCP/IP stack problem.

Tested OK.
Ping each computer from the other using the UNC:
=ping ^ computername

ping TERRY-SHED
That failed. "Ping request could not find host TERRY-SHED."
Duh - just realised, unlike last night, when I left it running, I
switched off TERRY-SHED before coming indoors. So hardly surprising
that failed! I'll try it again tomorrow. But note that, even when shed
PC was on, I was still unable to see it in Network Places from here on
TERRY.
If it fails either way there's an IP or Name resolution problem.
If pinging times out on any address, to see if the machines IP is correct along with
other settings.
= ipconfig ^ /all

C:\Documents and Settings\Terry Pinnell>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : TERRY
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys LNE100TX Fast
Ethernet Adapter(LNE100TX v4)
Physical Address. . . . . . . . . : 00-04-5A-58-37-D9
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.33
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Thu 29 June 2006 20:56:26
Lease Expires . . . . . . . . . . : Sun 2 July 2006 20:56:26
If anything isn't correct, at the prompt type and press Enter after each command (98
may be different):

Not sure if 'anything isn't correct'! Looks OK to my untrained eyes.
So I'll stop there and hope to get your further advice please.

Status remains exactly as described in previous post. Am now getting a
rather better signal strength of 53%, after adjusting the adapter on
its flexible stem. Solid web connection on shed PC. But cannot get
access to TERRY from TERRY-SHED. Get message along lines of "\\TERRY
cannot be accessed... Check typing..."
 
B

Brian A.

=ping ^ 192.168.1.1 *Routers IP, change as necessary.
OK, mine is the same. (Obviously not coincidence; are they all
identical?)

Yes, unless changed by the user/administrator.

It appears you have set the network incorrectly because your DNS is the same as the
gateway. The DNS Servers should be the that of your ISP's servers.
Is your router set to enable DHCP? Not related to the info you provided, the DHCP
enabled in your info is for your NIC, not the router. DHCP must be enabled in the
routers setup configuration.
WINS proxy should be: Enabled = NO. Actually change this first (on both machines
if needed) and see if it resolves the issue.
Host Name . . . . . . . . . . . . : TERRY
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys LNE100TX Fast
Ethernet Adapter(LNE100TX v4)
Physical Address. . . . . . . . . : 00-04-5A-58-37-D9
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.33
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Thu 29 June 2006 20:56:26
Lease Expires . . . . . . . . . . : Sun 2 July 2006 20:56:26
</quote>

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375




Terry Pinnell said:
Thanks for coming back on this. Greatly appreciate your expert help.
Right click My Network Places on the Desktop.
Click Properties.
Right click Local Area Connection.
Click Properties.

Under "This connection uses....."
Click "Client for MS Networks".
Click Properties.
Select "Windows Locator" from the dropdown box.
Click Ok.

Scroll to and select Internet Protocol (TCP/IP).
Click Properties.

Under the General tab make sure "Obtain an IP address automatically" is selected.
Click the Advanced button.

Under the DNS tab:
Selected "Append Primary and Parent DNS suffixes.
Register this connections address in DNS"

Under the WINS tab > NetBIOS:
Selected Default.
Ok out of MNP.
[TCP/IP]

Thanks, already checked all those defaults. All OK.
Reboot if required.
Open a command prompt, click Start > Run, type in: cmd and press Enter.
At the prompt type each command below and press Enter after each.
**Note: Command noted by =, Space noted by ^. Do not type the = or ^.

=ping ^ 192.168.1.1 *Routers IP, change as necessary.

OK, mine is the same. (Obviously not coincidence; are they all
identical?)
If it times out then there is no communication between the router and machine.
If not then the machine communicates with the router.

OK, that gave 3 lines, all identical. Times varied each time I ran it,
but typically around 1-2ms.
=ping ^ google.com
If it times out then there is no connection to the net.
If not then net connection is established and all is well.

No problem with net connection anyway - I have an 'always on'
broadband connection. Tested OK. (And connection was working fine from
shed too, an hour ago.)
ping 127.0.0.1
If it fails it may be a TCP/IP stack problem.

Tested OK.
Ping each computer from the other using the UNC:
=ping ^ computername

ping TERRY-SHED
That failed. "Ping request could not find host TERRY-SHED."
Duh - just realised, unlike last night, when I left it running, I
switched off TERRY-SHED before coming indoors. So hardly surprising
that failed! I'll try it again tomorrow. But note that, even when shed
PC was on, I was still unable to see it in Network Places from here on
TERRY.
If it fails either way there's an IP or Name resolution problem.
If pinging times out on any address, to see if the machines IP is correct along
with
other settings.
= ipconfig ^ /all

C:\Documents and Settings\Terry Pinnell>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : TERRY
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys LNE100TX Fast
Ethernet Adapter(LNE100TX v4)
Physical Address. . . . . . . . . : 00-04-5A-58-37-D9
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.33
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Thu 29 June 2006 20:56:26
Lease Expires . . . . . . . . . . : Sun 2 July 2006 20:56:26
If anything isn't correct, at the prompt type and press Enter after each command
(98
may be different):

Not sure if 'anything isn't correct'! Looks OK to my untrained eyes.
So I'll stop there and hope to get your further advice please.

Status remains exactly as described in previous post. Am now getting a
rather better signal strength of 53%, after adjusting the adapter on
its flexible stem. Solid web connection on shed PC. But cannot get
access to TERRY from TERRY-SHED. Get message along lines of "\\TERRY
cannot be accessed... Check typing..."
=ipconfig ^ /release
=ipconfig ^ /flushdns
=ipconfig ^ /renew
=ipconfig ^ /registerdns
=exit
If that fails reopen the command prompt, run release and flushdns only and exit.

Shut down the machine.
Pull the power from the router.
Pull the power from the modem.
Wait approx 30 secs.
Apply power to the modem and wait for it to finish synchronizing with the cable.
Apply power to the router and wait for it to finish synchronizing with the modem.
Power up the machine.
The machine should now be assigned a new IP from the router.
Run ipconfig or attempt net connection to test.
 
T

Terry Pinnell

Brian A. said:
Yes, unless changed by the user/administrator.

It appears you have set the network incorrectly because your DNS is the same as the
gateway. The DNS Servers should be the that of your ISP's servers.
Is your router set to enable DHCP? Not related to the info you provided, the DHCP
enabled in your info is for your NIC, not the router. DHCP must be enabled in the
routers setup configuration.
WINS proxy should be: Enabled = NO. Actually change this first (on both machines
if needed) and see if it resolves the issue.

</quote>

Many thanks, appreciate your continuing help. Too hot to work on this
right now, but will get into it again soon and report back.
 
T

Terry Pinnell

OK, I'm back on the case this morning and having trouble implementing
your suggestion.
Yes, unless changed by the user/administrator.

It appears you have set the network incorrectly because your DNS is the same as the
gateway. The DNS Servers should be the that of your ISP's servers.
Is your router set to enable DHCP?

I believe so, yes.

If I open my Prestige LAN Configurator then I get this in my browser:
http://www.terrypin.dial.pipex.com/Images/LANConfigurator1.gif

Under Advanced Setup, LAN I get this:

LAN - Setup
===========
DHCP
----
DHCP Server
Client IP Pool Starting Address 192.168.1.33
Size of Client IP Pool 32
Primary DNS Server 0.0.0.0 [Puzzling?]
Secondary DNS Server 0.0.0.0 [Puzzling?]
Remote DHCP Server N/A

TCP/IP
------
IP Address 192.168.1.1
IP Subnet Mask 255.255.255.0
RIP Direction Both
RIP Version RIP-1
Multicast None


Under System Status I get:

System Status
=============
System Status
-------------
System Name : [Puzzling why it's blank? I'd have expected
TERRY?]
ZyNOS F/W Version: V3.40(GG.0) | 8/5/2002
DSL FW Version: Alcatel, Version 3.8.164
Standard: Multi-Mode


WAN Information
---------------
IP Address: 86.132.110.29
IP Subnet Mask: 255.255.255.0
Default Gateway: 86.132.110.29
VPI/VCI: 0 / 38


LAN Information
---------------
MAC Address: 00:a0:c5:33:a7:84
IP Address: 192.168.1.1
IP Subnet Mask: 255.255.255.0
DHCP: Server
DHCP Start IP: 192.168.1.33
DHCP Pool Size: 32
Not related to the info you provided, the DHCP
enabled in your info is for your NIC, not the router.

Sorry, don't really follow. NIC? Do I need to alter something? My BT
Broadband connection is working fine.
DHCP must be enabled in the routers setup configuration.

From above, does it look OK?
WINS proxy should be: Enabled = NO. Actually change this first (on both machines
if needed) and see if it resolves the issue.

That's what has me stumped! How do I do that please? I see no option
to change 'WIN proxy'.FWIW, under the WINS tab I have this:
http://www.terrypin.dial.pipex.com/Images/LAN-PC-Settings1.gif
 
B

Brian A.

Please provide your router make/model or a link to the configuration setup document
from the manufacturer.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375




Terry Pinnell said:
OK, I'm back on the case this morning and having trouble implementing
your suggestion.
Yes, unless changed by the user/administrator.

It appears you have set the network incorrectly because your DNS is the same as
the
gateway. The DNS Servers should be the that of your ISP's servers.
Is your router set to enable DHCP?

I believe so, yes.

If I open my Prestige LAN Configurator then I get this in my browser:
http://www.terrypin.dial.pipex.com/Images/LANConfigurator1.gif

Under Advanced Setup, LAN I get this:

LAN - Setup
===========
DHCP
----
DHCP Server
Client IP Pool Starting Address 192.168.1.33
Size of Client IP Pool 32
Primary DNS Server 0.0.0.0 [Puzzling?]
Secondary DNS Server 0.0.0.0 [Puzzling?]
Remote DHCP Server N/A

TCP/IP
------
IP Address 192.168.1.1
IP Subnet Mask 255.255.255.0
RIP Direction Both
RIP Version RIP-1
Multicast None


Under System Status I get:

System Status
=============
System Status
-------------
System Name : [Puzzling why it's blank? I'd have expected
TERRY?]
ZyNOS F/W Version: V3.40(GG.0) | 8/5/2002
DSL FW Version: Alcatel, Version 3.8.164
Standard: Multi-Mode


WAN Information
---------------
IP Address: 86.132.110.29
IP Subnet Mask: 255.255.255.0
Default Gateway: 86.132.110.29
VPI/VCI: 0 / 38


LAN Information
---------------
MAC Address: 00:a0:c5:33:a7:84
IP Address: 192.168.1.1
IP Subnet Mask: 255.255.255.0
DHCP: Server
DHCP Start IP: 192.168.1.33
DHCP Pool Size: 32
Not related to the info you provided, the DHCP
enabled in your info is for your NIC, not the router.

Sorry, don't really follow. NIC? Do I need to alter something? My BT
Broadband connection is working fine.
DHCP must be enabled in the routers setup configuration.

From above, does it look OK?
WINS proxy should be: Enabled = NO. Actually change this first (on both machines
if needed) and see if it resolves the issue.

That's what has me stumped! How do I do that please? I see no option
to change 'WIN proxy'.FWIW, under the WINS tab I have this:
http://www.terrypin.dial.pipex.com/Images/LAN-PC-Settings1.gif
 
T

Terry Pinnell

Brian A. said:
Please provide your router make/model or a link to the configuration setup document
from the manufacturer.

ZyXEL Prestige 650 HW. (That's on the user guide. Although confusingly
the case says 'Prestige 600 Series'.)
www.zyxel.com
 
B

Brian A.

There should be a model number printed on a plate/sticker on the router. At the
moment I can't find setup configuration info on the P-650HW, however I'm checking out
the one for P-660HW-61.
http://us.zyxel.com/web/support_dow...0050831093216,420050117110858,420050831095441

or if the line wraps/breaks: http://snipurl.com/sq4p


Double check both machines and if you find it in DNS, remove it.
If you wish you could set the DNS but it shouldn't be necessary, DNS servers for
dial.pipex.com is:
158.43.240.4
158.43.240.3

On both machines, if you're using IE open its properties.
Click the Connections tab > LAN Settings button.
Select "Automatically detect settings" and de-select "Use a proxy server for your
LAN" if selected.
Click Ok > Apply > Ok.


--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 
T

Terry Pinnell

Brian A. said:
There should be a model number printed on a plate/sticker on the router.

The model on the plate underneath is 650HW-11.

Will study rest of your email tomorrow.

Thanks for your tenacity!
 
T

Terry Pinnell

Brian A. said:
There should be a model number printed on a plate/sticker on the router. At the
moment I can't find setup configuration info on the P-650HW, however I'm checking out
the one for P-660HW-61.
http://us.zyxel.com/web/support_dow...0050831093216,420050117110858,420050831095441

or if the line wraps/breaks: http://snipurl.com/sq4p

Sorry, you've lost me there. What has to be set? What is wrong?
Double check both machines and if you find it in DNS, remove it.

Find what? I already reported all the settings...
If you wish you could set the DNS but it shouldn't be necessary, DNS servers for
dial.pipex.com
is:
158.43.240.4
158.43.240.3

Where does dial.pipex.com enter the equation? My Broadband ISP is BT.
On both machines, if you're using IE open its properties.

Default browser is Firefox. But in IE
Click the Connections tab > LAN Settings button.
Select "Automatically detect settings" and de-select "Use a proxy server for your
LAN" if selected.
Click Ok > Apply > Ok.

those are already configured correctly.
 
T

Terry Pinnell

Terry Pinnell said:
ZyXEL Prestige 650 HW. (That's on the user guide. Although confusingly
the case says 'Prestige 600 Series'.)
www.zyxel.com

If it helps, I've scanned in the relevant sections of the user guide:

====================
Page 1:
Prestige Factory Defaults

LAN IP Address 192.168.1.1 Default Password 1234

Subnet Mask 255-255-255-0 DHCF IP Pool
192.168.1.33-192.168.1.64

Internet Access Checklist

Required Telephone Company Information

l.VPI (Virtual Path ldentifier)and VC1 (Virtual Channel Identifier)
numbers.

Required ISP (Internet Service Provider) Information

1. Encapsulation type (PPP, RFC 1483, ENET, ENCAP or PPPoE).

2. You need your My Login (user name) and My Password if you are using
PPP or PPPoE encapsulation.

3. Multiplexing method: LLC-based or VC-based.

4. The IP address of the DNS (Domain Name System) server(s) and
Gateway (if provided).

5. You may need to know vour Service Name if you are using PPPoE.

Preparing Your Network

All computers must have a 10M or 100M NIC (Network Interface Card) and
TCP/IP installed.

TCP/IP should already be installed on computers using Windows
NT/2000/XR Macintosh OS 7 and later operating

systems.

These procedures are for dynamic IP addresses.

---------
Page 2:

Setting up Your Windows NT/2000/XP Computer
Configuring TCP/IP

1. Click Start, Settings, Network and Dial-up Connections and
right-click Local Area Connection or the connection you want to
configure and ciick Properties. For Windows XI" click start. Control
Panel, Network and Internet Connections and then Network Connections.
Right-click the network connection you want to configure and then dick
Properties.

2. Select Internet Protocol (TCP/IP) (under the General tab in Win XF)
and click Properties.

3. The Internet Protocol TCP/IP Properties window opens. Click Obtain
an IP address automatically.

4. Click Obtain DNS server automatically.

5. Click Advanced, IP Settings tab and remove any installed gateways,
then dick OK.

6. Click OK to save and close the Internet Protocol (TCP/IP)
Properties window.

7. Click OK to close the Local Area Connection Properties window.

8. Turn on your Prestige and restart your computer (if prompted).

Verifying TCP/IP Properties

1. Click Start, Programs, Accessories and then Command Prompt.

2. In the Command Prompt window, type "ip@ohfig" and then press ENTER.
The window displays information about
your IP address, subnet mask and default.gateway.

Setting up Your Macintosh Computer
Configuring TCP/IP Properties

1. Click the Apple menu, Control Panel and double-click TCP/IP to open
the TCP/IP Control Panel.

2. Select Ethernet from the Connect via list.

3. Select Using DHCP Server from the Configure list.

4. Close the TCP/IP Control Panel. ,,,,, ,.

5. Click Save if prompted, to save changes to your configuration.

6. Turn on your Prestige and restart your computer (if prompted).

Verifying TCP/IP Properties

Check your TCP/IP properties in the TCP/IP Control Panel.

Accessing the Prestige

1. Web configurator.

2. SMT (System Management Terminal). Access the SMT via:

• Telnet
Procedure for Web Configurator Access

1. Launch your web browser and enter "192.168.1.1" as the URL.

2. Type "admin" as the user name, "1234" (default) as the password and
press ENTER. "

3. You should now see the SITE MAP screen. Click the help icon
(located in the upper right portion of most screens for on-line help.

Procedure for SMT Access via Telnet

1. Launch a Telnet program. In Windows, click Start and then Run. ,; ,

2. Type "Telnel" followed by a space and the IP address of me
Prestige, (192.168.1.1 is the default) and click OK to display the
password screen.

3. Enter "1234", the default password, to access the SMT main menu. As
you type a password, the screen displays an "*" (asterisk) for each
character you type.

---------
Page 3:

Troubleshooting —
PROBLEM CORRECTIVE ACTION
The PWR and/or SYS LED are off. • Make sure the Prestige's power
adapter is connected to the Prestige and plugged into an appropriate
power source. Check that the Prestige and the power source are both
turned on-• Turn the Prestige off and on. If the error persists, you
may have a hardware problem. In this case, you should contact your
vendor.

The LAN LEDs donot turn on. • Make sure your computer NIC
(Network Interface Card) is working properly.

The DSL LED is off. • Check the telephone wire and connections
between the Prestige DSL port and the wall jack.

I cannot access the SMT menu. • .The password is case-sensitive,
make sure you enter it with the correct casing. • The default SMT
password is "1234". If you have changed the password and have now
forgotten it, you will need to upload the default configuration file
(see the User's Guide).

I cannot access the web configurator. • Type "admin" in the User
Name field. The default password is "1234". Both fields are
case-sensitive. • If you have changed me password and have now
forgotten it, you will need to upload the ' default configuration file
(see the User's Guide). »Make sure that there is not an SMT console
session running. • Check that you have enabled web service access in
SM^Menu 24.11 - Remote Management Control. If you have configured an
IP address .in the Secured Client IF field, your computer's IP address
must match it. For WAN access, you must configure the Server Access
field to WAN only or ALL. Otherwise, the firewall (when activated)
blocks all WAN to LAN traffic by default • Your computer's and the
Prestige's IP addresses must be.on the same subnet for LAN access, •
If you changed the Prestige's LAN IP address, then enter the new one
as the URL. • Remove any niters in menu 3.1 (LAN) or menu 11.5 (WAN)
that block web service.

I cannot ping any ' computer on the LAN. • Make sure that the
LAN LEDs are on. • Check the TCP/IP configuration on the computers.
Make sure that the IP address-and the subnet mask of the Prestige and
the computers are on the same subnet.

I cannot get a WANIP address from the ISE • The WAN IP is provided
after the ISP verifies the MAC address, host name or user ID. • Find
out the verification method used by your ISP and configure the
corresponding fields.

I cannot access the Internet. • If the DSL LED is off, check the
telephone wire and connections between the Prestige DSL port and the
wall jack. • Check that your information from the Internet Access
Checklist is entered correctly and has the right casing.

====================
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top