Topic: dhcp

[crazybob]

I am hoping some one can explain the why to the following observation.

I built a new SME 7.3 server in server/gateway mode, and applied all the updates.
I gave it an ip, and told it to use dhcp, but did not attach anything to eth0
I made the adjustments to server manager to allow myself to connect to the server through what would normally be the wan port
I then installed vmware server
In vmware server I installed W2K Server.
I discovered I could not aquire an ip in the w2kserver.

After a couple of days of contemplating doing sever damage to my liver, I discovered things work properly only when I connect a computer to eth0.

I would not have discovered this in normal operation, but I am building this in an attempt to reduce the amount of configuration after installation.

I don't think it is really a bug, just something odd, and would like a little insight as to the why.

Thanks

Bob

[David Harper]

I'm not sure what the cause would be, but I have a question. For the client in VMWare Server, do you use NAT or a bridged adaptor?

[crazybob]

bridged

[David Harper]

Perhaps SME Server has some restriction on WAN connections having more than one address?

[CharlieBrady]

I then installed vmware server
In vmware server I installed W2K Server.
I discovered I could not aquire an ip in the w2kserver.

This sounds like it's an issue with vmware server or w2kserver, and perhaps has nothing to do with SME server.

... doing sever damage to my liver ...

You were going to cut it off ("sever it")?

[mmccarn]

A couple ideas:
I have a couple SME servers that will not even detect the ethernet adapters unless they are connected to something during bootup.

That is, if I boot up with nothing connected to the WAN port, I cannot connect to the wan without rebooting.

I have chalked this up to something in the drivers for the NICs in question, and just make sure I have network cables attached when I boot up.


I have another system that is a win2003 host running VMWare that failed miserably when a recent Windows 2003 service pack was released - the new Service Pack enabled "TCP Offloading" by default, which left me with a virtual system that could not talk to the host system.  Both the host and the vmware client could talk to the internet or to any other system on my network, but they could not talk to each other...

[crazybob]

Charlie, I have spelling problems at times. Severe was what I was after

mmccarn, thanks for letting me know that I am not the only one that has seen something like this.


Bob