ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual Server 2005

Recent Virtual Server 2005 posts

* Migration Fails
* Running W7 in VSRV 2005 R2
* New Virtual Server user question
* Running Windows 7 in Hyper-V
* Hyper-V standalone vs Hyper-V windows 2008 Core
* How do i know hyper-v works ?
* Hyper-V VSS Writer
* does standalone hyper-v comes with firewall ?
* Managing Standalone hyper-v server : The "MSVM_Virtualsystemmanagerservice" object was not found
* Slipstream Hyper-V Integration (nLite?)
* Can I copy a 18GB file to a Virtual Machine?
* how to activate the menu from hyper-v standalone server ?
* Enabling Hyper-V prevents host restarting
* Standalone Hyper-V Server
* Hyper-V and Virtual DHCP Server
* RRAS with 2 lan cards on Win2k8
* Hyper-V on HP workstation xw6200
* VSS restore using a new restore name
* Virtual guest services won"t install on a P2V Conversion
* Guest cannot ping host but everything else

Add Solution

Hyper-V networking

Source: microsoft.public.virtualserver
Sent: 01/12/2009
From: Patrick D.
Message:

Hi

On a full installation of W2k8 Enterprise I have Hyper-V (single physical
server).
Integration services are installed on all VMs.

All network-connections in the VMs have "limited or no connectivity" with an
IP of 169.x.x.x.
In case of normal connection, the VMs would obtain an IP from a DHCP Server
in the range of 192.168.x.x
The physical network adapter is on a brand new intel-mainboard (S5000XVN):
Intel Pro/1000 EB Network Connection with I/O Acceleration.

I chosed "external network type" in Virtual Network Manager and all VMs have
the VLAN ID 1.
What I discovered is, that the physical network adapter does not show the
point "VLAN ID" under Device-Manager/Network adapters/Intel
Nic/Properties/Advanced/Property.
Is this the reason, why my VMs have no connection?
Or what is the reason for this isolation of the VMs?

Thanks for your help.

Patrick

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Hyper-V networking

Sent: 01/12/2009
From: "Charlie Russel - MVP" <(email address - cut out)>
Message:

Do you have any DHCP server _on that VLAN_? If not, there's no way they'll
get an IP address, is there?

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Patrick D." <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Hi
>
> On a full installation of W2k8 Enterprise I have Hyper-V (single physical
> server).
> Integration services are installed on all VMs.
>
> All network-connections in the VMs have "limited or no connectivity" with
> an
> IP of 169.x.x.x.
> In case of normal connection, the VMs would obtain an IP from a DHCP
> Server
> in the range of 192.168.x.x
> The physical network adapter is on a brand new intel-mainboard (S5000XVN):
> Intel Pro/1000 EB Network Connection with I/O Acceleration.
>
> I chosed "external network type" in Virtual Network Manager and all VMs
> have
> the VLAN ID 1.
> What I discovered is, that the physical network adapter does not show the
> point "VLAN ID" under Device-Manager/Network adapters/Intel
> Nic/Properties/Advanced/Property.
> Is this the reason, why my VMs have no connection?
> Or what is the reason for this isolation of the VMs?
>
> Thanks for your help.
>
> Patrick

Re: Hyper-V networking

Sent: 01/13/2009
From: Patrick D.
Message:

Hi

does that mean, that with an "external network" an hyper-v solution on one
physical server can not communicate with a physical dhcp, which is not on
this physical machine?

Patrick

"Charlie Russel - MVP" wrote:

Show quoted text

> Do you have any DHCP server _on that VLAN_? If not, there's no way they'll
> get an IP address, is there?
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
> "Patrick D." <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hi
> >
> > On a full installation of W2k8 Enterprise I have Hyper-V (single physical
> > server).
> > Integration services are installed on all VMs.
> >
> > All network-connections in the VMs have "limited or no connectivity" with
> > an
> > IP of 169.x.x.x.
> > In case of normal connection, the VMs would obtain an IP from a DHCP
> > Server
> > in the range of 192.168.x.x
> > The physical network adapter is on a brand new intel-mainboard (S5000XVN):
> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
> >
> > I chosed "external network type" in Virtual Network Manager and all VMs
> > have
> > the VLAN ID 1.
> > What I discovered is, that the physical network adapter does not show the
> > point "VLAN ID" under Device-Manager/Network adapters/Intel
> > Nic/Properties/Advanced/Property.
> > Is this the reason, why my VMs have no connection?
> > Or what is the reason for this isolation of the VMs?
> >
> > Thanks for your help.
> >
> > Patrick
>
>

