Help! Lost my internal network after installing Wireless ADSL modem/router.hub.WiFi

[Alan F Cross]

Before:
Two PCs (XP Home and Win98) connected with Netgear mini-hub. All file
and drive sharing OK. Using Alcatel ADSL USB modem for broadband on XP
PC only.

Change:
Switched to D-Link DSL-G604T ADSL modem/router.hub.WiFi, to connect new
laptop.

All devices talk to the broadband connection, but I can't re-establish
the internal network. Re-installed my Netgear hub, and it's still not
there. Reinstalled my D-Link WiFi box.

When I try to get Windows to recognise the network, it says it doesn't
recommend that way of networking (security ... huh, they should talk!),
so seems to refuse to establish what I require. The D-Link has a
firewall, so, suitably set up, should be as OK as any other connection.

Anyone else had this, and know what to do about it?

TIA.

 

[Chuck]

Before:
Two PCs (XP Home and Win98) connected with Netgear mini-hub. All file
and drive sharing OK. Using Alcatel ADSL USB modem for broadband on XP
PC only.

Change:
Switched to D-Link DSL-G604T ADSL modem/router.hub.WiFi, to connect new
laptop.

All devices talk to the broadband connection, but I can't re-establish
the internal network. Re-installed my Netgear hub, and it's still not
there. Reinstalled my D-Link WiFi box.

When I try to get Windows to recognise the network, it says it doesn't
recommend that way of networking (security ... huh, they should talk!),
so seems to refuse to establish what I require. The D-Link has a
firewall, so, suitably set up, should be as OK as any other connection.

Anyone else had this, and know what to do about it?

TIA.

Alan,

Let's start from the beginning, first let's see what network configurations your
computers have when connected to the router.

Please provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.
Identify operating system (by name and version) with each ipconfig listing.

Now let's see if they have connectivity with each other.

From each computer, test connectivity and name resolution:
1) Ping itself by name.
2) Ping itself by ip address.
3) Ping the other by name.
4) Ping the other by ip address.
Report success / exact error displayed in each test (8 tests total).

Once we know the basics, we can see what to do next.

And Alan, please don't contribute to the spread and success of email address
mining viruses. Learn to munge your email address properly, to keep yourself a
bit safer when posting to open forums. Protect yourself and the rest of the
internet - read this article.
http://www.mailmsg.com/SPAM_munging.htm

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Hans-Georg Michna]

When I try to get Windows to recognise the network, it says it doesn't
recommend that way of networking (security ... huh, they should talk!),
so seems to refuse to establish what I require.

Alan,

did you use the Networking Wizard? Which choices did you enter
there?

Hans-Georg

 

[Alan F Cross]

Hi Chuck,

Thanks very much for picking up on this. And thanks for your point about
munging when communicating with newsgroups - a valid point.

Here's the config info
==============================
Windows IP Configuration Machine A
(win XP Home 5.1 SP1)

Host Name . . . . . . . . . . . . : proaxis-a
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
Physical Address. . . . . . . . . : 00-E0-18-D8-8C-DA
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
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. . . . . . . . . . : 07 October 2004 19:22:30
Lease Expires . . . . . . . . . . : 07 October 2004 20:22:30

======================================
Windows 98 IP Configuration - Machine B

Host Name . . . . . . . . . : PROAXIS-B
DNS Servers . . . . . . . . : 192.168.1.1
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

0 Ethernet adapter :

Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-00
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

1 Ethernet adapter :

Description . . . . . . . . : NETGEAR FA33X PCI Adapter
Physical Address. . . . . . : 00-40-F4-1A-1C-C6
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.1.4
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 10 06 04 19:38:07
Lease Expires . . . . . . . : 10 06 04 20:38:07


I have done the ping tests. Incidentally my router sees all DHCP
assigned names and addresses when asked (from either machine).


The ping tests

A can't ping itself by number (Request timed out)
A can't ping itself by name (Request timed out)

A can't ping B by name (Can't find host)
A can ping B by number

B can ping itself by name
B can ping itself by number

B can't ping A by name (unknown host)
B can't ping A by number (Request timed out)

When I attach the WiFi laptop, it can ping machine B (Win98), and see
its drives, and B can see the shared docs on the laptop (no drives yet
set as shared).

Work group names:
A - MSHOME - won't let me change it in the wizard
B - Heathfield
Laptop - MSHOME - factory default not yet changed

When I run the Network Setup Wizard on A, after it asks my connection
configuration to the network and the Internet which I confirm (Internet
via a hub), it tells me this connection is not recommended, and that it
is going to enable ICF. When I then set a work-group name (different
from MSHOME) it accepts it, then tries a connection and says "Cannot
complete the Network Setup Wizard An error occurred ...Go do it manually
or change settings" Very obtuse! When I run the Wizard again, it has
dropped back to the default work-group name of MSHOME.

