Filesharing Vista Ultimate

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I posted my problem on 26 april. But nobody has a solution. That is why I
post it again with the replies so far.

Hello,

I am running an peer-to-peer network with Vista Utlimate & XP Home.
Both workstations are behind a NAT Router. The peer-to-peer network always
worked without any problems untill I replaced the hardware of my Vista
workstations and did a complete reinstall of Vista.
Problem: File/Print sharing isn't working as it should be.

My network is set to Private
Sharing and Discovery settings are all ON for :

Network Discovery,
File Sharing,
Pulic Folder Sharing,
Printer Sharing,
Password Protected Sharing,
MEdia Sharing

On the vista workstation:
When I attempt to create a new folder share I get "Your folder cannot be
shared", but the shares are created.
I can see my vista workstation in the Explorer > Network, but when I select
I get the message: "\\vistaws 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 specified network name
is invalid"

I have administrator rights.
Disabled the Windows Firewall Service.
Disabled the Windows Defender Service.
Removed OneCare.

When I Run: \\vistaws from the Run windows ik get the message: A device
attached to the system is not functioning.

I can ping vistaws by hostname&ipaddress from vistaws
I can ping vistaws by hostname&ipaddress from xphomews
I can ping xphomews by ipaddress from vistaws
I cannot ping xphomews by hostname from vistaws
I can ping xphomews by hostname&ipaddress from xphomews

T tried to enable NetBIOS over TCP/IP.

When I run nbtstat -n from vistaws:

Node IpAddress: [192.168.1.36] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
VISTAWS <20> UNIQUE Registered
"I think something is missing here"
I think it should be like tihs:
Name Type Status
---------------------------------------------
VISTAWS <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
VISTAWS <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered

I hope somebody can help me with this (I think0 very strange) issue.
thanks in advance.

Sebastian.
Click to expand...


Sebastian,

What name resolution are you using?
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

The error "The specified network name is invalid" is a name resolution problem.
Probably "NetBT broadcast" aka "SMB" name resolution, which is sensitive to
NetBT and personal firewall settings.

When you disable the WF service, you may break Windows Networking.
Disabled the Windows Firewall Service.
Click to expand...
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

Enable and start the service, then Disable the firewall (if you must). Don't
stop the service. Better yet, configure NetBT / SMBs, and all personal
firewalls, consistently.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html
Click to expand...

Hi Chuck,
What name resolution are you using?
Click to expand...
My ip configuration:
Windows IP Configuration

Host Name . . . . . . . . . . . . : Vistaws
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lokaal

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : lokaal
Description . . . . . . . . . . . : Realtek RTL8187 Wireless 802.11g
54Mbps U
SB 2.0 Network Adapter
Physical Address. . . . . . . . . : 00-15-AF-05-51-3A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ec4f:124:163:9ac4%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.36(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, April 24, 2007 5:25:58 AM
Lease Expires . . . . . . . . . . : Friday, April 27, 2007 5:25:58 AM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 184554927
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . : lokaal
Description . . . . . . . . . . . : isatap.lokaal
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.36%12(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4136:e37a:8ee:1bdb:3f57:fedb(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::8ee:1bdb:3f57:fedb%10(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Enable and start the service, then Disable the firewall (if you must). Don't
stop the service. Better yet, configure NetBT / SMBs, and all personal
firewalls, consistently.
Click to expand...
I enabled the windows firewall service and followed your instructions.
Added the following ports:
137 tcp & upd
138 tcp & udp
139 tcp & udp
445 tcp
"File and Printer sharing" is also enabled in the firewall.

Still having the problem.

Sebastian
 
Turn "Password protected sharing" OFF. The ON setting dose not allow folders
to be shared on a network. The dropdown to the right of the setting explains
this.

Sebastian said:
I posted my problem on 26 april. But nobody has a solution. That is why I
post it again with the replies so far.

Hello,

I am running an peer-to-peer network with Vista Utlimate & XP Home.
Both workstations are behind a NAT Router. The peer-to-peer network always
worked without any problems untill I replaced the hardware of my Vista
workstations and did a complete reinstall of Vista.
Problem: File/Print sharing isn't working as it should be.

My network is set to Private
Sharing and Discovery settings are all ON for :

Network Discovery,
File Sharing,
Pulic Folder Sharing,
Printer Sharing,
Password Protected Sharing,
MEdia Sharing

On the vista workstation:
When I attempt to create a new folder share I get "Your folder cannot be
shared", but the shares are created.
I can see my vista workstation in the Explorer > Network, but when I select
I get the message: "\\vistaws 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 specified network name
is invalid"

I have administrator rights.
Disabled the Windows Firewall Service.
Disabled the Windows Defender Service.
Removed OneCare.

When I Run: \\vistaws from the Run windows ik get the message: A device
attached to the system is not functioning.

I can ping vistaws by hostname&ipaddress from vistaws
I can ping vistaws by hostname&ipaddress from xphomews
I can ping xphomews by ipaddress from vistaws
I cannot ping xphomews by hostname from vistaws
I can ping xphomews by hostname&ipaddress from xphomews

T tried to enable NetBIOS over TCP/IP.

When I run nbtstat -n from vistaws:

Node IpAddress: [192.168.1.36] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
VISTAWS <20> UNIQUE Registered
"I think something is missing here"
I think it should be like tihs:
Name Type Status
---------------------------------------------
VISTAWS <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
VISTAWS <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered

I hope somebody can help me with this (I think0 very strange) issue.
thanks in advance.

Sebastian.
Click to expand...


Sebastian,

What name resolution are you using?
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

The error "The specified network name is invalid" is a name resolution problem.
Probably "NetBT broadcast" aka "SMB" name resolution, which is sensitive to
NetBT and personal firewall settings.

When you disable the WF service, you may break Windows Networking.
Disabled the Windows Firewall Service.
Click to expand...
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

Enable and start the service, then Disable the firewall (if you must). Don't
stop the service. Better yet, configure NetBT / SMBs, and all personal
firewalls, consistently.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html
Click to expand...

Hi Chuck,
What name resolution are you using?
Click to expand...
My ip configuration:
Windows IP Configuration

Host Name . . . . . . . . . . . . : Vistaws
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lokaal

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : lokaal
Description . . . . . . . . . . . : Realtek RTL8187 Wireless 802.11g
54Mbps U
SB 2.0 Network Adapter
Physical Address. . . . . . . . . : 00-15-AF-05-51-3A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ec4f:124:163:9ac4%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.36(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, April 24, 2007 5:25:58 AM
Lease Expires . . . . . . . . . . : Friday, April 27, 2007 5:25:58 AM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 184554927
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . : lokaal
Description . . . . . . . . . . . : isatap.lokaal
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.36%12(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4136:e37a:8ee:1bdb:3f57:fedb(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::8ee:1bdb:3f57:fedb%10(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Enable and start the service, then Disable the firewall (if you must). Don't
stop the service. Better yet, configure NetBT / SMBs, and all personal
firewalls, consistently.
Click to expand...
I enabled the windows firewall service and followed your instructions.
Added the following ports:
137 tcp & upd
138 tcp & udp
139 tcp & udp
445 tcp
"File and Printer sharing" is also enabled in the firewall.

Still having the problem.

Sebastian
Click to expand...
 
Hi Kentsyl,

I tried but it doesn't work. When I turn it off it still comes with the ÿour
folder could not be shared" message and my own machine in the network is not
accessible.

Sebastian.

kentsyl said:
Turn "Password protected sharing" OFF. The ON setting dose not allow folders
to be shared on a network. The dropdown to the right of the setting explains
this.

Sebastian said:
I posted my problem on 26 april. But nobody has a solution. That is why I
post it again with the replies so far.

On Thu, 26 Apr 2007 03:52:03 -0700, Sebastian

Hello,

I am running an peer-to-peer network with Vista Utlimate & XP Home.
Both workstations are behind a NAT Router. The peer-to-peer network always
worked without any problems untill I replaced the hardware of my Vista
workstations and did a complete reinstall of Vista.
Problem: File/Print sharing isn't working as it should be.

My network is set to Private
Sharing and Discovery settings are all ON for :

Network Discovery,
File Sharing,
Pulic Folder Sharing,
Printer Sharing,
Password Protected Sharing,
MEdia Sharing

On the vista workstation:
When I attempt to create a new folder share I get "Your folder cannot be
shared", but the shares are created.
I can see my vista workstation in the Explorer > Network, but when I select
I get the message: "\\vistaws 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 specified network name
is invalid"

I have administrator rights.
Disabled the Windows Firewall Service.
Disabled the Windows Defender Service.
Removed OneCare.

When I Run: \\vistaws from the Run windows ik get the message: A device
attached to the system is not functioning.

I can ping vistaws by hostname&ipaddress from vistaws
I can ping vistaws by hostname&ipaddress from xphomews
I can ping xphomews by ipaddress from vistaws
I cannot ping xphomews by hostname from vistaws
I can ping xphomews by hostname&ipaddress from xphomews

T tried to enable NetBIOS over TCP/IP.

When I run nbtstat -n from vistaws:

Node IpAddress: [192.168.1.36] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
VISTAWS <20> UNIQUE Registered
"I think something is missing here"
I think it should be like tihs:
Name Type Status
---------------------------------------------
VISTAWS <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
VISTAWS <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered

I hope somebody can help me with this (I think0 very strange) issue.
thanks in advance.

Sebastian.


Sebastian,

What name resolution are you using?
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

The error "The specified network name is invalid" is a name resolution problem.
Probably "NetBT broadcast" aka "SMB" name resolution, which is sensitive to
NetBT and personal firewall settings.

When you disable the WF service, you may break Windows Networking.
Disabled the Windows Firewall Service.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

Enable and start the service, then Disable the firewall (if you must). Don't
stop the service. Better yet, configure NetBT / SMBs, and all personal
firewalls, consistently.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html
Click to expand...

Hi Chuck,
What name resolution are you using?
Click to expand...
My ip configuration:
Windows IP Configuration

Host Name . . . . . . . . . . . . : Vistaws
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lokaal

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : lokaal
Description . . . . . . . . . . . : Realtek RTL8187 Wireless 802.11g
54Mbps U
SB 2.0 Network Adapter
Physical Address. . . . . . . . . : 00-15-AF-05-51-3A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ec4f:124:163:9ac4%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.36(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, April 24, 2007 5:25:58 AM
Lease Expires . . . . . . . . . . : Friday, April 27, 2007 5:25:58 AM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 184554927
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . : lokaal
Description . . . . . . . . . . . : isatap.lokaal
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.36%12(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4136:e37a:8ee:1bdb:3f57:fedb(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::8ee:1bdb:3f57:fedb%10(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Enable and start the service, then Disable the firewall (if you must). Don't
stop the service. Better yet, configure NetBT / SMBs, and all personal
firewalls, consistently.
Click to expand...
I enabled the windows firewall service and followed your instructions.
Added the following ports:
137 tcp & upd
138 tcp & udp
139 tcp & udp
445 tcp
"File and Printer sharing" is also enabled in the firewall.

Still having the problem.

Sebastian
Click to expand...
Click to expand...
 
Back
Top