"James McIllece [MS]" <(E-Mail Removed)> wrote in
news:Xns95AA96BDD9DC0jamesmcionlinemicros@207.46.2 48.16:
> "Ondrej Sevecek" <ondra_at_sevecek_dt_com> wrote in
> news:#(E-Mail Removed):
>
>> I have done it both ways already, but neither worked on 2003. But
>> now, I tested it on my XP system and there it ran.
>>
>> Is there a possibility that it might not run on 2003 system? I have
>> installed support tools (do not know from what system's CD) and
>> resource kit tools.
>>
>> I am very thankfull to your answer anyway.
>>
>> Ondra.
>>
>>
>>
>> "James McIllece [MS]" <(E-Mail Removed)> wrote in
>> message news:Xns95AA761C0A79Bjamesmcionlinemicros@207.46.2 48.16...
>>> "Ondrej Sevecek" <ondra_at_sevecek_dt_com> wrote in
>>> news:ud$(E-Mail Removed):
>>>
>>> > Hello,
>>> >
>>> > as stated at MS weg:
>>> > http://www.microsoft.com/resources/d...owsServ/2003/s
>>> > t and
>>> > ard/proddocs/en-us/Default.asp?url=/resources/documentation/Windows
>>> > S erv /2003/standard/proddocs/en-us/netsh_bridge.asp
>>> >
>>> > NETSH should contain context called BRIDGE. Either non is included
>>> > or I have been wrong. So how can I switch NETSH to the BRIDGE
>>> > context? I have Server 2003 Ent.
>>> >
>>> > O.
>>> >
>>> >
>>> >
>>>
>>> You are probably having trouble because if you type "netsh bridge"
>>> and press enter, it doesn't work. Do this instead:
>>>
>>> At a command prompt, type netsh, then press enter. Then type bridge,
>>> and press enter.
>>>
>>> Note that if you are executing a script with a specific full
>>> command, the script will execute properly.
>>>
>>> --
>>> James McIllece, Microsoft
>>>
>>> Please do not send email directly to this alias. This is my online
>> account
>>> name for newsgroup participation only.
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>>
>
> That's weird. Before I answered your original question I logged onto a
> WS03 machine and tested it, so I know the netsh bridge context is
> available on WS03 Enterprise.
>
> This is just a guess, but you may need to have administrative
> privileges on the server to run netsh, I'm not sure. If you performed
> your test with admin privileges and it didn't work, I guess the next
> step would be to remove the support tools pack you installed and then
> test the context.
>
> Other than that I don't have any ideas for you, but perhaps someone
> else will -- and I will ask around to see if anyone else has
> encountered this problem.
>
Hi again Ondrej --
I asked one of my coworkers about this and he suggested that I mention to
you that you can't execute netsh bridge commands unless you have already
bridged the connection between two network adapters.
You should be able to enter the netsh bridge context without having bridged
the adapters, however the commands won't work.
It seemed to me from your posts that the problem you were having was that
you couldn't even enter the "bridge" context, but I thought I would relay
this information in case there was a misunderstanding.
So to clarify, the first step is to bridge connections in the Network
Connections folder -- then open Command Prompt, type netsh, then enter,
then bridge, then enter, and then you should be able to execute the netsh
bridge commands.
Hope that helps --
--
James McIllece, Microsoft
Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.
This posting is provided "AS IS" with no warranties, and confers no rights.
Similar Threads
Linear Mode
