Hi, everyone!

I've just installed Windows 2008 Enterprise in a Virtual PC 2007 virtual
machine.
The server is set up as a PDC with it's own domain forrest, and has a
DNS server.

DNS resolves Ok, but I have 2 major issues.

1) If connecting to/from WinXP / Windows 2003 computer, the network
share is visible, but I cannot copy files. The operation fails after a
few seconds, with the "Network name cannot be found" (or "is not
available") error.

This works OK, if the client is Vista, so I presume it's a SMB 2.0
issue. Any hints on how to force the w2k8 box to use SMB 1.0?

2) From the w2k8 box, I cannot browse to www.microsoft.com,
www.mozilla.com, and a few other international sites. DNS resolution
works fine (ping is ok), website is found, but I get stuck on the
"waiting for response".
Local (in my country) sites work fine; everything works fine from other
computers in my main domain.

Help would be appreciated.

Regards,

Sigmund Jakhel
Integrum IT, Slovenia, Europe

RE: Windows 2008 & Win XP Client blues - Network name cannot be found by lforbes

lforbes
Thu Mar 27 21:20:00 PDT 2008

Hi,

I don't think it is an SMB issue. According to MS's site the SMB session is
set based on the clients.

http://technet.microsoft.com/en-us/library/bb726965.aspx

"Computers running Windows Server 2008 or Windows Vista support both SMB 1.0
and SMB 2.0. The version of SMB that is used for file sharing operations is
determined during the SMB session negotiation. The following table shows
which version of SMB that is used for various combinations of client and
server computers."

I haven't worked with 2008 yet and don't have any plans too for at least a
year. Maybe there is an update for Windows XP and 2003 in order to connect to
2008?

Have you tried mapping to the share using \\server\share and
\\server.domain.local\share?

Cheers,
Lara

"Ziga Jakhel" wrote:

> Hi, everyone!
>
> I've just installed Windows 2008 Enterprise in a Virtual PC 2007 virtual
> machine.
> The server is set up as a PDC with it's own domain forrest, and has a
> DNS server.
>
> DNS resolves Ok, but I have 2 major issues.
>
> 1) If connecting to/from WinXP / Windows 2003 computer, the network
> share is visible, but I cannot copy files. The operation fails after a
> few seconds, with the "Network name cannot be found" (or "is not
> available") error.
>
> This works OK, if the client is Vista, so I presume it's a SMB 2.0
> issue. Any hints on how to force the w2k8 box to use SMB 1.0?
>
> 2) From the w2k8 box, I cannot browse to www.microsoft.com,
> www.mozilla.com, and a few other international sites. DNS resolution
> works fine (ping is ok), website is found, but I get stuck on the
> "waiting for response".
> Local (in my country) sites work fine; everything works fine from other
> computers in my main domain.
>
> Help would be appreciated.
>
> Regards,
>
> Sigmund Jakhel
> Integrum IT, Slovenia, Europe
>

Re: Windows 2008 & Win XP Client blues - Network name cannot be found by Ziga

Ziga
Fri Mar 28 07:17:01 PDT 2008

Hi, Lara!

Thanks for the input... since Vista clients work, I strongly suspect
SMB. I know what the docs say (which presently isn't all that much), but
as a developer also know the differences to world-as-built :)

The fqdn naming gives the same results.

Regards,

Ziga