I hope this is enough information to get your teeth into, and I thank
you for any time you can give it. I know it's a pretty basic
configuration, and can't believe I'm having such trouble.

Hope you get the chance to look at this and give me a bit of your
wisdom! Thanks again.

Best regards

 

[Alan F Cross]

Alan,

did you use the Networking Wizard? Which choices did you enter
there?

Hans-Georg

First connectivity choices - I chose 'other'
Second connectivity choices - I chose first option ("This computer
connects to the Internet directly or through a network hub ... ")

Windows then tells me it doesn't recommend this, and enables ICF (OK,
nothing lost). But after asking me about host names and work-group name,
it then fails to make a connection ("Cannot complete the Network Setup
Wizard, An error occurred..."). It then forgets my work-group name.

See my newsgroup response to Chuck for a full report on settings.

TIA

 

[Chuck]

Hi Chuck,

Thanks very much for picking up on this. And thanks for your point about
munging when communicating with newsgroups - a valid point.

Here's the config info
==============================
Windows IP Configuration Machine A
(win XP Home 5.1 SP1)

Host Name . . . . . . . . . . . . : proaxis-a
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
Physical Address. . . . . . . . . : 00-E0-18-D8-8C-DA
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
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. . . . . . . . . . : 07 October 2004 19:22:30
Lease Expires . . . . . . . . . . : 07 October 2004 20:22:30

======================================
Windows 98 IP Configuration - Machine B

Host Name . . . . . . . . . : PROAXIS-B
DNS Servers . . . . . . . . : 192.168.1.1
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

0 Ethernet adapter :

Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-00
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

1 Ethernet adapter :

Description . . . . . . . . : NETGEAR FA33X PCI Adapter
Physical Address. . . . . . : 00-40-F4-1A-1C-C6
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.1.4
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 10 06 04 19:38:07
Lease Expires . . . . . . . : 10 06 04 20:38:07


I have done the ping tests. Incidentally my router sees all DHCP
assigned names and addresses when asked (from either machine).


The ping tests

A can't ping itself by number (Request timed out)
A can't ping itself by name (Request timed out)

A can't ping B by name (Can't find host)
A can ping B by number

B can ping itself by name
B can ping itself by number

B can't ping A by name (unknown host)
B can't ping A by number (Request timed out)

When I attach the WiFi laptop, it can ping machine B (Win98), and see
its drives, and B can see the shared docs on the laptop (no drives yet
set as shared).

Work group names:
A - MSHOME - won't let me change it in the wizard
B - Heathfield
Laptop - MSHOME - factory default not yet changed

When I run the Network Setup Wizard on A, after it asks my connection
configuration to the network and the Internet which I confirm (Internet
via a hub), it tells me this connection is not recommended, and that it
is going to enable ICF. When I then set a work-group name (different
from MSHOME) it accepts it, then tries a connection and says "Cannot
complete the Network Setup Wizard An error occurred ...Go do it manually
or change settings" Very obtuse! When I run the Wizard again, it has
dropped back to the default work-group name of MSHOME.

I hope this is enough information to get your teeth into, and I thank
you for any time you can give it. I know it's a pretty basic
configuration, and can't believe I'm having such trouble.

Hope you get the chance to look at this and give me a bit of your
wisdom! Thanks again.

Best regards

Alan,

Start by rerunning the wizard on A, and say that it connects thru another
computer - the router acts as another computer. That should avoid involving
ICF.

Try changing the workgroup name from My Computer - Properties - Computer Name
tab.

Try the pings again.

If that doesn't help, let's look at the static route tables.
Start - Run - "cmd". Type "route print >c:\route.txt" into the command window -
Open c:\route.txt in Notepad, copy and paste into your next post. Identify
operating system (by name and version) with each ipconfig listing.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Alan F Cross]

Hi Chuck,

Did as you suggested with specifying 'via another computer'. Local
Network on Network Connections is now showing under the heading Network
Bridge (MAC Bridge Miniport), and my A machine now shows up twice
(192.168.1.2 and 1.5) to the router. But at least the Wizard completed
without complaint. Pings fail in exactly the same way.

