Is SSH working and is everything being processed by vcld to the point where you see the Connect button on the web page? If you are just manually running the scripts then RDP won't be available because the firewall port isn't open. vcld opens it later on in the process.

I have not seen the error before in the output from IP config called from configure_networking.vbs:
"An internal error occurred: The file name is too long."

I'm wondering if a problem occurred obtaining the IP address. Can you run "ipconfig /all" manually and does this error show up? If SSH is working correctly on the private interface, then I'm guessing there is a routing table problem. There are no 129.x entries. This seems odd. Do any entries appear for 129.x in the routing table it you run "ipconfig /renew", then "route print"?

If vcld is completely loading the computer, then the problems that occur in configure_networking.vbs may not be the problem. The output from the log file where "set_public_default_route" is called will be helpful. The .vbs script attempts to set default routes but the vcld code does this again later on.

-Andy


______________
configure_networking.vbs beginning to run: 3/23/2010 12:53:50 PM
Windows Version: 5.1.2600
---------------------------------------------------------------------------
12:54:26 PM
---------------------------------------------------------------------------
Printing routing table, command: cmd.exe /c %SystemRoot%\system32\route.exe 
print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 56 00 00 00 ...... AMD PCNET Family PCI Ethernet Adapter #3 - 
Packet Scheduler Miniport
0x10004 ...00 50 56 00 00 01 ...... AMD PCNET Family PCI Ethernet Adapter #4 - 
Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1     192.168.1.1       30
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      169.254.0.0      255.255.0.0  169.254.237.166  169.254.237.166      30
  169.254.237.166  255.255.255.255        127.0.0.1       127.0.0.1       30
  169.254.255.255  255.255.255.255  169.254.237.166  169.254.237.166      30
      192.168.0.0      255.255.0.0      192.168.1.1     192.168.1.1       30
      192.168.1.1  255.255.255.255        127.0.0.1       127.0.0.1       30
    192.168.1.255  255.255.255.255      192.168.1.1     192.168.1.1       30
        224.0.0.0        240.0.0.0  169.254.237.166  169.254.237.166      30
        224.0.0.0        240.0.0.0      192.168.1.1     192.168.1.1       30
  255.255.255.255  255.255.255.255  169.254.237.166  169.254.237.166      1
  255.255.255.255  255.255.255.255      192.168.1.1     192.168.1.1       1
Default Gateway:       192.168.0.1
===========================================================================
Persistent Routes:
  None
Printing routing table successful, exit code: 0
12:54:27 PM
---------------------------------------------------------------------------
12:54:27 PM
---------------------------------------------------------------------------
Running ipconfig /all, command: cmd.exe /c %SystemRoot%\system32\ipconfig.exe 
/all

Windows IP Configuration

An internal error occurred: The file name is too long.

Please contact Microsoft Product Support Services for further help.

Additional information: Unable to query host name.

Running ipconfig /all successful, exit code: 0
12:54:28 PM
----------------------------------------------------------------------
*** AMD PCNET Family PCI Ethernet Adapter (Index: 1) ***

Adpater name: AMD PCNET Family PCI Ethernet Adapter
Ignored adpater name section: Ignored adpater description section: IP address: 129.128.9.119 Matching VCL private address section: Matching non-public address section: * PUBLIC_NAME = Local Area Connection
* DHCP enabled         = True
* PUBLIC_IP            = 129.128.9.119
* PUBLIC_SUBNET_MASK   = 255.255.254.0
* PUBLIC_GATEWAY = * PUBLIC_DESCRIPTION = AMD PCNET Family PCI Ethernet Adapter
----------------------------------------------------------------------
*** AMD PCNET Family PCI Ethernet Adapter (Index: 4) ***

Adpater name: AMD PCNET Family PCI Ethernet Adapter
Ignored adpater name section: Ignored adpater description section: IP address: 192.168.1.1 Matching VCL private address section: Matching non-public address section: 192.168
IP address is not a public nor valid VCL private address: 192.168.1.1
---------------------------------------------------------------------------
12:54:29 PM
---------------------------------------------------------------------------
PRIVATE_NAME = PRIVATE_IP = PRIVATE_SUBNET_MASK = PRIVATE_GATEWAY =
PUBLIC_NAME           = Local Area Connection
PUBLIC_IP             = 129.128.9.119
PUBLIC_SUBNET_MASK    = 255.255.254.0
PUBLIC_GATEWAY =
Failed to retrieve private and public network configuration, returning exit 
status 1
_________________


Which looks bad to me.  Poking around a bit, it seems that 
configure_networking.vbs expects my private lan to be 10.x.x.x, but I've got it 
as 192.168.x.x, as per other documentation.  Is this relevant?

To summarize this round of glitch-squishing, the sysprep_cmdlines.cmd issue, 
with the symptom of the failure to autologin after running sysprep, seems to be 
solved, or at least worked around, by the pre-creation of the Logs folder.  But 
the inability to connect via RDC after the reservation is made persists, which 
may be due to something going wrong with the configure_networking.vbs script.

Back to you, Andy (with continued gratefulness for your help).

Terry

Reply via email to