\\XXX is not accessible. you might not have permission to use this network resource!

  • Thread starter Thread starter Ahmad Sabry
  • Start date Start date
A

Ahmad Sabry

Guest
Hello!
i've a windows 2000\2003 domains , today i found computers not able to
browse the domain Network \\Sahm, but by nebios names it's working.
when they try to browse they get:
((\\XXX 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 network path was not found))
i restarted sever & brwoser services on server and clients and still not
accessible.

Any Help !!
 
Re: \\XXX is not accessible. you might not have permission to usethis network resource!

Re: \\XXX is not accessible. you might not have permission to usethis network resource!

On 16 Gen, 10:49, "Ahmad Sabry" <asa...@askmePLZ.com> wrote:
> Hello!
> i've a windows 2000\2003 domains , today i found computers not able to
> browse the domain Network \\Sahm, but by nebios names it's working.
> when they try to browse they get:
> ((\\XXX 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 network path was not found))
> i restarted sever & brwoser services on server and clients and still not
> accessible.
>
> Any Help !!

Hi!

Try with \\ipaddress to exclude Dns issue.
 
Re: \\XXX is not accessible. you might not have permission to use this network resource!

Re: \\XXX is not accessible. you might not have permission to use this network resource!

I already Can browse by netbios names of each member in domain, but
computers are not listed.
any additional reccomendations ?

Thanks
"Giampaolo Spaggiari - IT Consultant" <spaggiarig@gmail.com> wrote in
message
news:36e972f6-c9b2-4bbf-be44-62f468b04b07@s12g2000prg.googlegroups.com...
> On 16 Gen, 10:49, "Ahmad Sabry" <asa...@askmePLZ.com> wrote:
>> Hello!
>> i've a windows 2000\2003 domains , today i found computers not able to
>> browse the domain Network \\Sahm, but by nebios names it's working.
>> when they try to browse they get:
>> ((\\XXX 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 network path was not found))
>> i restarted sever & brwoser services on server and clients and still not
>> accessible.
>>
>> Any Help !!
>
> Hi!
>
> Try with \\ipaddress to exclude Dns issue.
 
Re: \\XXX is not accessible. you might not have permission to use this network resource!

Re: \\XXX is not accessible. you might not have permission to use this network resource!

Are you sure that NETBIOS over TCP/IP is enabled for all the clients?
"Ahmad Sabry" <asabry@askmePLZ.com> wrote in message
news:uq6pCGDWIHA.3556@TK2MSFTNGP02.phx.gbl...
>I already Can browse by netbios names of each member in domain, but
>computers are not listed.
> any additional reccomendations ?
>
> Thanks
> "Giampaolo Spaggiari - IT Consultant" <spaggiarig@gmail.com> wrote in
> message
> news:36e972f6-c9b2-4bbf-be44-62f468b04b07@s12g2000prg.googlegroups.com...
>> On 16 Gen, 10:49, "Ahmad Sabry" <asa...@askmePLZ.com> wrote:
>>> Hello!
>>> i've a windows 2000\2003 domains , today i found computers not able to
>>> browse the domain Network \\Sahm, but by nebios names it's working.
>>> when they try to browse they get:
>>> ((\\XXX 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 network path was not found))
>>> i restarted sever & brwoser services on server and clients and still not
>>> accessible.
>>>
>>> Any Help !!
>>
>> Hi!
>>
>> Try with \\ipaddress to exclude Dns issue.
>
>
>
 
Re: \\XXX is not accessible. you might not have permission to use this network resource!

Re: \\XXX is not accessible. you might not have permission to use this network resource!

I'm sure .. everything was worknig just fine.
The only thing has changed is the crashed ISA which operate as a DNS
forwarder "forward the internal requests"for sahm.com" to the internal
Domain name All other domains "like google and yahoo etc.." by using
external Domain.
i had a working ghost image i restored it after the crash, and after that
none can browse the network again.




