Problems Setting Up a Small Wireless Home Network

[Guest]

I am new at this game, so please keep it simple. I am trying to set up a
network to allow sharing between two machines running Office XP Home. My
wireless "workstation" appears to be working well, with both it and the
"server" appearing in the "View Workgroup Computers" list. When I double
click on the "server", I get a message which says "\\<server name> is not
accessible. You might not have permission to use the network resource.
Contact the administrator of this server to find out if you have access
permissions. The network path is not found." The problems with the "server"
are more profound. When I click "View Workgroup Computers", nothing is
listed, and I get the error "<workgroup name> is not available. 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".

I can ping the workstation from the server, but I can't ping the server from
the workstation. I can ping the router from both machines, and can access
the internet from both. I cannot share files between the two machines, and I
cannot print from the workstation.

Both machines have two users (two parents on the server, two kids on the
workstation) and a guest is set up on both machines - I have ensured that
there is no password for any of them. I have run browstat from the server,
and got the following message:


Status for domain STEVENS on transport
\Device\NetBT_Tcpip_{2146DAED-CED3-461C-ACC3-51263F11D51E}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Browstat on the workstation gives the following:

Status for domain STEVENS on transport
\Device\NetBT_Tcpip_{65809199-E4A5-4FB1-8C9F-9284C41E2895}
Browsing is active on domain.
Master browser name is: OFFICETWO
Master browser is running build 2600
1 backup servers retrieved from master OFFICETWO
\\OFFICETWO
There are 2 servers in domain STEVENS on transport
\Device\NetBT_Tcpip_{65809199-E4A5-4FB1-8C9F-9284C41E2895}
There are 1 domains in domain STEVENS on transport
\Device\NetBT_Tcpip_{65809199-E4A5-4FB1-8C9F-9284C41E2895}

Any thoughts? As I said, I am a bit of a nuffy on this stuff, so please
keep it simple.

 

[Chuck]

I am new at this game, so please keep it simple. I am trying to set up a
network to allow sharing between two machines running Office XP Home. My
wireless "workstation" appears to be working well, with both it and the
"server" appearing in the "View Workgroup Computers" list. When I double
click on the "server", I get a message which says "\\<server name> is not
accessible. You might not have permission to use the network resource.
Contact the administrator of this server to find out if you have access
permissions. The network path is not found." The problems with the "server"
are more profound. When I click "View Workgroup Computers", nothing is
listed, and I get the error "<workgroup name> is not available. 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".

I can ping the workstation from the server, but I can't ping the server from
the workstation. I can ping the router from both machines, and can access
the internet from both. I cannot share files between the two machines, and I
cannot print from the workstation.

Both machines have two users (two parents on the server, two kids on the
workstation) and a guest is set up on both machines - I have ensured that
there is no password for any of them. I have run browstat from the server,
and got the following message:


Status for domain STEVENS on transport
\Device\NetBT_Tcpip_{2146DAED-CED3-461C-ACC3-51263F11D51E}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Browstat on the workstation gives the following:

Status for domain STEVENS on transport
\Device\NetBT_Tcpip_{65809199-E4A5-4FB1-8C9F-9284C41E2895}
Browsing is active on domain.
Master browser name is: OFFICETWO
Master browser is running build 2600
1 backup servers retrieved from master OFFICETWO
\\OFFICETWO
There are 2 servers in domain STEVENS on transport
\Device\NetBT_Tcpip_{65809199-E4A5-4FB1-8C9F-9284C41E2895}
There are 1 domains in domain STEVENS on transport
\Device\NetBT_Tcpip_{65809199-E4A5-4FB1-8C9F-9284C41E2895}

Any thoughts? As I said, I am a bit of a nuffy on this stuff, so please
keep it simple.

Start from "I can't ping the server from the workstation". Check the firewall
on the server.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>

If nothing there to help, try and provide more details.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

 

[Ron Lowe]