lforbes wrote:
> Hi,
>
> I don't think it is an SMB issue. According to MS's site the SMB session is
> set based on the clients.
>
> http://technet.microsoft.com/en-us/library/bb726965.aspx
>
> "Computers running Windows Server 2008 or Windows Vista support both SMB 1.0
> and SMB 2.0. The version of SMB that is used for file sharing operations is
> determined during the SMB session negotiation. The following table shows
> which version of SMB that is used for various combinations of client and
> server computers."
>
> I haven't worked with 2008 yet and don't have any plans too for at least a
> year. Maybe there is an update for Windows XP and 2003 in order to connect to
> 2008?
>
> Have you tried mapping to the share using \\server\share and
> \\server.domain.local\share?
>
> Cheers,
> Lara
>
> "Ziga Jakhel" wrote:
>
>> Hi, everyone!
>>
>> I've just installed Windows 2008 Enterprise in a Virtual PC 2007 virtual
>> machine.
>> The server is set up as a PDC with it's own domain forrest, and has a
>> DNS server.
>>
>> DNS resolves Ok, but I have 2 major issues.
>>
>> 1) If connecting to/from WinXP / Windows 2003 computer, the network
>> share is visible, but I cannot copy files. The operation fails after a
>> few seconds, with the "Network name cannot be found" (or "is not
>> available") error.
>>
>> This works OK, if the client is Vista, so I presume it's a SMB 2.0
>> issue. Any hints on how to force the w2k8 box to use SMB 1.0?
>>
>> 2) From the w2k8 box, I cannot browse to www.microsoft.com,
>> www.mozilla.com, and a few other international sites. DNS resolution
>> works fine (ping is ok), website is found, but I get stuck on the
>> "waiting for response".
>> Local (in my country) sites work fine; everything works fine from other
>> computers in my main domain.
>>
>> Help would be appreciated.
>>
>> Regards,
>>
>> Sigmund Jakhel
>> Integrum IT, Slovenia, Europe
>>

Re: Windows 2008 & Win XP Client blues - Network name cannot be fo by lforbes

lforbes
Fri Mar 28 12:48:01 PDT 2008

Hi,

That may be indeed true. Isn't Windows 2008 server still in RC? I didn't
think they have released the finished version yet but I may be wrong.

That being said I share my Vista machine at home between my XP machines with
no issues either way.

Cheers,
Lara

"Ziga Jakhel" wrote:

> Hi, Lara!
>
> Thanks for the input... since Vista clients work, I strongly suspect
> SMB. I know what the docs say (which presently isn't all that much), but
> as a developer also know the differences to world-as-built :)
>
> The fqdn naming gives the same results.
>
> Regards,
>
> Ziga
>
> lforbes wrote:
> > Hi,
> >
> > I don't think it is an SMB issue. According to MS's site the SMB session is
> > set based on the clients.
> >
> > http://technet.microsoft.com/en-us/library/bb726965.aspx
> >
> > "Computers running Windows Server 2008 or Windows Vista support both SMB 1.0
> > and SMB 2.0. The version of SMB that is used for file sharing operations is
> > determined during the SMB session negotiation. The following table shows
> > which version of SMB that is used for various combinations of client and
> > server computers."
> >
> > I haven't worked with 2008 yet and don't have any plans too for at least a
> > year. Maybe there is an update for Windows XP and 2003 in order to connect to
> > 2008?
> >
> > Have you tried mapping to the share using \\server\share and
> > \\server.domain.local\share?
> >
> > Cheers,
> > Lara
> >
> > "Ziga Jakhel" wrote:
> >
> >> Hi, everyone!
> >>
> >> I've just installed Windows 2008 Enterprise in a Virtual PC 2007 virtual
> >> machine.
> >> The server is set up as a PDC with it's own domain forrest, and has a
> >> DNS server.
> >>
> >> DNS resolves Ok, but I have 2 major issues.
> >>
> >> 1) If connecting to/from WinXP / Windows 2003 computer, the network
> >> share is visible, but I cannot copy files. The operation fails after a
> >> few seconds, with the "Network name cannot be found" (or "is not
> >> available") error.
> >>
> >> This works OK, if the client is Vista, so I presume it's a SMB 2.0
> >> issue. Any hints on how to force the w2k8 box to use SMB 1.0?
> >>
> >> 2) From the w2k8 box, I cannot browse to www.microsoft.com,
> >> www.mozilla.com, and a few other international sites. DNS resolution
> >> works fine (ping is ok), website is found, but I get stuck on the
> >> "waiting for response".
> >> Local (in my country) sites work fine; everything works fine from other
> >> computers in my main domain.
> >>
> >> Help would be appreciated.
> >>
> >> Regards,
> >>
> >> Sigmund Jakhel
> >> Integrum IT, Slovenia, Europe
> >>
>