"Nightlegend" <nightlegend@tiscali.co.uk> wrote in message
news:uve9PMEWIHA.4476@TK2MSFTNGP06.phx.gbl...
> Are you sure that NETBIOS over TCP/IP is enabled for all the clients?
> "Ahmad Sabry" <asabry@askmePLZ.com> wrote in message
> news:uq6pCGDWIHA.3556@TK2MSFTNGP02.phx.gbl...
>>I already Can browse by netbios names of each member in domain, but
>>computers are not listed.
>> any additional reccomendations ?
>>
>> Thanks
>> "Giampaolo Spaggiari - IT Consultant" <spaggiarig@gmail.com> wrote in
>> message
>> news:36e972f6-c9b2-4bbf-be44-62f468b04b07@s12g2000prg.googlegroups.com...
>>> On 16 Gen, 10:49, "Ahmad Sabry" <asa...@askmePLZ.com> wrote:
>>>> Hello!
>>>> i've a windows 2000\2003 domains , today i found computers not able to
>>>> browse the domain Network \\Sahm, but by nebios names it's working.
>>>> when they try to browse they get:
>>>> ((\\XXX 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 network path was not found))
>>>> i restarted sever & brwoser services on server and clients and still
>>>> not
>>>> accessible.
>>>>
>>>> Any Help !!
>>>
>>> Hi!
>>>
>>> Try with \\ipaddress to exclude Dns issue.
>>
>>
>>
>
>
 
Re: \\XXX is not accessible. you might not have permission to use this network resource!

Re: \\XXX is not accessible. you might not have permission to use this network resource!

you Can try removing each computer from the domail then readding it.

Peter

"Ahmad Sabry" <asabry@askmePLZ.com> wrote in message
news:uNsEqPFWIHA.1212@TK2MSFTNGP05.phx.gbl...
> I'm sure .. everything was worknig just fine.
> The only thing has changed is the crashed ISA which operate as a DNS
> forwarder "forward the internal requests"for sahm.com" to the internal
> Domain name All other domains "like google and yahoo etc.." by using
> external Domain.
> i had a working ghost image i restored it after the crash, and after that
> none can browse the network again.
>
>
>
>
> "Nightlegend" <nightlegend@tiscali.co.uk> wrote in message
> news:uve9PMEWIHA.4476@TK2MSFTNGP06.phx.gbl...
>> Are you sure that NETBIOS over TCP/IP is enabled for all the clients?
>> "Ahmad Sabry" <asabry@askmePLZ.com> wrote in message
>> news:uq6pCGDWIHA.3556@TK2MSFTNGP02.phx.gbl...
>>>I already Can browse by netbios names of each member in domain, but
>>>computers are not listed.
>>> any additional reccomendations ?
>>>
>>> Thanks
>>> "Giampaolo Spaggiari - IT Consultant" <spaggiarig@gmail.com> wrote in
>>> message
>>> news:36e972f6-c9b2-4bbf-be44-62f468b04b07@s12g2000prg.googlegroups.com...
>>>> On 16 Gen, 10:49, "Ahmad Sabry" <asa...@askmePLZ.com> wrote:
>>>>> Hello!
>>>>> i've a windows 2000\2003 domains , today i found computers not able to
>>>>> browse the domain Network \\Sahm, but by nebios names it's working.
>>>>> when they try to browse they get:
>>>>> ((\\XXX 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 network path was not found))
>>>>> i restarted sever & brwoser services on server and clients and still
>>>>> not
>>>>> accessible.
>>>>>
>>>>> Any Help !!
>>>>
>>>> Hi!
>>>>
>>>> Try with \\ipaddress to exclude Dns issue.
>>>
>>>
>>>
>>
>>
>
>
 
Re: \\XXX is not accessible. you might not have permission to use this network resource!

Re: \\XXX is not accessible. you might not have permission to use this network resource!

Hello Ahmad,