Re: Hyper-V networking

Sent: 01/13/2009
From: "Charlie Russel - MVP" <(email address - cut out)>
Message:

No, it means that with an external network in hyper-v, the _physical_ nic
doesn't have an IP address or run TCP/IP at all. If you set your network to
be on a vlan, it doesn't communicate with other computers that aren't on
that vlan.

Hyper-V networking is very different from anything we've worked with
before - it's NOT a bridge, unlike VS or VMWare. I'd _start_ by configuring
without any vlan stuff, make sure you get everything working. If you need
DHCP to the computers that are on the vlan, you'll want to make sure you
have a DHCP server that will be on that same vlan.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Patrick D." <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Hi
>
> does that mean, that with an "external network" an hyper-v solution on one
> physical server can not communicate with a physical dhcp, which is not on
> this physical machine?
>
> Patrick
>
> "Charlie Russel - MVP" wrote:
>
>> Do you have any DHCP server _on that VLAN_? If not, there's no way
>> they'll
>> get an IP address, is there?
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>> "Patrick D." <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Hi
>> >
>> > On a full installation of W2k8 Enterprise I have Hyper-V (single
>> > physical
>> > server).
>> > Integration services are installed on all VMs.
>> >
>> > All network-connections in the VMs have "limited or no connectivity"
>> > with
>> > an
>> > IP of 169.x.x.x.
>> > In case of normal connection, the VMs would obtain an IP from a DHCP
>> > Server
>> > in the range of 192.168.x.x
>> > The physical network adapter is on a brand new intel-mainboard
>> > (S5000XVN):
>> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
>> >
>> > I chosed "external network type" in Virtual Network Manager and all VMs
>> > have
>> > the VLAN ID 1.
>> > What I discovered is, that the physical network adapter does not show
>> > the
>> > point "VLAN ID" under Device-Manager/Network adapters/Intel
>> > Nic/Properties/Advanced/Property.
>> > Is this the reason, why my VMs have no connection?
>> > Or what is the reason for this isolation of the VMs?
>> >
>> > Thanks for your help.
>> >
>> > Patrick
>>
>>

Re: Hyper-V networking

Sent: 01/13/2009
From: Patrick D.
Message:

Hi Charlie

well, then I should go away from this test-solution, with external dhcp. The
final configuration will have a SBS 2008 (with dhcp) virtually on the same
vlan like all other servers.
Will this virtual SBS 2008 be able to give an IP to physical clients in the
same domain?

Patrick

"Charlie Russel - MVP" wrote:

Show quoted text

> No, it means that with an external network in hyper-v, the _physical_ nic
> doesn't have an IP address or run TCP/IP at all. If you set your network to
> be on a vlan, it doesn't communicate with other computers that aren't on
> that vlan.
>
> Hyper-V networking is very different from anything we've worked with
> before - it's NOT a bridge, unlike VS or VMWare. I'd _start_ by configuring
> without any vlan stuff, make sure you get everything working. If you need
> DHCP to the computers that are on the vlan, you'll want to make sure you
> have a DHCP server that will be on that same vlan.
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
> "Patrick D." <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hi
> >
> > does that mean, that with an "external network" an hyper-v solution on one
> > physical server can not communicate with a physical dhcp, which is not on
> > this physical machine?
> >
> > Patrick
> >
> > "Charlie Russel - MVP" wrote:
> >
> >> Do you have any DHCP server _on that VLAN_? If not, there's no way
> >> they'll
> >> get an IP address, is there?
> >>
> >> --
> >> Charlie.
> >> http://msmvps.com/blogs/xperts64
> >> http://mvp.support.microsoft.com/profile/charlie.russel
> >>
> >> "Patrick D." <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> > Hi
> >> >
> >> > On a full installation of W2k8 Enterprise I have Hyper-V (single
> >> > physical
> >> > server).
> >> > Integration services are installed on all VMs.
> >> >
> >> > All network-connections in the VMs have "limited or no connectivity"
> >> > with
> >> > an
> >> > IP of 169.x.x.x.
> >> > In case of normal connection, the VMs would obtain an IP from a DHCP
> >> > Server
> >> > in the range of 192.168.x.x
> >> > The physical network adapter is on a brand new intel-mainboard
> >> > (S5000XVN):
> >> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
> >> >
> >> > I chosed "external network type" in Virtual Network Manager and all VMs
> >> > have
> >> > the VLAN ID 1.
> >> > What I discovered is, that the physical network adapter does not show
> >> > the
> >> > point "VLAN ID" under Device-Manager/Network adapters/Intel
> >> > Nic/Properties/Advanced/Property.
> >> > Is this the reason, why my VMs have no connection?
> >> > Or what is the reason for this isolation of the VMs?
> >> >
> >> > Thanks for your help.
> >> >
> >> > Patrick
> >>
> >>
>
>