Here is the route for the A machine XP Home 5.1 SP1 (192.168.1.2 and
1.5) after the above changes.
=========================================================================
==
Interface List
0x1 ........................... MS TCP Loopback interface
0x10004 ...62 d9 48 09 83 fc ...... MAC Bridge Miniport - Packet
Scheduler Miniport
=========================================================================
==
=========================================================================
==
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.5
10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.5 192.168.1.5
10
192.168.1.5 255.255.255.255 127.0.0.1 127.0.0.1
10
192.168.1.255 255.255.255.255 192.168.1.5 192.168.1.5
10
224.0.0.0 240.0.0.0 192.168.1.5 192.168.1.5
10
255.255.255.255 255.255.255.255 192.168.1.5 192.168.1.5
1
Default Gateway: 192.168.1.1
=========================================================================
==
Persistent Routes:
None
==================================================================

And for the B machine Win98 (192.168.1.4)
Active Routes:

Network Address Netmask Gateway Address Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.4
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4
1
192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4
1
224.0.0.0 224.0.0.0 192.168.1.4 192.168.1.4
1
255.255.255.255 255.255.255.255 192.168.1.4 0.0.0.0
1

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

So no change yet, but I have hope for progress!

 

[Chuck]

Hi Chuck,

Did as you suggested with specifying 'via another computer'. Local
Network on Network Connections is now showing under the heading Network
Bridge (MAC Bridge Miniport), and my A machine now shows up twice
(192.168.1.2 and 1.5) to the router. But at least the Wizard completed
without complaint. Pings fail in exactly the same way.

Here is the route for the A machine XP Home 5.1 SP1 (192.168.1.2 and
1.5) after the above changes.
=========================================================================
==
Interface List
0x1 ........................... MS TCP Loopback interface
0x10004 ...62 d9 48 09 83 fc ...... MAC Bridge Miniport - Packet
Scheduler Miniport
=========================================================================
==
=========================================================================
==
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.5
10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.5 192.168.1.5
10
192.168.1.5 255.255.255.255 127.0.0.1 127.0.0.1
10
192.168.1.255 255.255.255.255 192.168.1.5 192.168.1.5
10
224.0.0.0 240.0.0.0 192.168.1.5 192.168.1.5
10
255.255.255.255 255.255.255.255 192.168.1.5 192.168.1.5
1
Default Gateway: 192.168.1.1
=========================================================================
==
Persistent Routes:
None
==================================================================

And for the B machine Win98 (192.168.1.4)
Active Routes:

Network Address Netmask Gateway Address Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.4
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4
1
192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4
1
224.0.0.0 224.0.0.0 192.168.1.4 192.168.1.4
1
255.255.255.255 255.255.255.255 192.168.1.4 0.0.0.0
1

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

So no change yet, but I have hope for progress!

Alan,

Get rid of the bridge. Rerun ipconfig and route, and post both after deleting
the bridge.

What network devices are on A? The original ipconfig showed just a Broadcom GB.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Chuck]

Hi Chuck,

Did as you suggested with specifying 'via another computer'. Local
Network on Network Connections is now showing under the heading Network
Bridge (MAC Bridge Miniport), and my A machine now shows up twice
(192.168.1.2 and 1.5) to the router. But at least the Wizard completed
without complaint. Pings fail in exactly the same way.

Here is the route for the A machine XP Home 5.1 SP1 (192.168.1.2 and
1.5) after the above changes.
=========================================================================
==
Interface List
0x1 ........................... MS TCP Loopback interface
0x10004 ...62 d9 48 09 83 fc ...... MAC Bridge Miniport - Packet
Scheduler Miniport
=========================================================================
==
=========================================================================
==
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.5
10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.5 192.168.1.5
10
192.168.1.5 255.255.255.255 127.0.0.1 127.0.0.1
10
192.168.1.255 255.255.255.255 192.168.1.5 192.168.1.5
10
224.0.0.0 240.0.0.0 192.168.1.5 192.168.1.5
10
255.255.255.255 255.255.255.255 192.168.1.5 192.168.1.5
1
Default Gateway: 192.168.1.1
=========================================================================
==
Persistent Routes:
None
==================================================================

And for the B machine Win98 (192.168.1.4)
Active Routes:

Network Address Netmask Gateway Address Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.4
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4
1
192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4
1
224.0.0.0 224.0.0.0 192.168.1.4 192.168.1.4
1
255.255.255.255 255.255.255.255 192.168.1.4 0.0.0.0
1

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

So no change yet, but I have hope for progress!

Alan,

Get rid of the bridge. Settings - Network Connections - right click on the
bridge, select delete.

Rerun ipconfig and route, and post both after deleting the bridge.

What network devices are on A? The original ipconfig showed just a Broadcom GB.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Alan F Cross]

Chuck

Follow-up to my last posting:

Trying a few more things. I've removed the bridge network that was
created by 'lying' to Windows, and gone through the same process as
before to set up a home network with the Wizard. No change, but I now
notice the following as being the settings the Wizard intends to apply
to create the network:

XP Home 5.1 SP1
=============================================

Internet connection settings:

Internet connection: Local Area Connection
Internet Connection Firewall: enabled
____________________________________________________
Network settings:

Computer description: Primary
Computer name: PROAXIS-A
Workgroup name: HEATHFIELD

The Shared Documents folder and any printers connected to this computer
have been shared.
___________________________________________________
Connection to your network: 1394 Connection

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

Note the 1394 (Firewire) connection! Now, on an earlier panel it said
that it was choosing Local Area Connection (Broadcom NetXtreme Gigabit
Ethernet) rather than 1394, but then goes to set the Firewire
connection! No wonder it won't talk. But is it using this because Local
Area Connection is failing?

So, still stumped, but getting wiser!

 

[Alan F Cross]

Chuck,

Further follow-up..

Just checked the connection properties for 1394 Firewire, and it has
(all checked):

Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks
Internet protocol (TCP/IP)

That doesn't sound right to me, but perhaps its a Windows quirk. Don't
want to interfere with it in case I lose my Firewire scanner! But I have
to stop Windows saying it's choosing Ethernet and then picking Firewire!

Off to bed now (I'm in the UK) so will pick up again in the morning.
Thanks again for all your help.

 

[Alan F Cross]

I think I've (nearly) got it!

Old setup was Internet via USB and firewall, so old internal network was
not passing through the firewall. New setup has the Internet and the
internal network both on Ethernet, and thus both firewalled (as
presently set).

Switch off the firewall and everything sees everything!

Just got to work out how to protect the A machine with the firewall on
the broadband connection, without nobbling the internal network. Any
clues?

Supplementary question ... with a hardware firewall in the ADSL
modem/router, is there any need to look at IPX/SPX for my internal file
and print sharing, or does the hardware firewall make this unnecessary?

 

[Hans-Georg Michna]

In message <[email protected]>, Hans-Georg

First connectivity choices - I chose 'other'
Second connectivity choices - I chose first option ("This computer
connects to the Internet directly or through a network hub ... ")

Windows then tells me it doesn't recommend this, and enables ICF (OK,
nothing lost). But after asking me about host names and work-group name,
it then fails to make a connection ("Cannot complete the Network Setup
Wizard, An error occurred...").

Alan,

what error?

Anyway, it can be set up manually without using the wizard, so
if you don't want to follow up on that wizard error, just ignore
this message.

Hans-Georg

 

[Alan F Cross]

Chuck, Hans-Georg,

Well, I'm there!

When my Setup Wizard highlighted Local Area Connection, but then it
proceeded to deploy 1394, I thought I'd be perverse and override its
choice by highlighting 1394. Sure enough, it then proceeded to deploy
Local Area Connection. Crazy or what!?

Then I discovered that the Norton firewall was getting in the way. So I
set the rules to permit printer and file sharing, but that was not
enough. I then had to go into Norton's 'home Networking' panel and add
my 192.168 .... range to the list of trusted networks.

All now working, and I hope all is secure (reasonably!). Many thanks for
all the clues and assistance along the way.

One lesson seems to be ... if something doesn't work, switch off the
firewall. If it then works, go chasing firewall settings till it works
with the firewall on.

Grateful for all your input on this.

 

[Chuck]

Chuck, Hans-Georg,

Well, I'm there!

When my Setup Wizard highlighted Local Area Connection, but then it
proceeded to deploy 1394, I thought I'd be perverse and override its
choice by highlighting 1394. Sure enough, it then proceeded to deploy
Local Area Connection. Crazy or what!?

Then I discovered that the Norton firewall was getting in the way. So I
set the rules to permit printer and file sharing, but that was not
enough. I then had to go into Norton's 'home Networking' panel and add
my 192.168 .... range to the list of trusted networks.

All now working, and I hope all is secure (reasonably!). Many thanks for
all the clues and assistance along the way.

One lesson seems to be ... if something doesn't work, switch off the
firewall. If it then works, go chasing firewall settings till it works
with the firewall on.

Grateful for all your input on this.

Alan,

So your problem had a multitude of causes.

The Network Setup Wizard makes a lot of assumptions that complicate things.
Sometimes it would have been simpler to just have done things manually.

Then firewall configuration on top of that.

Anyway, just to answer a previous question. IPX/SPX is not necessary, and will
only complicate your LAN. NetBIOS Over TCP/IP, on top of the native TCP/IP, is
all that's necessary for most Windows networks.

So congrats for getting thru all your problems, and thanks for updating us.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.