Is the crashed ISA configured as the DNS server of your domain at the client
workstations? Please post an ipconfig /all from one workstation.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I'm sure .. everything was worknig just fine.
> The only thing has changed is the crashed ISA which operate as a DNS
> forwarder "forward the internal requests"for sahm.com" to the internal
> Domain name All other domains "like google and yahoo etc.." by using
> external Domain.
> i had a working ghost image i restored it after the crash, and after
> that
> none can browse the network again.
> "Nightlegend" <nightlegend@tiscali.co.uk> wrote in message
> news:uve9PMEWIHA.4476@TK2MSFTNGP06.phx.gbl...
>
>> Are you sure that NETBIOS over TCP/IP is enabled for all the clients?
>> "Ahmad Sabry" <asabry@askmePLZ.com> wrote in message
>> news:uq6pCGDWIHA.3556@TK2MSFTNGP02.phx.gbl...
>>
>>> I already Can browse by netbios names of each member in domain, but
>>> computers are not listed.
>>> any additional reccomendations ?
>>> Thanks
>>> "Giampaolo Spaggiari - IT Consultant" <spaggiarig@gmail.com> wrote
>>> in
>>> message
>>> news:36e972f6-c9b2-4bbf-be44-62f468b04b07@s12g2000prg.googlegroups.c
>>> om...
>>>> On 16 Gen, 10:49, "Ahmad Sabry" <asa...@askmePLZ.com> wrote:
>>>>
>>>>> Hello!
>>>>> i've a windows 2000\2003 domains , today i found computers not
>>>>> able to
>>>>> browse the domain Network \\Sahm, but by nebios names it's
>>>>> working.
>>>>> when they try to browse they get:
>>>>> ((\\XXX 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 network path was not found))
>>>>> i restarted sever & brwoser services on server and clients and
>>>>> still
>>>>> not
>>>>> accessible.
>>>>> Any Help !!
>>>>>
>>>> Hi!
>>>>
>>>> Try with \\ipaddress to exclude Dns issue.
>>>>
 
Re: \\XXX is not accessible. you might not have permission to use this network resource!

Re: \\XXX is not accessible. you might not have permission to use this network resource!

Hello Meinolf !
this is from my machine "Which is a client just like others" :
Ethernet adapter LAN:
Connection-specific DNS Suffix . : SAHM.COM
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
Physical Address. . . . . . . . . : 00-1A-4D-6D-02-BF
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.3
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Thursday, January 17, 2008
9:36:10 AM
Lease Expires . . . . . . . . . . : Sunday, January 27, 2008 9:36:10
AM
This is from Domain at the branch office:
Windows IP Configuration
Host Name . . . . . . . . . . . . : SAHM1
Primary Dns Suffix . . . . . . . : sahm.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : sahm.com
PPP adapter RAS Server (Dial In) Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.18
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
Ethernet adapter LAN:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet
NIC #3
Physical Address. . . . . . . . . : 00-50-FC-2C-6C-A1
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.3
Ethernet adapter wan:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet
NIC #2
Physical Address. . . . . . . . . : 00-06-4F-00-F6-4B
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.0.102
PPP adapter Sahm:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.208
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 192.168.0.100
192.168.0.102

And that one from ISA1 , our gateway:

Windows IP Configuration
Host Name . . . . . . . . . . . . : ISA1
Primary Dns Suffix . . . . . . . : sahm.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : sahm.com
Ethernet adapter WAN-Built-In:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Compatible Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-11-09-BC-07-A2
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : XXX.XXX.XXX.XXX
Subnet Mask . . . . . . . . . . . : 255.255.255.252
Default Gateway . . . . . . . . . : XXX.XXX.XXX.XXX
DNS Servers . . . . . . . . . . . : 208.67.222.222
Ethernet adapter LAN:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA VT6105 Rhine III Compatible Fast
Ethernet Adapter
Physical Address. . . . . . . . . : 00-11-95-EB-A0-A1
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.3
I do aperciate it very much Meinolf .. Many thanks for help

Ahmad Sabry

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb667e2228ca268fcfd2a8ae@msnews.microsoft.com...
> Hello Ahmad,
>
> Is the crashed ISA configured as the DNS server of your domain at the
> client workstations? Please post an ipconfig /all from one workstation.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> I'm sure .. everything was worknig just fine.
>> The only thing has changed is the crashed ISA which operate as a DNS
>> forwarder "forward the internal requests"for sahm.com" to the internal
>> Domain name All other domains "like google and yahoo etc.." by using
>> external Domain.
>> i had a working ghost image i restored it after the crash, and after
>> that
>> none can browse the network again.
>> "Nightlegend" <nightlegend@tiscali.co.uk> wrote in message
>> news:uve9PMEWIHA.4476@TK2MSFTNGP06.phx.gbl...
>>
>>> Are you sure that NETBIOS over TCP/IP is enabled for all the clients?
>>> "Ahmad Sabry" <asabry@askmePLZ.com> wrote in message
>>> news:uq6pCGDWIHA.3556@TK2MSFTNGP02.phx.gbl...
>>>
>>>> I already Can browse by netbios names of each member in domain, but
>>>> computers are not listed.
>>>> any additional reccomendations ?
>>>> Thanks
>>>> "Giampaolo Spaggiari - IT Consultant" <spaggiarig@gmail.com> wrote
>>>> in
>>>> message
>>>> news:36e972f6-c9b2-4bbf-be44-62f468b04b07@s12g2000prg.googlegroups.c
>>>> om...
>>>>> On 16 Gen, 10:49, "Ahmad Sabry" <asa...@askmePLZ.com> wrote:
>>>>>
>>>>>> Hello!
>>>>>> i've a windows 2000\2003 domains , today i found computers not
>>>>>> able to
>>>>>> browse the domain Network \\Sahm, but by nebios names it's
>>>>>> working.
>>>>>> when they try to browse they get:
>>>>>> ((\\XXX 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 network path was not found))
>>>>>> i restarted sever & brwoser services on server and clients and
>>>>>> still
>>>>>> not
>>>>>> accessible.
>>>>>> Any Help !!
>>>>>>
>>>>> Hi!
>>>>>
>>>>> Try with \\ipaddress to exclude Dns issue.
>>>>>
>
>
 
Re: \\XXX is not accessible. you might not have permission to use this network resource!

Re: \\XXX is not accessible. you might not have permission to use this network resource!

Hello Ahmad,

Your client machine points to the ISA server as DNS server and not to the
Domain DNS server. This causes the problem with the domain access.

I think it would be a good solution to post this special configuration part
from domain and isa to the:

microsoft.public.isaserver
microsoft.public.isa.configuration
microsoft.public.isa.clients

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hello Meinolf !
> this is from my machine "Which is a client just like others" :
> Ethernet adapter LAN:
> Connection-specific DNS Suffix . : SAHM.COM
> Description . . . . . . . . . . . : Intel(R) PRO/100 VE
> Network
> Connection
> Physical Address. . . . . . . . . : 00-1A-4D-6D-02-BF
> 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.3
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> Lease Obtained. . . . . . . . . . : Thursday, January 17, 2008
> 9:36:10 AM
> Lease Expires . . . . . . . . . . : Sunday, January 27, 2008
> 9:36:10
> AM
> This is from Domain at the branch office:
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : SAHM1
> Primary Dns Suffix . . . . . . . : sahm.com
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : Yes
> DNS Suffix Search List. . . . . . : sahm.com
> PPP adapter RAS Server (Dial In) Interface:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.18
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . :
> Ethernet adapter LAN:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
> Ethernet
> NIC #3
> Physical Address. . . . . . . . . : 00-50-FC-2C-6C-A1
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.3
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 192.168.1.3
> Ethernet adapter wan:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
> Ethernet
> NIC #2
> Physical Address. . . . . . . . . : 00-06-4F-00-F6-4B
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.5
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> 192.168.0.102
> PPP adapter Sahm:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.0.208
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . : 0.0.0.0
> DNS Servers . . . . . . . . . . . : 192.168.0.100
> 192.168.0.102
> And that one from ISA1 , our gateway:
>
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : ISA1
> Primary Dns Suffix . . . . . . . : sahm.com
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : sahm.com
> Ethernet adapter WAN-Built-In:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : VIA Rhine II Compatible Fast
> Ethernet
> Adapter
> Physical Address. . . . . . . . . : 00-11-09-BC-07-A2
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : XXX.XXX.XXX.XXX
> Subnet Mask . . . . . . . . . . . : 255.255.255.252
> Default Gateway . . . . . . . . . : XXX.XXX.XXX.XXX
> DNS Servers . . . . . . . . . . . : 208.67.222.222
> Ethernet adapter LAN:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : VIA VT6105 Rhine III Compatible
> Fast
> Ethernet Adapter
> Physical Address. . . . . . . . . : 00-11-95-EB-A0-A1
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.1
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 192.168.1.3
> I do aperciate it very much Meinolf .. Many thanks for help
> Ahmad Sabry
>
> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
> news:ff16fb667e2228ca268fcfd2a8ae@msnews.microsoft.com...
>
>> Hello Ahmad,
>>
>> Is the crashed ISA configured as the DNS server of your domain at the
>> client workstations? Please post an ipconfig /all from one
>> workstation.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> I'm sure .. everything was worknig just fine.
>>> The only thing has changed is the crashed ISA which operate as a DNS
>>> forwarder "forward the internal requests"for sahm.com" to the
>>> internal
>>> Domain name All other domains "like google and yahoo etc.." by using
>>> external Domain.
>>> i had a working ghost image i restored it after the crash, and after
>>> that
>>> none can browse the network again.
>>> "Nightlegend" <nightlegend@tiscali.co.uk> wrote in message
>>> news:uve9PMEWIHA.4476@TK2MSFTNGP06.phx.gbl...
>>>> Are you sure that NETBIOS over TCP/IP is enabled for all the
>>>> clients? "Ahmad Sabry" <asabry@askmePLZ.com> wrote in message
>>>> news:uq6pCGDWIHA.3556@TK2MSFTNGP02.phx.gbl...
>>>>
>>>>> I already Can browse by netbios names of each member in domain,
>>>>> but
>>>>> computers are not listed.
>>>>> any additional reccomendations ?
>>>>> Thanks
>>>>> "Giampaolo Spaggiari - IT Consultant" <spaggiarig@gmail.com> wrote
>>>>> in
>>>>> message
>>>>> news:36e972f6-c9b2-4bbf-be44-62f468b04b07@s12g2000prg.googlegroups
>>>>> .c
>>>>> om...
>>>>>> On 16 Gen, 10:49, "Ahmad Sabry" <asa...@askmePLZ.com> wrote:
>>>>>>
>>>>>>> Hello!
>>>>>>> i've a windows 2000\2003 domains , today i found computers not
>>>>>>> able to
>>>>>>> browse the domain Network \\Sahm, but by nebios names it's
>>>>>>> working.
>>>>>>> when they try to browse they get:
>>>>>>> ((\\XXX 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 network path was not found))
>>>>>>> i restarted sever & brwoser services on server and clients and
>>>>>>> still
>>>>>>> not
>>>>>>> accessible.
>>>>>>> Any Help !!
>>>>>> Hi!
>>>>>>
>>>>>> Try with \\ipaddress to exclude Dns issue.
>>>>>>
 