Re: Hyper-V networking

Sent: 01/13/2009
From: Patrick D.
Message:

Hi

my final solution will only have one dhcp. The sbs 2008 virtualized. Can I
still put the single physical server hyper-v solution on a external network
in this case?

Patrick

"Bill Grant" wrote:

Show quoted text

> Of course. But in that case I would not put it on an external network. I
> would run the SBS domain on a private virtual network. You can then use DHCP
> on this network and not interfere with the DHCP service on the physical LAN.
>
>
> "Patrick D." <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hi Charlie
> >
> > well, then I should go away from this test-solution, with external dhcp.
> > The
> > final configuration will have a SBS 2008 (with dhcp) virtually on the same
> > vlan like all other servers.
> > Will this virtual SBS 2008 be able to give an IP to physical clients in
> > the
> > same domain?
> >
> > Patrick
> >
> > "Charlie Russel - MVP" wrote:
> >
> >> No, it means that with an external network in hyper-v, the _physical_ nic
> >> doesn't have an IP address or run TCP/IP at all. If you set your network
> >> to
> >> be on a vlan, it doesn't communicate with other computers that aren't on
> >> that vlan.
> >>
> >> Hyper-V networking is very different from anything we've worked with
> >> before - it's NOT a bridge, unlike VS or VMWare. I'd _start_ by
> >> configuring
> >> without any vlan stuff, make sure you get everything working. If you need
> >> DHCP to the computers that are on the vlan, you'll want to make sure you
> >> have a DHCP server that will be on that same vlan.
> >>
> >> --
> >> Charlie.
> >> http://msmvps.com/blogs/xperts64
> >> http://mvp.support.microsoft.com/profile/charlie.russel
> >>
> >> "Patrick D." <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> > Hi
> >> >
> >> > does that mean, that with an "external network" an hyper-v solution on
> >> > one
> >> > physical server can not communicate with a physical dhcp, which is not
> >> > on
> >> > this physical machine?
> >> >
> >> > Patrick
> >> >
> >> > "Charlie Russel - MVP" wrote:
> >> >
> >> >> Do you have any DHCP server _on that VLAN_? If not, there's no way
> >> >> they'll
> >> >> get an IP address, is there?
> >> >>
> >> >> --
> >> >> Charlie.
> >> >> http://msmvps.com/blogs/xperts64
> >> >> http://mvp.support.microsoft.com/profile/charlie.russel
> >> >>
> >> >> "Patrick D." <(email address - cut out)> wrote in message
> >> >> news:(email address - cut out)...
> >> >> > Hi
> >> >> >
> >> >> > On a full installation of W2k8 Enterprise I have Hyper-V (single
> >> >> > physical
> >> >> > server).
> >> >> > Integration services are installed on all VMs.
> >> >> >
> >> >> > All network-connections in the VMs have "limited or no connectivity"
> >> >> > with
> >> >> > an
> >> >> > IP of 169.x.x.x.
> >> >> > In case of normal connection, the VMs would obtain an IP from a DHCP
> >> >> > Server
> >> >> > in the range of 192.168.x.x
> >> >> > The physical network adapter is on a brand new intel-mainboard
> >> >> > (S5000XVN):
> >> >> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
> >> >> >
> >> >> > I chosed "external network type" in Virtual Network Manager and all
> >> >> > VMs
> >> >> > have
> >> >> > the VLAN ID 1.
> >> >> > What I discovered is, that the physical network adapter does not
> >> >> > show
> >> >> > the
> >> >> > point "VLAN ID" under Device-Manager/Network adapters/Intel
> >> >> > Nic/Properties/Advanced/Property.
> >> >> > Is this the reason, why my VMs have no connection?
> >> >> > Or what is the reason for this isolation of the VMs?
> >> >> >
> >> >> > Thanks for your help.
> >> >> >
> >> >> > Patrick
> >> >>
> >> >>
> >>
> >>
>