I am new at this game, so please keep it simple. I am trying to set up a
network to allow sharing between two machines running Office XP Home. My
wireless "workstation" appears to be working well, with both it and the
"server" appearing in the "View Workgroup Computers" list. When I double
click on the "server", I get a message which says "\\<server name> is not
accessible. You might not have permission to use the network resource.
Contact the administrator of this server to find out if you have access
permissions. The network path is not found." The problems with the
"server"
are more profound. When I click "View Workgroup Computers", nothing is
listed, and I get the error "<workgroup name> is not available. 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".

I can ping the workstation from the server, but I can't ping the server
from
the workstation. I can ping the router from both machines, and can access
the internet from both. I cannot share files between the two machines,
and I
cannot print from the workstation.

Both machines have two users (two parents on the server, two kids on the
workstation) and a guest is set up on both machines - I have ensured that
there is no password for any of them. I have run browstat from the
server,
and got the following message:


Status for domain STEVENS on transport
\Device\NetBT_Tcpip_{2146DAED-CED3-461C-ACC3-51263F11D51E}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Browstat on the workstation gives the following:

Status for domain STEVENS on transport
\Device\NetBT_Tcpip_{65809199-E4A5-4FB1-8C9F-9284C41E2895}
Browsing is active on domain.
Master browser name is: OFFICETWO
Master browser is running build 2600
1 backup servers retrieved from master OFFICETWO
\\OFFICETWO
There are 2 servers in domain STEVENS on transport
\Device\NetBT_Tcpip_{65809199-E4A5-4FB1-8C9F-9284C41E2895}
There are 1 domains in domain STEVENS on transport
\Device\NetBT_Tcpip_{65809199-E4A5-4FB1-8C9F-9284C41E2895}

Any thoughts? As I said, I am a bit of a nuffy on this stuff, so please
keep it simple.

Sounds like firewall problems on 'server'.
Go into the windows firewall and on the exceptions tab, select the
File+Print sharing exception.

The network setup wizard should have made these
setting for you if you choose the correct path through it.

You can re-run the wizard on each machine, and choose these options:

First question, choose the middle option,
"Connect to the internet through a residential
gateway or other computer".

Accept or change the Computer Name.
Accept or change the Workgroup name.
( Irritatingly, it defaults to mshome, not the current workgroup. )

Select to enable File and Print Sharing.

Don't make a disk, just finish the wizard.

That should set up all the correct permissions etc.
It will enable the F+P exception in the firewall, and it will start the
browser service.
It will enable the Guest account, and grant it network access rights.

If you have 3-rd party firewalls or other security software, either
configure it for
F+P sharing, or un-install it untill you get everything working.

 

[Guest]

Guys,

I appreciate you taking the time out to help me. I pretty much tried both
of your approaches, with no luck. I have run the ipconfig /all, and got the
following on the server:



Windows IP Configuration



Host Name . . . . . . . . . . . . : MUMANDDAD

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection 3:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet

Physical Address. . . . . . . . . : 00-0F-EA-7E-24-E0

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.3

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 203.2.75.132

198.142.0.51

Lease Obtained. . . . . . . . . . : Wednesday, 15 June 2005 2:17:33 AM

Lease Expires . . . . . . . . . . : Wednesday, 15 June 2005 10:21:09
PM



Tunnel adapter Automatic Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-00-03

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.3%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled


I have not run it on the workstation, as you both seem to quickly have
determined that my problem is with the server.

Again, I appreciate your help.

Joff86

 

[Chuck]

Guys,

I appreciate you taking the time out to help me. I pretty much tried both
of your approaches, with no luck. I have run the ipconfig /all, and got the
following on the server:



Windows IP Configuration



Host Name . . . . . . . . . . . . : MUMANDDAD

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection 3:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet

Physical Address. . . . . . . . . : 00-0F-EA-7E-24-E0

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.3

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 203.2.75.132

198.142.0.51

Lease Obtained. . . . . . . . . . : Wednesday, 15 June 2005 2:17:33 AM

Lease Expires . . . . . . . . . . : Wednesday, 15 June 2005 10:21:09
PM



Tunnel adapter Automatic Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-00-03

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.3%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled


I have not run it on the workstation, as you both seem to quickly have
determined that my problem is with the server.

Again, I appreciate your help.

Joff86

Remove Teredo Tunneling aka IPV6.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>

 

[Chuck]

Guys,

I appreciate you taking the time out to help me. I pretty much tried both
of your approaches, with no luck. I have run the ipconfig /all, and got the
following on the server:



Windows IP Configuration



Host Name . . . . . . . . . . . . : MUMANDDAD

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection 3:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet

Physical Address. . . . . . . . . : 00-0F-EA-7E-24-E0

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.3

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 203.2.75.132

198.142.0.51

Lease Obtained. . . . . . . . . . : Wednesday, 15 June 2005 2:17:33 AM

Lease Expires . . . . . . . . . . : Wednesday, 15 June 2005 10:21:09
PM



Tunnel adapter Automatic Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-00-03

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.3%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled


I have not run it on the workstation, as you both seem to quickly have
determined that my problem is with the server.

Again, I appreciate your help.

Joff86

Remove Teredo Tunneling aka IPV6.
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>

 

[Ron Lowe]

Guys,

I appreciate you taking the time out to help me. I pretty much tried both
of your approaches, with no luck. I have run the ipconfig /all, and got
the
following on the server:

Is it the still the case that the server can ping the other machine,
but the other machine cannot ping the server?

If that is still the case, I'd still say there's a firewall problem on the
server.

And that the Windows firewall on the server has the
File+Print sharing exception enabled?

Just a point - are the machines running windows XP Service Pack 2?
The service pack level is important.

Removing IPv6 will simplify the configuration, and that can
only be a good thing during troubleshooting.

If the windows firewall is truly set to permit F+P sharing, then it should
also permit pings. So if it's not the Windows firewall, then I'd look for
another firewall.

Is there, or has there ever been, any 3-rd party firewall on the server
machine?

Is there any VPN client software on the machine? There is usually a
firewall hiding in there.

Untill you can get the assymetric ping problem sorted out, nothing else is
going to work.

 

[Guest]

Ron,

Yes I did have a VPN network on my machine, which for the time being (until
I get the networking working), I have now removed. Thanks to the tidying up
of network protocols that Chuck and yourself have recommended, I can now ping
both ways, and I can now share files from the workstation to the server
perfectly. I am still getting the same error, however, when I try to access
shared files from the server on the workstation. All very confusing - does
this mean that my problems with the server are now sorted, and I can
concentrate on the workstation?

I am exhausted - I was up to 3am on this last night, so I am heading off to
bed. I just wanted to thank you and Chuck for your assistance to date. I
will be back on the job tomorrow night, once I have caught up on some sleep.
Any thoughts that you have in the mean time would be appreciated. e.g. should
I now do a browstat and ipconfig /all from the workstation?

Thanks again.

Joff

 

[Chuck]

Ron,

Yes I did have a VPN network on my machine, which for the time being (until
I get the networking working), I have now removed. Thanks to the tidying up
of network protocols that Chuck and yourself have recommended, I can now ping
both ways, and I can now share files from the workstation to the server
perfectly. I am still getting the same error, however, when I try to access
shared files from the server on the workstation. All very confusing - does
this mean that my problems with the server are now sorted, and I can
concentrate on the workstation?

I am exhausted - I was up to 3am on this last night, so I am heading off to
bed. I just wanted to thank you and Chuck for your assistance to date. I
will be back on the job tomorrow night, once I have caught up on some sleep.
Any thoughts that you have in the mean time would be appreciated. e.g. should
I now do a browstat and ipconfig /all from the workstation?

Thanks again.

Joff

Joff,

The problem you're reporting - "\\<server name> is not accessible...", and
computers not visible in Network Neighborhood, is symptomatic of either a
firewall or master browser problem. Running "ipconfig /all" and "browstat
status" helps us isolate the problem, but you have to solve it.

If you just have two computers, simply disable the browser on one computer and
reboot both. If that doesn't do the job, please post updated "ipconfig /all"
and "browstat status", and we'll continue.
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html#Prevent>

 

[Ron Lowe]

Ron,

Yes I did have a VPN network on my machine, which for the time being
(until
I get the networking working), I have now removed. Thanks to the tidying
up
of network protocols that Chuck and yourself have recommended, I can now
ping
both ways, and I can now share files from the workstation to the server
perfectly. I am still getting the same error, however, when I try to
access
shared files from the server on the workstation. All very confusing -
does
this mean that my problems with the server are now sorted, and I can
concentrate on the workstation?

I am exhausted - I was up to 3am on this last night, so I am heading off
to
bed. I just wanted to thank you and Chuck for your assistance to date. I
will be back on the job tomorrow night, once I have caught up on some
sleep.
Any thoughts that you have in the mean time would be appreciated. e.g.
should
I now do a browstat and ipconfig /all from the workstation?

Thanks again.

Joff

Now the pings are sorted out, we can move on.

Can you clarify: the files you want to access are on the 'server',
and you want to access them from the 'workstation'?

If that's correct, go to the workstation and issue these
commands from a command prompt window:

ping <server ip address>
ping <server name>
net view
net view \\<server name>
net view \\<workstation name>

Do both the pings work ( IP address and name ?)
What errors do you get from the net view commands?

Now, on the server.
Go to a command prompt, and issue these commands:

ping <workstation ip address>
ping <workstation name>
net view
net view \\<server name>
net view \\<workstation name>
net share
net user guest

Can you dump the results of these tests?

 

[Guest]

Now the pings are sorted out, we can move on.

Can you clarify: the files you want to access are on the 'server',
and you want to access them from the 'workstation'?

If that's correct, go to the workstation and issue these
commands from a command prompt window:

ping <server ip address>
ping <server name>
net view
net view \\<server name>
net view \\<workstation name>

Do both the pings work ( IP address and name ?)
What errors do you get from the net view commands?

Now, on the server.
Go to a command prompt, and issue these commands:

ping <workstation ip address>
ping <workstation name>
net view
net view \\<server name>
net view \\<workstation name>
net share
net user guest

Can you dump the results of these tests?

Ron,

As a starting point, I would love to access files located on the server from
the workstation, but ideally, accessing files both ways would be better.
Anyway, here is the result of the tests from the workstation:

ping <server ip address>

Pinging 192.168.0.3 with 32 bytes of data:



Reply from 192.168.0.3: bytes=32 time=7ms TTL=128

Reply from 192.168.0.3: bytes=32 time=1ms TTL=128

Reply from 192.168.0.3: bytes=32 time=1ms TTL=128

Reply from 192.168.0.3: bytes=32 time=1ms TTL=128



Ping statistics for 192.168.0.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 7ms, Average = 2ms

ping <server name>

Pinging mumanddad [192.168.0.3] with 32 bytes of data:



Reply from 192.168.0.3: bytes=32 time=1ms TTL=128

Reply from 192.168.0.3: bytes=32 time=1ms TTL=128

Reply from 192.168.0.3: bytes=32 time=1ms TTL=128

Reply from 192.168.0.3: bytes=32 time=2ms TTL=128



Ping statistics for 192.168.0.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 2ms, Average = 1ms

net view

Server Name Remark

-------------------------------------------------------------------------------
\\MUMANDDAD Joff & Emma's Machine

\\OFFICETWO Children's Computer

The command completed successfully.

net view \\<server name>

System error 5 has occurred. Access is denied.

net view \\<workstation name>

Shared resources at \\officetwo

Children's Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
Shared Docs Disk
The command completed successfully.

And from the server:

ping <workstation ip address>

Pinging 192.168.0.2 with 32 bytes of data:



Reply from 192.168.0.2: bytes=32 time=1ms TTL=128

Reply from 192.168.0.2: bytes=32 time=2ms TTL=128

Reply from 192.168.0.2: bytes=32 time=2ms TTL=128

Reply from 192.168.0.2: bytes=32 time=1ms TTL=128



Ping statistics for 192.168.0.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 2ms, Average = 1ms


ping <workstation name>

Pinging officetwo [192.168.0.2] with 32 bytes of data:



Reply from 192.168.0.2: bytes=32 time=1ms TTL=128

Reply from 192.168.0.2: bytes=32 time=1ms TTL=128

Reply from 192.168.0.2: bytes=32 time=1ms TTL=128

Reply from 192.168.0.2: bytes=32 time=1ms TTL=128



Ping statistics for 192.168.0.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 1ms, Average = 1ms


net view

Server Name Remark

-------------------------------------------------------------------------------
\\MUMANDDAD Joff & Emma's Machine

\\OFFICETWO Children's Computer

The command completed successfully.

net view \\<server name>

Shared resources at \\mumanddad

Joff & Emma's Machine

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Microsoft Office Document Image Writer
Printer2 Print hp deskjet 960c
Shared Docs Disk
The command completed successfully.

net view \\<workstation name>

Shared resources at \\officetwo

Children's Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
Shared Docs Disk (UNC)
The command completed successfully.

net share

Share name Resource Remark

-------------------------------------------------------------------------------
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers

IPC$ Remote IPC

Shared Docs C:\Documents and Settings\All Users\Documents

Printer Microsoft Document Ima Spooled Microsoft Office Document Image
Wr
Printer2 USB001 Spooled hp deskjet 960c

The command completed successfully.


net user guest

User name Guest
Full Name
Comment Built-in account for guest access to the
computer/domain
User's comment
Country code 000 (System Default)
Account active Yes
Account expires Never

Password last set 6/13/2005 10:58 PM
Password expires Never
Password changeable 6/13/2005 10:58 PM
Password required No
User may change password No

Workstations allowed All
Logon script
User profile
Home directory
Last logon 6/16/2005 10:09 PM

Logon hours allowed All

Local Group Memberships *Guests
Global Group memberships *None
The command completed successfully.


I hope this help to resolve the problem - I am feeling a bit guilty about
taking up your time.

Regards,

Joff

 

[Ron Lowe]

System error 5 has occurred. Access is denied.

OK, that's good info.

Almost everything is working.

We can ping in both directions, by IP address and name.
That means the firewalls are probably OK, and name resolution is working.
The browse list is complete, and visible from both machines.
Each machine can enumerate it's own shares.
Each machine can list it's own shared resources.
Server can enumerate workstation's share.

The only problem is that workstation cannot enumerate server's shared
resources, and fails with error 5, access denied.

However, the Guest account is clearly active on the server machine, so share
enumeration ought so be possible.


So this leads us to a possible conclusion....

On the server, go to start | Run | type 'Regedit' in the box.

On the left hand pane, navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\

In the LSA folder, look in the right-hand pane.
look for the value 'RestrictAnonymous'.

It needs to be zero.
If it is not, double-click it and set it to zero.

( The value of RestrictAnonymousSam can be left at 1. )

Close regedit, and re-boot the server machine.

See if that helps.

 

[Guest]

Ron,

You champion!!! Well done - that did the trick. Thanks to you and Chuck
for all of your help. One more thing, and I almost hate to ask. As you
know, I removed the VPN software that I use to dial into my work in an effort
to get things working. Now that it is, I really need to reinstall it. I am
dreading doing it, in case it upsets things again, so I am wondering if there
are any special tricks that I should know about. Your thoughts would be much
appreciated.

Regards,

Joff

 

[Ron Lowe]

You champion!!! Well done - that did the trick. Thanks to you and Chuck

for all of your help. One more thing, and I almost hate to ask. As you
know, I removed the VPN software that I use to dial into my work in an
effort
to get things working. Now that it is, I really need to reinstall it. I
am
dreading doing it, in case it upsets things again, so I am wondering if
there
are any special tricks that I should know about. Your thoughts would be
much
appreciated.

Regards,

Joff

Go ahead and re-install it, but look through the options to find out where
the firewall is enabled.

If you tell us what VPN client software ( and version ) you are using,
perhaps someone will know how to configure it's firewall.

Normally, when you bring up a VPN client, it firewalls out other traffic
other than the tunnel on the network card so that all network traffic goes
down the tunnel. This is normally the desired behaviour. However, when
the tunnel is not running, it ought to be possible to shut down this
firewall.

 

[Guest]

Ron,

I reinstalled it (the software is called Check Point VPN-1 SecureClient),
and sure enough, it has introduced the problems again. The pinging of the
server from the workstation no longer works - what a pest! Would you advise
me starting off another post on this one?

Regards,

Joff

 

[Ron Lowe]

Ron,

I reinstalled it (the software is called Check Point VPN-1 SecureClient),
and sure enough, it has introduced the problems again. The pinging of the
server from the workstation no longer works - what a pest! Would you
advise
me starting off another post on this one?

Regards,

Joff

Probably best to start a new thread.

Look through the options on the VPN software.
There ought to be some way to disable the firewall whilst the VPN is not
running.

 

[Guest]

Ron,

I am not sure whether you are still "tuned in" to this thread, but on the
offchance that you are.... I have spoken with someone at work, who has given
me some instructions which apparently disables the firewall on the VPN. I
have done this, which allows me to ping the IP address in both directions.
Thereafter, however, things get hairy. I have run the diagnostics that you
previously asked me to post, which I outline below - keep in mind that the
VPN is on the server, MUMANDDAD:

On the workstation:
ping <server ip address>

Pinging 192.168.0.3 with 32 bytes of data:



Reply from 192.168.0.3: bytes=32 time=26ms TTL=128

Reply from 192.168.0.3: bytes=32 time=2ms TTL=128

Reply from 192.168.0.3: bytes=32 time=1ms TTL=128

Reply from 192.168.0.3: bytes=32 time=2ms TTL=128



Ping statistics for 192.168.0.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 26ms, Average = 7ms

ping <server name>

Pinging mumanddad [192.168.0.3] with 32 bytes of data:



Reply from 192.168.0.3: bytes=32 time=1ms TTL=128

Reply from 192.168.0.3: bytes=32 time=2ms TTL=128

Reply from 192.168.0.3: bytes=32 time=1ms TTL=128

Reply from 192.168.0.3: bytes=32 time=2ms TTL=128



Ping statistics for 192.168.0.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 2ms, Average = 1ms

net view

System error 6118 has occurred

net view \\<server name>

Shared resources at \\mumanddad

Joff & Emma's Machine

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Microsoft Office Document Image Writer
Printer2 Print hp deskjet 960c
Shared Docs Disk
The command completed successfully.


net view \\<workstation name>

Shared resources at \\officetwo

Children's Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
Shared Docs Disk
The command completed successfully.


On the server:
ping <workstation ip address>

Pinging 192.168.0.2 with 32 bytes of data:



Reply from 192.168.0.2: bytes=32 time=82ms TTL=128

Reply from 192.168.0.2: bytes=32 time=2ms TTL=128

Reply from 192.168.0.2: bytes=32 time=2ms TTL=128

Reply from 192.168.0.2: bytes=32 time=2ms TTL=128



Ping statistics for 192.168.0.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 2ms, Maximum = 82ms, Average = 22ms


ping <workstation name>

Ping request could not find host officetwo. Please check the name and try
again.

net view

System error 6118 has occurred

net view \\<server name>

Shared resources at \\mumanddad

Joff & Emma's Machine

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Microsoft Office Document Image Writer
Printer2 Print hp deskjet 960c
Shared Docs Disk
The command completed successfully.


net view \\<workstation name>

net view officetwo system error 53 has occurred

net share

Share name Resource Remark

-------------------------------------------------------------------------------
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers

IPC$ Remote IPC

Shared Docs C:\Documents and Settings\All Users\Documents

Printer Microsoft Document Ima Spooled Microsoft Office Document Image
Wr
Printer2 USB001 Spooled hp deskjet 960c

The command completed successfully.

net user guest

User name Guest
Full Name
Comment Built-in account for guest access to the
computer/domain
User's comment
Country code 000 (System Default)
Account active Yes
Account expires Never

Password last set 6/13/2005 10:58 PM
Password expires Never
Password changeable 6/13/2005 10:58 PM
Password required No
User may change password No

Workstations allowed All
Logon script
User profile
Home directory
Last logon 6/21/2005 9:50 PM

Logon hours allowed All

Local Group Memberships *Guests
Global Group memberships *None
The command completed successfully.

Any thoughts? Remember, I have disabled the browser on the workstation, but
it is still enabled on the server. Let me know if you think the advice on
the VPN was poor - it seems that the problems relate more to the workstation
now than the server, which made believe that the VPN side of things was OK.
Let me know if you disagree.

Regards,

Joff

 

[Ron Lowe]

OK, different day, differeent errors.
Now, assuming you have not made any changes to \\officetwo, we should focus
on \\mum&dad.

It looks like the server ( mum&dad) is not firewalled any more.
It responds to pings,
It responds to it's name;
It can be browsed.
That's good.

The \\officetwo machine is pingable by IP address, but not name, from the
server.
This is a Name Resolution problem. The machine is not resolving remote
NetBIOS names.

So the first thing I'd check is NetBIOS name resolution.

On \\mum&dad, go to a command prompt, and do an ipconfig /all
Report the 'Node Type'.

Also, check the workgroup name has not changed on this machine.

I'd quickly re-run the Network Setup Wizard on \\mum&dad, and choose the
Residential Gateway option, and yes, enable file sharing. Be sure to set
the workgroup name correctly. I don't think it will make much difference,
but I don't know what damage the VPN client did.

The browsing error ( 6118 ) we will deal with once we have sorted out Name
Resolution. This error is essentially a name resolution error too, neither
machine can find a Master Browser for your workgroup name.

The workstation would have started it's own, if the browser service was not
stopped. But leave it as it is for now, having 2 different browse lists
will just add to confusion.

Given that \\mum&dad can't resolve ANY netbios names, I'm not surprised it
cant't find a browser.
That will probably fix itself once we have fixed up NetBIOS name resolution.
However, I'm a little surprised that \\office2 can't find the browser
running on \\mum&dad.

The causes that I can think of are:

1) Firewalling on \\mum+dad : Unlikely. It's browsable.

2) Computer Browser service not started on \\mum+dad.
Check: start | Run | Services.msc
Check Computer Browser Service is started, startup type = Automatic.

3) The workgroup name on \\mum+dad is wrong.
\\mum+dad is maintaing a browse list for a different workgroup.
This would be visible on \\mum+dad, if name reslution was working.
So \\office2 cannot find a browser for it's workgroup, and can't start
its own,
because the browser service is disabled on it.

So re-check the workgroup name.

 

[Guest]

Ron,

I have tried to answer your questions one by one below, as best as I can:

Firstly, I must confess, I made one small change after these problems arose
I point out, in that I changed the \\mumanddad's Computer Browser setting
from Disabled to Automatic, and changed \\officetwo's from Automatic to
disabled. I powered down both machines, started up \\mumanddad first, then
did the same for \\officetwo. While I probably should not have made the
change, I must make it clear that the problems that have arisen since
reinstalling the VPN software were evident BEFORE I made this change. That
said, let me know if you think I should change it back.

Secondly, the 'node type' on \\mumanddad when I do an ipcofig /all is
"Unknown"

Thirdly, I reran the Network setup on \\mumanddad (and \\officetwo, for that
matter), and made sure that the workgroup name has not changed, and matches.
By the way, the workgroup name is "WORKGROUP".

The computer browser status is "Started" on \\mumanddad, with a Startup Type
of "Automatic". For the record, on \\officetwo, computer browser status is
null, with a Startup Type of "Disabled".

Finally, the workgroup name on \\mumanddad is the same as on \\officetwo
i.e. WORKGROUP.

I have run browstat on both machines and dumped the results below:

On \\mumanddad:

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{2146DAED-CED3-461C-ACC3-51263F11D51E}
Browsing is NOT active on domain.
Master browser name is held by: MUMANDDAD
Master browser is running build 2600

On \\officetwo:

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{65809199-E4A5-4FB1-8C9F-9284C41E2895}
Browsing is NOT active on domain.
Master browser name is held by: MUMANDDAD
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
\\MUMANDDAD . Version:05.01 Flags: 51203 NT POTENTIAL MASTER

Regards,

Joff