Networking two PCs

[Dan]

Hello,

I am trying to connect two PCs with firewire. There has been many posting
that I have read that have not resolved my issue.

I have two PCs (one with XP Home and the other with Pro) that I have
connected with a firewire cable. Both PCs recognize the connection but are
unable to see the other PCs information. I want to be able to transfer large
files on multiple occassions. Files and Setting Transfer Wizard will not work
- does not recognize the firewire port, only USB, COM ports or Infrared.

I am unable to ping each computer from the other using the IP address. On
the XP Pro computer, Simple File Sharing is enabled. The Guest account is
enabled, on each computer. On XP Pro, for the Local Security Policy, under
"Deny access to this computer from the network", Guest is not in the list.

Here is the information from ipconfig from both machines.

Windows IP Configuration
Host Name . . . . . . . . . . . . : Main-Computer
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Home Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-01-80-4D-B4-8C
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. . . . . . . . . . : October 26, 2004 8:51:42 PM
Lease Expires . . . . . . . . . . : November 2, 2004 8:51:42 PM
PPP adapter {94067D11-68A4-4C3C-BA8D-E6F672413B6A}:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.140.152.235
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 172.140.152.235
DNS Servers . . . . . . . . . . . : 205.188.146.146
NetBIOS over Tcpip. . . . . . . . : Disabled
Other adapter 1394 Connection:
Connection-specific DNS Suffix . : sympatico.ca
Description . . . . . . . . . . . : 1394 Net Adapter
Physical Address. . . . . . . . . : 22-84-69-EB-FD-9E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.66.187
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Windows IP Configuration
Host Name . . . . . . . . . . . . : LAPTOP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG
Network Connection
Physical Address. . . . . . . . . : 00-0E-35-39-7F-D2
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.3
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. . . . . . . . . . : October 26, 2004 9:00:44 PM
Lease Expires . . . . . . . . . . : November 2, 2004 9:00:44 PM
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8139 C+ Fast Ethernet
NIC
Physical Address. . . . . . . . . : 00-0F-B0-04-70-1D
Other adapter 1394 Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 1394 Net Adapter
Physical Address. . . . . . . . . : 22-AA-6F-22-95-66
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.215.152
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Both machines connect to the internet through a Comtrend ADSL wired/wireless
router. Main-Computer is wired and laptop is wireless (don't use the wired
connection). Main also has a dial-up connection.

The internet service is working on both Main and Laptop. If I connect Laptop
by Ethernet cable to the router, I still can not ping Main to Laptop, or
Laptop to Main (by address).

Help is greatly appreciated.

Dan

[Chuck]

On Sun, 31 Oct 2004 14:56:01 -0800, Dan > wrote:

>Hello,
>
>I am trying to connect two PCs with firewire. There has been many posting
>that I have read that have not resolved my issue.
>
>I have two PCs (one with XP Home and the other with Pro) that I have
>connected with a firewire cable. Both PCs recognize the connection but are
>unable to see the other PCs information. I want to be able to transfer large
>files on multiple occassions. Files and Setting Transfer Wizard will not work
>- does not recognize the firewire port, only USB, COM ports or Infrared.
>
>I am unable to ping each computer from the other using the IP address. On
>the XP Pro computer, Simple File Sharing is enabled. The Guest account is
>enabled, on each computer. On XP Pro, for the Local Security Policy, under
>"Deny access to this computer from the network", Guest is not in the list.
>
>Here is the information from ipconfig from both machines.

<SNIP>

>Both machines connect to the internet through a Comtrend ADSL wired/wireless
>router. Main-Computer is wired and laptop is wireless (don't use the wired
>connection). Main also has a dial-up connection.
>
>The internet service is working on both Main and Laptop. If I connect Laptop
>by Ethernet cable to the router, I still can not ping Main to Laptop, or
>Laptop to Main (by address).
>
>Help is greatly appreciated.
>
>Dan

Dan,

Are there any firewalls, Microsoft or third party, on either computer?

If that's no help, let's look at the static route for each computer.
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.

When you ping, just to clarify things, what addresses are you using?

What SP on each computer?

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

[Dan]

"Chuck" wrote:

> On Sun, 31 Oct 2004 14:56:01 -0800, Dan > wrote:
>
> >Hello,
> >
> >I am trying to connect two PCs with firewire. There has been many posting
> >that I have read that have not resolved my issue.
> >
> >I have two PCs (one with XP Home and the other with Pro) that I have
> >connected with a firewire cable. Both PCs recognize the connection but are
> >unable to see the other PCs information. I want to be able to transfer large
> >files on multiple occassions. Files and Setting Transfer Wizard will not work
> >- does not recognize the firewire port, only USB, COM ports or Infrared.
> >
> >I am unable to ping each computer from the other using the IP address. On
> >the XP Pro computer, Simple File Sharing is enabled. The Guest account is
> >enabled, on each computer. On XP Pro, for the Local Security Policy, under
> >"Deny access to this computer from the network", Guest is not in the list.
> >
> >Here is the information from ipconfig from both machines.
>
> <SNIP>
>
> >Both machines connect to the internet through a Comtrend ADSL wired/wireless
> >router. Main-Computer is wired and laptop is wireless (don't use the wired
> >connection). Main also has a dial-up connection.
> >
> >The internet service is working on both Main and Laptop. If I connect Laptop
> >by Ethernet cable to the router, I still can not ping Main to Laptop, or
> >Laptop to Main (by address).
> >
> >Help is greatly appreciated.
> >
> >Dan
>
> Dan,
>
> Are there any firewalls, Microsoft or third party, on either computer?
>
> If that's no help, let's look at the static route for each computer.
> 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.
>
> When you ping, just to clarify things, what addresses are you using?
>
> What SP on each computer?
>
> Cheers,
> Chuck
> Paranoia comes from experience - and is not necessarily a bad thing.
>

Chuck,

For unknown reasons, everything is now working. I am able to ping the other
PC using the IP address and the name of the machine. I can also see the
opposite PC's files in SharedDocs folder.

Is there a way to still have this access with a firewall software enabled?
So there is no need to toggle between them when connecting to the internet
and the opposite PC?

Hopefully the Home Network Setup will now work.

Thanks for all the help.

[Chuck]

On Sun, 31 Oct 2004 15:49:02 -0800, Dan > wrote:

>"Chuck" wrote:
>
>> On Sun, 31 Oct 2004 14:56:01 -0800, Dan > wrote:
>>
>> >Hello,
>> >
>> >I am trying to connect two PCs with firewire. There has been many posting
>> >that I have read that have not resolved my issue.
>> >
>> >I have two PCs (one with XP Home and the other with Pro) that I have
>> >connected with a firewire cable. Both PCs recognize the connection but are
>> >unable to see the other PCs information. I want to be able to transfer large
>> >files on multiple occassions. Files and Setting Transfer Wizard will not work
>> >- does not recognize the firewire port, only USB, COM ports or Infrared.
>> >
>> >I am unable to ping each computer from the other using the IP address. On
>> >the XP Pro computer, Simple File Sharing is enabled. The Guest account is
>> >enabled, on each computer. On XP Pro, for the Local Security Policy, under
>> >"Deny access to this computer from the network", Guest is not in the list.
>> >
>> >Here is the information from ipconfig from both machines.
>>
>> <SNIP>
>>
>> >Both machines connect to the internet through a Comtrend ADSL wired/wireless
>> >router. Main-Computer is wired and laptop is wireless (don't use the wired
>> >connection). Main also has a dial-up connection.
>> >
>> >The internet service is working on both Main and Laptop. If I connect Laptop
>> >by Ethernet cable to the router, I still can not ping Main to Laptop, or
>> >Laptop to Main (by address).
>> >
>> >Help is greatly appreciated.
>> >
>> >Dan
>>
>> Dan,
>>
>> Are there any firewalls, Microsoft or third party, on either computer?
>>
>> If that's no help, let's look at the static route for each computer.
>> 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.
>>
>> When you ping, just to clarify things, what addresses are you using?
>>
>> What SP on each computer?
>>
>> Cheers,
>> Chuck
>> Paranoia comes from experience - and is not necessarily a bad thing.
>>
>
>Chuck,
>
>For unknown reasons, everything is now working. I am able to ping the other
>PC using the IP address and the name of the machine. I can also see the
>opposite PC's files in SharedDocs folder.
>
>Is there a way to still have this access with a firewall software enabled?
>So there is no need to toggle between them when connecting to the internet
>and the opposite PC?
>
>Hopefully the Home Network Setup will now work.
>
>Thanks for all the help.

Dan,

Weird. But that's computers for you. Chaotic systems many times.

Don't bother with the wizard - if you have things working now, make any
additional adjustments manually - and know what you're changing. Using the
wizard can have side effects.

You have a wireless LAN, so you absolutely should be using a firewall, and all
other possible protection. Don't make it easy for an unknown wireless neighbor
to exploit your open WLAN.

Change the router management password, and disable remote (WAN) management.

Enable WEP / WPA. Use non-trivial (non-guessable) values for each. (No "My dog
has fleas").

Enable MAC filtering.

Change the subnet of your LAN - don't use the default.

Disable DHCP, and assign an address to each computer manually.

Which firewall are you running? Any personal firewall absolutely has to have
some ability to open access for specified applications - and file sharing is one
very necessary application.

If it's Windows Firewall (XP SP2 native firewall), for instance, you enable the
File and Printer Sharing exception, and set scope to the individual (fixed) ip
addresses used by the interfaces on the other computer.

Don't disable SSID broadcast - some configurations require the SSID broadcast.
But change the SSID itself - to something that doesn't identify you, or the
equipment.

Enable the router activity log. Examine it regularly. Know what each
connection listed represents - you? a neighbor?.

Anyway, congrats on getting file sharing working. Now get your firewall
adjusted, then we can work out the Firewire issues.

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

[Dan]

"Chuck" wrote:

> On Sun, 31 Oct 2004 15:49:02 -0800, Dan > wrote:
>
> >"Chuck" wrote:
> >
> >> On Sun, 31 Oct 2004 14:56:01 -0800, Dan > wrote:
> >>
> >> >Hello,
> >> >
> >> >I am trying to connect two PCs with firewire. There has been many posting
> >> >that I have read that have not resolved my issue.
> >> >
> >> >I have two PCs (one with XP Home and the other with Pro) that I have
> >> >connected with a firewire cable. Both PCs recognize the connection but are
> >> >unable to see the other PCs information. I want to be able to transfer large
> >> >files on multiple occassions. Files and Setting Transfer Wizard will not work
> >> >- does not recognize the firewire port, only USB, COM ports or Infrared.
> >> >
> >> >I am unable to ping each computer from the other using the IP address. On
> >> >the XP Pro computer, Simple File Sharing is enabled. The Guest account is
> >> >enabled, on each computer. On XP Pro, for the Local Security Policy, under
> >> >"Deny access to this computer from the network", Guest is not in the list.
> >> >
> >> >Here is the information from ipconfig from both machines.
> >>
> >> <SNIP>
> >>
> >> >Both machines connect to the internet through a Comtrend ADSL wired/wireless
> >> >router. Main-Computer is wired and laptop is wireless (don't use the wired
> >> >connection). Main also has a dial-up connection.
> >> >
> >> >The internet service is working on both Main and Laptop. If I connect Laptop
> >> >by Ethernet cable to the router, I still can not ping Main to Laptop, or
> >> >Laptop to Main (by address).
> >> >
> >> >Help is greatly appreciated.
> >> >
> >> >Dan
> >>
> >> Dan,
> >>
> >> Are there any firewalls, Microsoft or third party, on either computer?
> >>
> >> If that's no help, let's look at the static route for each computer.
> >> 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.
> >>
> >> When you ping, just to clarify things, what addresses are you using?
> >>
> >> What SP on each computer?
> >>
> >> Cheers,
> >> Chuck
> >> Paranoia comes from experience - and is not necessarily a bad thing.
> >>
> >
> >Chuck,
> >
> >For unknown reasons, everything is now working. I am able to ping the other
> >PC using the IP address and the name of the machine. I can also see the
> >opposite PC's files in SharedDocs folder.
> >
> >Is there a way to still have this access with a firewall software enabled?
> >So there is no need to toggle between them when connecting to the internet
> >and the opposite PC?
> >
> >Hopefully the Home Network Setup will now work.
> >
> >Thanks for all the help.
>
> Dan,
>
> Weird. But that's computers for you. Chaotic systems many times.
>
> Don't bother with the wizard - if you have things working now, make any
> additional adjustments manually - and know what you're changing. Using the
> wizard can have side effects.
>
> You have a wireless LAN, so you absolutely should be using a firewall, and all
> other possible protection. Don't make it easy for an unknown wireless neighbor
> to exploit your open WLAN.
>
> Change the router management password, and disable remote (WAN) management.
>
> Enable WEP / WPA. Use non-trivial (non-guessable) values for each. (No "My dog
> has fleas").
>
> Enable MAC filtering.
>
> Change the subnet of your LAN - don't use the default.
>
> Disable DHCP, and assign an address to each computer manually.
>
> Which firewall are you running? Any personal firewall absolutely has to have
> some ability to open access for specified applications - and file sharing is one
> very necessary application.
>
> If it's Windows Firewall (XP SP2 native firewall), for instance, you enable the
> File and Printer Sharing exception, and set scope to the individual (fixed) ip
> addresses used by the interfaces on the other computer.
>
> Don't disable SSID broadcast - some configurations require the SSID broadcast.
> But change the SSID itself - to something that doesn't identify you, or the
> equipment.
>
> Enable the router activity log. Examine it regularly. Know what each
> connection listed represents - you? a neighbor?.
>
> Anyway, congrats on getting file sharing working. Now get your firewall
> adjusted, then we can work out the Firewire issues.
>
> Cheers,
> Chuck
> Paranoia comes from experience - and is not necessarily a bad thing.
>
Chuck,

Thanks for the information. I will work on the wireless LAN setup.
Presently I have NIS and Windows Firewall enabled. I will try to alter these
programs to let the 1394 connection to work.

Is there some documentation I can follow in setting up the procedures you
discussed:
- disable remote (WAN) management
- Enable WEP / WPA
- Enable MAC filtering
- Change the subnet of your LAN
- Disable DHCP, and assign an address to each computer manually.
- Changing SSID
- Enable the router activity log

The last time I tried some of the above options, I was unable to access the
internet from any of the PCs.

As for the firewire issue, that also is now working. When I was able to
"ping" each machine, now the firewire connection works and I can transfer
files between each PC.

Your help has been greatly appreciated.

Thanks

[Chuck]

On Sun, 31 Oct 2004 17:52:42 -0800, Dan > wrote:

>"Chuck" wrote:

<SNIP>

>> Change the router management password, and disable remote (WAN) management.
>>
>> Enable WEP / WPA. Use non-trivial (non-guessable) values for each. (No "My dog
>> has fleas").
>>
>> Enable MAC filtering.
>>
>> Change the subnet of your LAN - don't use the default.
>>
>> Disable DHCP, and assign an address to each computer manually.
>>
>> Which firewall are you running? Any personal firewall absolutely has to have
>> some ability to open access for specified applications - and file sharing is one
>> very necessary application.
>>
>> If it's Windows Firewall (XP SP2 native firewall), for instance, you enable the
>> File and Printer Sharing exception, and set scope to the individual (fixed) ip
>> addresses used by the interfaces on the other computer.
>>
>> Don't disable SSID broadcast - some configurations require the SSID broadcast.
>> But change the SSID itself - to something that doesn't identify you, or the
>> equipment.
>>
>> Enable the router activity log. Examine it regularly. Know what each
>> connection listed represents - you? a neighbor?.
>>
>> Anyway, congrats on getting file sharing working. Now get your firewall
>> adjusted, then we can work out the Firewire issues.
>>
>> Cheers,
>> Chuck
>> Paranoia comes from experience - and is not necessarily a bad thing.
>>
>Chuck,
>
>Thanks for the information. I will work on the wireless LAN setup.
>Presently I have NIS and Windows Firewall enabled. I will try to alter these
>programs to let the 1394 connection to work.
>
>Is there some documentation I can follow in setting up the procedures you
>discussed:
>- disable remote (WAN) management
>- Enable WEP / WPA
>- Enable MAC filtering
>- Change the subnet of your LAN
>- Disable DHCP, and assign an address to each computer manually.
>- Changing SSID
>- Enable the router activity log
>
>The last time I tried some of the above options, I was unable to access the
>internet from any of the PCs.
>
>As for the firewire issue, that also is now working. When I was able to
>"ping" each machine, now the firewire connection works and I can transfer
>files between each PC.
>
>Your help has been greatly appreciated.
>
>Thanks

Dan,

Glad to help. That's what this forum is for.

All of these tasks, excepting the manual assignment of ip addresses, is a router
configuration issue.

Each tasks does indeed have the possibility of preventing you access,
unfortunately. You should make and test one change at a time. And familiarise
yourself with the hard rest process of the router, to return all settings to the
default state.

Fortunately, none of these tasks have to be done immediately. You should,
however, do each as soon as convenient.

You can get wireless advice in microsoft.public.windows.networking.wireless.
And help for your router in the BBR Forums <http://www.dslreports.com/forums>,
where there's a separate forum for each brand of router.

What make and model router do you have? I'll try to help you thru some of it.

You should probably disable one firewall or the other. Using two firewalls is a
good way to mess your networking up easily.

NPF (the firewall in NIS), IIRC, has two settings. Firstly, you have to define
a trusted zone. This is most easily done by specifying your subnet, though as I
said above you should use fixed, individual addresses for a wireless LAN.
Anyway, once you define the trusted addresses, you have to specify what traffic
you allow for them.

Windows Firewall is simpler. You simply enable the File and Printer Sharing
exception, and specify the scope (again either subnet, or individual addresses).

Look at this as a learning experience. You'll be able to advise your friends
after you get done.

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

[Dan]

"Chuck" wrote:

> On Sun, 31 Oct 2004 17:52:42 -0800, Dan > wrote:
>
> >"Chuck" wrote:
>
> <SNIP>
>
> >> Change the router management password, and disable remote (WAN) management.
> >>
> >> Enable WEP / WPA. Use non-trivial (non-guessable) values for each. (No "My dog
> >> has fleas").
> >>
> >> Enable MAC filtering.
> >>
> >> Change the subnet of your LAN - don't use the default.
> >>
> >> Disable DHCP, and assign an address to each computer manually.
> >>
> >> Which firewall are you running? Any personal firewall absolutely has to have
> >> some ability to open access for specified applications - and file sharing is one
> >> very necessary application.
> >>
> >> If it's Windows Firewall (XP SP2 native firewall), for instance, you enable the
> >> File and Printer Sharing exception, and set scope to the individual (fixed) ip
> >> addresses used by the interfaces on the other computer.
> >>
> >> Don't disable SSID broadcast - some configurations require the SSID broadcast.
> >> But change the SSID itself - to something that doesn't identify you, or the
> >> equipment.
> >>
> >> Enable the router activity log. Examine it regularly. Know what each
> >> connection listed represents - you? a neighbor?.
> >>
> >> Anyway, congrats on getting file sharing working. Now get your firewall
> >> adjusted, then we can work out the Firewire issues.
> >>
> >> Cheers,
> >> Chuck
> >> Paranoia comes from experience - and is not necessarily a bad thing.
> >>
> >Chuck,
> >
> >Thanks for the information. I will work on the wireless LAN setup.
> >Presently I have NIS and Windows Firewall enabled. I will try to alter these
> >programs to let the 1394 connection to work.
> >
> >Is there some documentation I can follow in setting up the procedures you
> >discussed:
> >- disable remote (WAN) management
> >- Enable WEP / WPA
> >- Enable MAC filtering
> >- Change the subnet of your LAN
> >- Disable DHCP, and assign an address to each computer manually.
> >- Changing SSID
> >- Enable the router activity log
> >
> >The last time I tried some of the above options, I was unable to access the
> >internet from any of the PCs.
> >
> >As for the firewire issue, that also is now working. When I was able to
> >"ping" each machine, now the firewire connection works and I can transfer
> >files between each PC.
> >
> >Your help has been greatly appreciated.
> >
> >Thanks
>
> Dan,
>
> Glad to help. That's what this forum is for.
>
> All of these tasks, excepting the manual assignment of ip addresses, is a router
> configuration issue.
>
> Each tasks does indeed have the possibility of preventing you access,
> unfortunately. You should make and test one change at a time. And familiarise
> yourself with the hard rest process of the router, to return all settings to the
> default state.
>
> Fortunately, none of these tasks have to be done immediately. You should,
> however, do each as soon as convenient.
>
> You can get wireless advice in microsoft.public.windows.networking.wireless.
> And help for your router in the BBR Forums <http://www.dslreports.com/forums>,
> where there's a separate forum for each brand of router.
>
> What make and model router do you have? I'll try to help you thru some of it.
>
> You should probably disable one firewall or the other. Using two firewalls is a
> good way to mess your networking up easily.
>
> NPF (the firewall in NIS), IIRC, has two settings. Firstly, you have to define
> a trusted zone. This is most easily done by specifying your subnet, though as I
> said above you should use fixed, individual addresses for a wireless LAN.
> Anyway, once you define the trusted addresses, you have to specify what traffic
> you allow for them.
>
> Windows Firewall is simpler. You simply enable the File and Printer Sharing
> exception, and specify the scope (again either subnet, or individual addresses).
>
> Look at this as a learning experience. You'll be able to advise your friends
> after you get done.
>
> Cheers,
> Chuck
> Paranoia comes from experience - and is not necessarily a bad thing.
>

The model is a Comtrend CT-534 Wireless ADSL Router. With respect to the
firewall, I would be leaning towared NIS. I will begin shortly on each of the
items listed above and see what falls out.

Thanks

[Chuck]

On Mon, 1 Nov 2004 09:28:05 -0800, Dan > wrote:

>"Chuck" wrote:
>
>> On Sun, 31 Oct 2004 17:52:42 -0800, Dan > wrote:
>>
>> >"Chuck" wrote:
>>
>> <SNIP>
>>
>> >> Change the router management password, and disable remote (WAN) management.
>> >>
>> >> Enable WEP / WPA. Use non-trivial (non-guessable) values for each. (No "My dog
>> >> has fleas").
>> >>
>> >> Enable MAC filtering.
>> >>
>> >> Change the subnet of your LAN - don't use the default.
>> >>
>> >> Disable DHCP, and assign an address to each computer manually.
>> >>
>> >> Which firewall are you running? Any personal firewall absolutely has to have
>> >> some ability to open access for specified applications - and file sharing is one
>> >> very necessary application.
>> >>
>> >> If it's Windows Firewall (XP SP2 native firewall), for instance, you enable the
>> >> File and Printer Sharing exception, and set scope to the individual (fixed) ip
>> >> addresses used by the interfaces on the other computer.
>> >>
>> >> Don't disable SSID broadcast - some configurations require the SSID broadcast.
>> >> But change the SSID itself - to something that doesn't identify you, or the
>> >> equipment.
>> >>
>> >> Enable the router activity log. Examine it regularly. Know what each
>> >> connection listed represents - you? a neighbor?.
>> >>
>> >> Anyway, congrats on getting file sharing working. Now get your firewall
>> >> adjusted, then we can work out the Firewire issues.
>> >>
>> >> Cheers,
>> >> Chuck
>> >> Paranoia comes from experience - and is not necessarily a bad thing.
>> >>
>> >Chuck,
>> >
>> >Thanks for the information. I will work on the wireless LAN setup.
>> >Presently I have NIS and Windows Firewall enabled. I will try to alter these
>> >programs to let the 1394 connection to work.
>> >
>> >Is there some documentation I can follow in setting up the procedures you
>> >discussed:
>> >- disable remote (WAN) management
>> >- Enable WEP / WPA
>> >- Enable MAC filtering
>> >- Change the subnet of your LAN
>> >- Disable DHCP, and assign an address to each computer manually.
>> >- Changing SSID
>> >- Enable the router activity log
>> >
>> >The last time I tried some of the above options, I was unable to access the
>> >internet from any of the PCs.
>> >
>> >As for the firewire issue, that also is now working. When I was able to
>> >"ping" each machine, now the firewire connection works and I can transfer
>> >files between each PC.
>> >
>> >Your help has been greatly appreciated.
>> >
>> >Thanks
>>
>> Dan,
>>
>> Glad to help. That's what this forum is for.
>>
>> All of these tasks, excepting the manual assignment of ip addresses, is a router
>> configuration issue.
>>
>> Each tasks does indeed have the possibility of preventing you access,
>> unfortunately. You should make and test one change at a time. And familiarise
>> yourself with the hard rest process of the router, to return all settings to the
>> default state.
>>
>> Fortunately, none of these tasks have to be done immediately. You should,
>> however, do each as soon as convenient.
>>
>> You can get wireless advice in microsoft.public.windows.networking.wireless.
>> And help for your router in the BBR Forums <http://www.dslreports.com/forums>,
>> where there's a separate forum for each brand of router.
>>
>> What make and model router do you have? I'll try to help you thru some of it.
>>
>> You should probably disable one firewall or the other. Using two firewalls is a
>> good way to mess your networking up easily.
>>
>> NPF (the firewall in NIS), IIRC, has two settings. Firstly, you have to define
>> a trusted zone. This is most easily done by specifying your subnet, though as I
>> said above you should use fixed, individual addresses for a wireless LAN.
>> Anyway, once you define the trusted addresses, you have to specify what traffic
>> you allow for them.
>>
>> Windows Firewall is simpler. You simply enable the File and Printer Sharing
>> exception, and specify the scope (again either subnet, or individual addresses).
>>
>> Look at this as a learning experience. You'll be able to advise your friends
>> after you get done.
>>
>> Cheers,
>> Chuck
>> Paranoia comes from experience - and is not necessarily a bad thing.
>>
>
>The model is a Comtrend CT-534 Wireless ADSL Router. With respect to the
>firewall, I would be leaning towared NIS. I will begin shortly on each of the
>items listed above and see what falls out.
>
>Thanks

OK, Dan. Please reply in this thread (same Subject) when you do.

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