Re: Hyper-V networking

Sent: 01/13/2009
From: "Charlie Russel - MVP" <(email address - cut out)>
Message:

The parent (host) really should not use DHCP if your only DHCP server is on
a VM. Far better to simply give it a fixed IP address.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Patrick D." <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Hi
>
> my final solution will only have one dhcp. The sbs 2008 virtualized. Can I
> still put the single physical server hyper-v solution on a external
> network
> in this case?
>
> Patrick
>
> "Bill Grant" wrote:
>
>> Of course. But in that case I would not put it on an external network.
>> I
>> would run the SBS domain on a private virtual network. You can then use
>> DHCP
>> on this network and not interfere with the DHCP service on the physical
>> LAN.
>>
>>
>> "Patrick D." <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Hi Charlie
>> >
>> > well, then I should go away from this test-solution, with external
>> > dhcp.
>> > The
>> > final configuration will have a SBS 2008 (with dhcp) virtually on the
>> > same
>> > vlan like all other servers.
>> > Will this virtual SBS 2008 be able to give an IP to physical clients in
>> > the
>> > same domain?
>> >
>> > Patrick
>> >
>> > "Charlie Russel - MVP" wrote:
>> >
>> >> No, it means that with an external network in hyper-v, the _physical_
>> >> nic
>> >> doesn't have an IP address or run TCP/IP at all. If you set your
>> >> network
>> >> to
>> >> be on a vlan, it doesn't communicate with other computers that aren't
>> >> on
>> >> that vlan.
>> >>
>> >> Hyper-V networking is very different from anything we've worked with
>> >> before - it's NOT a bridge, unlike VS or VMWare. I'd _start_ by
>> >> configuring
>> >> without any vlan stuff, make sure you get everything working. If you
>> >> need
>> >> DHCP to the computers that are on the vlan, you'll want to make sure
>> >> you
>> >> have a DHCP server that will be on that same vlan.
>> >>
>> >> --
>> >> Charlie.
>> >> http://msmvps.com/blogs/xperts64
>> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >>
>> >> "Patrick D." <(email address - cut out)> wrote in message
>> >> news:(email address - cut out)...
>> >> > Hi
>> >> >
>> >> > does that mean, that with an "external network" an hyper-v solution
>> >> > on
>> >> > one
>> >> > physical server can not communicate with a physical dhcp, which is
>> >> > not
>> >> > on
>> >> > this physical machine?
>> >> >
>> >> > Patrick
>> >> >
>> >> > "Charlie Russel - MVP" wrote:
>> >> >
>> >> >> Do you have any DHCP server _on that VLAN_? If not, there's no way
>> >> >> they'll
>> >> >> get an IP address, is there?
>> >> >>
>> >> >> --
>> >> >> Charlie.
>> >> >> http://msmvps.com/blogs/xperts64
>> >> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >> >>
>> >> >> "Patrick D." <(email address - cut out)> wrote in message
>> >> >> news:(email address - cut out)...
>> >> >> > Hi
>> >> >> >
>> >> >> > On a full installation of W2k8 Enterprise I have Hyper-V (single
>> >> >> > physical
>> >> >> > server).
>> >> >> > Integration services are installed on all VMs.
>> >> >> >
>> >> >> > All network-connections in the VMs have "limited or no
>> >> >> > connectivity"
>> >> >> > with
>> >> >> > an
>> >> >> > IP of 169.x.x.x.
>> >> >> > In case of normal connection, the VMs would obtain an IP from a
>> >> >> > DHCP
>> >> >> > Server
>> >> >> > in the range of 192.168.x.x
>> >> >> > The physical network adapter is on a brand new intel-mainboard
>> >> >> > (S5000XVN):
>> >> >> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
>> >> >> >
>> >> >> > I chosed "external network type" in Virtual Network Manager and
>> >> >> > all
>> >> >> > VMs
>> >> >> > have
>> >> >> > the VLAN ID 1.
>> >> >> > What I discovered is, that the physical network adapter does not
>> >> >> > show
>> >> >> > the
>> >> >> > point "VLAN ID" under Device-Manager/Network adapters/Intel
>> >> >> > Nic/Properties/Advanced/Property.
>> >> >> > Is this the reason, why my VMs have no connection?
>> >> >> > Or what is the reason for this isolation of the VMs?
>> >> >> >
>> >> >> > Thanks for your help.
>> >> >> >
>> >> >> > Patrick
>> >> >>
>> >> >>
>> >>
>> >>
>>