Re: \\XXX is not accessible. you might not have permission to use this network resource!

Re: \\XXX is not accessible. you might not have permission to use this network resource!

Hi Meinolf ,,
i already configured my machine to point to the domain as a DNS but it has
the same problem.. let's skip ISA as it would be considered as a gateway in
this case. what supposed to stop the ability to browse the computer in my
domain??
Thank you.
"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb667e5008ca2702d645b47b@msnews.microsoft.com...
> Hello Ahmad,
>
> Your client machine points to the ISA server as DNS server and not to the
> Domain DNS server. This causes the problem with the domain access.
>
> I think it would be a good solution to post this special configuration
> part from domain and isa to the:
>
> microsoft.public.isaserver
> microsoft.public.isa.configuration
> microsoft.public.isa.clients
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Hello Meinolf !
>> this is from my machine "Which is a client just like others" :
>> Ethernet adapter LAN:
>> Connection-specific DNS Suffix . : SAHM.COM
>> Description . . . . . . . . . . . : Intel(R) PRO/100 VE
>> Network
>> Connection
>> Physical Address. . . . . . . . . : 00-1A-4D-6D-02-BF
>> 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.3
>> DNS Servers . . . . . . . . . . . : 192.168.1.1
>> Lease Obtained. . . . . . . . . . : Thursday, January 17, 2008
>> 9:36:10 AM
>> Lease Expires . . . . . . . . . . : Sunday, January 27, 2008
>> 9:36:10
>> AM
>> This is from Domain at the branch office:
>> Windows IP Configuration
>> Host Name . . . . . . . . . . . . : SAHM1
>> Primary Dns Suffix . . . . . . . : sahm.com
>> Node Type . . . . . . . . . . . . : Unknown
>> IP Routing Enabled. . . . . . . . : Yes
>> WINS Proxy Enabled. . . . . . . . : Yes
>> DNS Suffix Search List. . . . . . : sahm.com
>> PPP adapter RAS Server (Dial In) Interface:
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
>> Physical Address. . . . . . . . . : 00-53-45-00-00-00
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.18
>> Subnet Mask . . . . . . . . . . . : 255.255.255.255
>> Default Gateway . . . . . . . . . :
>> Ethernet adapter LAN:
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
>> Ethernet
>> NIC #3
>> Physical Address. . . . . . . . . : 00-50-FC-2C-6C-A1
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.3
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . :
>> DNS Servers . . . . . . . . . . . : 192.168.1.3
>> Ethernet adapter wan:
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
>> Ethernet
>> NIC #2
>> Physical Address. . . . . . . . . : 00-06-4F-00-F6-4B
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.5
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.1.1
>> DNS Servers . . . . . . . . . . . : 192.168.1.1
>> 192.168.0.102
>> PPP adapter Sahm:
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
>> Physical Address. . . . . . . . . : 00-53-45-00-00-00
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.0.208
>> Subnet Mask . . . . . . . . . . . : 255.255.255.255
>> Default Gateway . . . . . . . . . : 0.0.0.0
>> DNS Servers . . . . . . . . . . . : 192.168.0.100
>> 192.168.0.102
>> And that one from ISA1 , our gateway:
>>
>> Windows IP Configuration
>> Host Name . . . . . . . . . . . . : ISA1
>> Primary Dns Suffix . . . . . . . : sahm.com
>> Node Type . . . . . . . . . . . . : Unknown
>> IP Routing Enabled. . . . . . . . : Yes
>> WINS Proxy Enabled. . . . . . . . : No
>> DNS Suffix Search List. . . . . . : sahm.com
>> Ethernet adapter WAN-Built-In:
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : VIA Rhine II Compatible Fast
>> Ethernet
>> Adapter
>> Physical Address. . . . . . . . . : 00-11-09-BC-07-A2
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : XXX.XXX.XXX.XXX
>> Subnet Mask . . . . . . . . . . . : 255.255.255.252
>> Default Gateway . . . . . . . . . : XXX.XXX.XXX.XXX
>> DNS Servers . . . . . . . . . . . : 208.67.222.222
>> Ethernet adapter LAN:
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : VIA VT6105 Rhine III Compatible
>> Fast
>> Ethernet Adapter
>> Physical Address. . . . . . . . . : 00-11-95-EB-A0-A1
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.1
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . :
>> DNS Servers . . . . . . . . . . . : 192.168.1.3
>> I do aperciate it very much Meinolf .. Many thanks for help
>> Ahmad Sabry
>>
>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
>> news:ff16fb667e2228ca268fcfd2a8ae@msnews.microsoft.com...
>>
>>> Hello Ahmad,
>>>
>>> Is the crashed ISA configured as the DNS server of your domain at the
>>> client workstations? Please post an ipconfig /all from one
>>> workstation.
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> I'm sure .. everything was worknig just fine.
>>>> The only thing has changed is the crashed ISA which operate as a DNS
>>>> forwarder "forward the internal requests"for sahm.com" to the
>>>> internal
>>>> Domain name All other domains "like google and yahoo etc.." by using
>>>> external Domain.
>>>> i had a working ghost image i restored it after the crash, and after
>>>> that
>>>> none can browse the network again.
>>>> "Nightlegend" <nightlegend@tiscali.co.uk> wrote in message
>>>> news:uve9PMEWIHA.4476@TK2MSFTNGP06.phx.gbl...
>>>>> Are you sure that NETBIOS over TCP/IP is enabled for all the
>>>>> clients? "Ahmad Sabry" <asabry@askmePLZ.com> wrote in message
>>>>> news:uq6pCGDWIHA.3556@TK2MSFTNGP02.phx.gbl...
>>>>>
>>>>>> I already Can browse by netbios names of each member in domain,
>>>>>> but
>>>>>> computers are not listed.
>>>>>> any additional reccomendations ?
>>>>>> Thanks
>>>>>> "Giampaolo Spaggiari - IT Consultant" <spaggiarig@gmail.com> wrote
>>>>>> in
>>>>>> message
>>>>>> news:36e972f6-c9b2-4bbf-be44-62f468b04b07@s12g2000prg.googlegroups
>>>>>> .c
>>>>>> om...
>>>>>>> On 16 Gen, 10:49, "Ahmad Sabry" <asa...@askmePLZ.com> wrote:
>>>>>>>
>>>>>>>> Hello!
>>>>>>>> i've a windows 2000\2003 domains , today i found computers not
>>>>>>>> able to
>>>>>>>> browse the domain Network \\Sahm, but by nebios names it's
>>>>>>>> working.
>>>>>>>> when they try to browse they get:
>>>>>>>> ((\\XXX 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 network path was not found))
>>>>>>>> i restarted sever & brwoser services on server and clients and
>>>>>>>> still
>>>>>>>> not
>>>>>>>> accessible.
>>>>>>>> Any Help !!
>>>>>>> Hi!
>>>>>>>
>>>>>>> Try with \\ipaddress to exclude Dns issue.
>>>>>>>
>
>
 
Re: \\XXX is not accessible. you might not have permission to use this network resource!

Re: \\XXX is not accessible. you might not have permission to use this network resource!

Hello Ahmad,

I think it will be better to include the isa groups because you are using
the server and this adds functionality that i don't know. And as i said the
ipconfig from your client is only using the ISA not your domain DNS.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hi Meinolf ,,
> i already configured my machine to point to the domain as a DNS but it
> has
> the same problem.. let's skip ISA as it would be considered as a
> gateway in
> this case. what supposed to stop the ability to browse the computer in
> my
> domain??
> Thank you.
> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
> news:ff16fb667e5008ca2702d645b47b@msnews.microsoft.com...
>> Hello Ahmad,
>>
>> Your client machine points to the ISA server as DNS server and not to
>> the Domain DNS server. This causes the problem with the domain
>> access.
>>
>> I think it would be a good solution to post this special
>> configuration part from domain and isa to the:
>>
>> microsoft.public.isaserver
>> microsoft.public.isa.configuration
>> microsoft.public.isa.clients
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Hello Meinolf !
>>> this is from my machine "Which is a client just like others" :
>>> Ethernet adapter LAN:
>>> Connection-specific DNS Suffix . : SAHM.COM
>>> Description . . . . . . . . . . . : Intel(R) PRO/100 VE
>>> Network
>>> Connection
>>> Physical Address. . . . . . . . . : 00-1A-4D-6D-02-BF
>>> 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.3
>>> DNS Servers . . . . . . . . . . . : 192.168.1.1
>>> Lease Obtained. . . . . . . . . . : Thursday, January 17, 2008
>>> 9:36:10 AM
>>> Lease Expires . . . . . . . . . . : Sunday, January 27, 2008
>>> 9:36:10
>>> AM
>>> This is from Domain at the branch office:
>>> Windows IP Configuration
>>> Host Name . . . . . . . . . . . . : SAHM1
>>> Primary Dns Suffix . . . . . . . : sahm.com
>>> Node Type . . . . . . . . . . . . : Unknown
>>> IP Routing Enabled. . . . . . . . : Yes
>>> WINS Proxy Enabled. . . . . . . . : Yes
>>> DNS Suffix Search List. . . . . . : sahm.com
>>> PPP adapter RAS Server (Dial In) Interface:
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
>>> Physical Address. . . . . . . . . : 00-53-45-00-00-00
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.1.18
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.255
>>> Default Gateway . . . . . . . . . :
>>> Ethernet adapter LAN:
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
>>> Ethernet
>>> NIC #3
>>> Physical Address. . . . . . . . . : 00-50-FC-2C-6C-A1
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.1.3
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . :
>>> DNS Servers . . . . . . . . . . . : 192.168.1.3
>>> Ethernet adapter wan:
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
>>> Ethernet
>>> NIC #2
>>> Physical Address. . . . . . . . . : 00-06-4F-00-F6-4B
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.1.5
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>> DNS Servers . . . . . . . . . . . : 192.168.1.1
>>> 192.168.0.102
>>> PPP adapter Sahm:
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
>>> Physical Address. . . . . . . . . : 00-53-45-00-00-00
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.0.208
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.255
>>> Default Gateway . . . . . . . . . : 0.0.0.0
>>> DNS Servers . . . . . . . . . . . : 192.168.0.100
>>> 192.168.0.102
>>> And that one from ISA1 , our gateway:
>>> Windows IP Configuration
>>> Host Name . . . . . . . . . . . . : ISA1
>>> Primary Dns Suffix . . . . . . . : sahm.com
>>> Node Type . . . . . . . . . . . . : Unknown
>>> IP Routing Enabled. . . . . . . . : Yes
>>> WINS Proxy Enabled. . . . . . . . : No
>>> DNS Suffix Search List. . . . . . : sahm.com
>>> Ethernet adapter WAN-Built-In:
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : VIA Rhine II Compatible Fast
>>> Ethernet
>>> Adapter
>>> Physical Address. . . . . . . . . : 00-11-09-BC-07-A2
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : XXX.XXX.XXX.XXX
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.252
>>> Default Gateway . . . . . . . . . : XXX.XXX.XXX.XXX
>>> DNS Servers . . . . . . . . . . . : 208.67.222.222
>>> Ethernet adapter LAN:
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : VIA VT6105 Rhine III Compatible
>>> Fast
>>> Ethernet Adapter
>>> Physical Address. . . . . . . . . : 00-11-95-EB-A0-A1
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.1.1
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . :
>>> DNS Servers . . . . . . . . . . . : 192.168.1.3
>>> I do aperciate it very much Meinolf .. Many thanks for help
>>> Ahmad Sabry
>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
>>> news:ff16fb667e2228ca268fcfd2a8ae@msnews.microsoft.com...
>>>
>>>> Hello Ahmad,
>>>>
>>>> Is the crashed ISA configured as the DNS server of your domain at
>>>> the client workstations? Please post an ipconfig /all from one
>>>> workstation.
>>>>
>>>> Best regards
>>>>
>>>> Meinolf Weber
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers no rights.
>>>> ** Please do NOT email, only reply to Newsgroups
>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>> I'm sure .. everything was worknig just fine.
>>>>> The only thing has changed is the crashed ISA which operate as a
>>>>> DNS
>>>>> forwarder "forward the internal requests"for sahm.com" to the
>>>>> internal
>>>>> Domain name All other domains "like google and yahoo etc.." by
>>>>> using
>>>>> external Domain.
>>>>> i had a working ghost image i restored it after the crash, and
>>>>> after
>>>>> that
>>>>> none can browse the network again.
>>>>> "Nightlegend" <nightlegend@tiscali.co.uk> wrote in message
>>>>> news:uve9PMEWIHA.4476@TK2MSFTNGP06.phx.gbl...
>>>>>> Are you sure that NETBIOS over TCP/IP is enabled for all the
>>>>>> clients? "Ahmad Sabry" <asabry@askmePLZ.com> wrote in message
>>>>>> news:uq6pCGDWIHA.3556@TK2MSFTNGP02.phx.gbl...
>>>>>>
>>>>>>> I already Can browse by netbios names of each member in domain,
>>>>>>> but
>>>>>>> computers are not listed.
>>>>>>> any additional reccomendations ?
>>>>>>> Thanks
>>>>>>> "Giampaolo Spaggiari - IT Consultant" <spaggiarig@gmail.com>
>>>>>>> wrote
>>>>>>> in
>>>>>>> message
>>>>>>> news:36e972f6-c9b2-4bbf-be44-62f468b04b07@s12g2000prg.googlegrou
>>>>>>> ps
>>>>>>> .c
>>>>>>> om...
>>>>>>>> On 16 Gen, 10:49, "Ahmad Sabry" <asa...@askmePLZ.com> wrote:
>>>>>>>>
>>>>>>>>> Hello!
>>>>>>>>> i've a windows 2000\2003 domains , today i found computers not
>>>>>>>>> able to
>>>>>>>>> browse the domain Network \\Sahm, but by nebios names it's
>>>>>>>>> working.
>>>>>>>>> when they try to browse they get:
>>>>>>>>> ((\\XXX 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 network path was not found))
>>>>>>>>> i restarted sever & brwoser services on server and clients and
>>>>>>>>> still
>>>>>>>>> not
>>>>>>>>> accessible.
>>>>>>>>> Any Help !!
>>>>>>>> Hi!
>>>>>>>>
>>>>>>>> Try with \\ipaddress to exclude Dns issue.
>>>>>>>>
 

Similar threads

G
The feature you are trying to use is on a network resource that is unavailable
Replies
0
Views
327
gnartheratking
G
A
This video of Facebook being creepy might convince you to ditch the social network for good
Replies
0
Views
74
Andy Meek
A
M
This is the only Labor Day 2020 sale you need to shop this year – and it just started early
Replies
0
Views
84
Maren Estrada
M
V
Windows 10 Error: Windows cannot access the specified device, path, or file. You may not have the appropriate permission to access the item
Replies
0
Views
115
Vladimir Amir
V
J
This report might convince you to avoid hotels until coronavirus is gone
Replies
0
Views
99
Jacob Siegal
J
Back
Top