Re: Hyper-V networking

Sent: 01/13/2009
From: "Les Connor" <(email address - cut out)>
Message:

I think you'll want your host on a fixed IP, not relying on a DHCP server
running as a guest. Your host should have at least 2 NICs, one reserved for
itself; other(s) for the guest(s).

So, for example:

Edge device lan ip 192.168.0.1 (static)
Host nic one 192.168.0.2 (static)
Host nic two will "host" the hyper-v switch, it won't have an IP (as Charlie
explained), and will be an "external" network. You specify this NIC when you
create the network.
Your SBS guest will have a NIC, and will use the network above - fixed IP
192.168.0.3
SBS will provide DHCP for the 192.168.0.0 network.
Any other machines, physical, or virtual (if connected to the above
"external network") will be served by the SBS DHCP.

--
-----------------------------------------------
Les Connor [SBS MVP]

"Patrick D." <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

Re: Hyper-V networking

Sent: 01/14/2009
From: "Bill Grant" <not.available@online>
Message:

Of course. But in that case I would not put it on an external network. I
would run the SBS domain on a private virtual network. You can then use DHCP
on this network and not interfere with the DHCP service on the physical LAN.

"Patrick D." <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Hi Charlie
>
> well, then I should go away from this test-solution, with external dhcp.
> The
> final configuration will have a SBS 2008 (with dhcp) virtually on the same
> vlan like all other servers.
> Will this virtual SBS 2008 be able to give an IP to physical clients in
> the
> same domain?
>
> Patrick
>
> "Charlie Russel - MVP" wrote:
>
>> No, it means that with an external network in hyper-v, the _physical_ nic
>> doesn't have an IP address or run TCP/IP at all. If you set your network
>> to
>> be on a vlan, it doesn't communicate with other computers that aren't on
>> that vlan.
>>
>> Hyper-V networking is very different from anything we've worked with
>> before - it's NOT a bridge, unlike VS or VMWare. I'd _start_ by
>> configuring
>> without any vlan stuff, make sure you get everything working. If you need
>> DHCP to the computers that are on the vlan, you'll want to make sure you
>> have a DHCP server that will be on that same vlan.
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>> "Patrick D." <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Hi
>> >
>> > does that mean, that with an "external network" an hyper-v solution on
>> > one
>> > physical server can not communicate with a physical dhcp, which is not
>> > on
>> > this physical machine?
>> >
>> > Patrick
>> >
>> > "Charlie Russel - MVP" wrote:
>> >
>> >> Do you have any DHCP server _on that VLAN_? If not, there's no way
>> >> they'll
>> >> get an IP address, is there?
>> >>
>> >> --
>> >> Charlie.
>> >> http://msmvps.com/blogs/xperts64
>> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >>
>> >> "Patrick D." <(email address - cut out)> wrote in message
>> >> news:(email address - cut out)...
>> >> > Hi
>> >> >
>> >> > On a full installation of W2k8 Enterprise I have Hyper-V (single
>> >> > physical
>> >> > server).
>> >> > Integration services are installed on all VMs.
>> >> >
>> >> > All network-connections in the VMs have "limited or no connectivity"
>> >> > with
>> >> > an
>> >> > IP of 169.x.x.x.
>> >> > In case of normal connection, the VMs would obtain an IP from a DHCP
>> >> > Server
>> >> > in the range of 192.168.x.x
>> >> > The physical network adapter is on a brand new intel-mainboard
>> >> > (S5000XVN):
>> >> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
>> >> >
>> >> > I chosed "external network type" in Virtual Network Manager and all
>> >> > VMs
>> >> > have
>> >> > the VLAN ID 1.
>> >> > What I discovered is, that the physical network adapter does not
>> >> > show
>> >> > the
>> >> > point "VLAN ID" under Device-Manager/Network adapters/Intel
>> >> > Nic/Properties/Advanced/Property.
>> >> > Is this the reason, why my VMs have no connection?
>> >> > Or what is the reason for this isolation of the VMs?
>> >> >
>> >> > Thanks for your help.
>> >> >
>> >> > Patrick
>> >>
>> >>
>>
>>

Re: Hyper-V networking

Sent: 01/14/2009
From: "Bill Grant" <not.available@online>
Message:

As long as you realize that all machines on the physical network will see
the DHCP service running on the SBS server.

"Patrick D." <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: