Hello Mike,

Thank you for replying..

I can see that i had a type error, i am sorry and you are right.

I am running 3.0.6 PATCH, a,b,c,d

But i am testing some other thing now.

I have tested that if i wait app. 10-15 min. the vrouter updates and i can connect to the internet..?
I just need to do a couple of more tests, i will write back if it look like that is the issue..

Kind regards
Gert

Hello Oded,

Yes, thank you - lol.

But now i have figured it out.

I the instllation manual it states that i should change:
net.bridge.bridge-nf-call-iptables = 1
net.bridge.bridge-nf-call-arptables = 1

but i think that is wrong, when that is configured it does not Work, i can not communicate between the VMs, and vrouter if they are on different servers.

Kind regards
Gert

I've ran into a similar problem before. In my experience if the Router VM is destroyed and re-create it'll have a new IP. While that won't prevent the instance from acquiring an IP address (DHCP discovery happens via broadcast) the DHCP lease does include an IP address of a DNS server, the old Router VM's IP. Below I look at what you've reported and try to corollate each line of what you said to a problem with DNS.

==============================================================
i create a domain, and a account.
I create a network, and a Windows instance
this Works....

At this point, the Router VM is up, assigned a DHCP lease to the new instance you just created

Then i shot Down the router, now when i start the router and the instance it does not Work.-

When you say the instance didn't work, how exactly did you test this out? If you're using the sysvm router for a DNS server and you did anything which involved resolving a hostname after deleting the sysvm router you'll fail to resolve the hostname/domain*. *In my experience when the sysvm router comes up again, it'll have a new IP, which means the IP address which was being served as a DNS server via DHCP leases won't be rechable anymore and any previously created instances won't be able to resolve domains. I understand you say further below you're unable to ping however are you trying to ping a hostname or an IP? Even if you were trying to ping an IP, might the inability to ping an IP be related to your networking setup as opposed to something with that particular instance?

i can delete the instance and the router create the instance and the router then it Works Again ???

Assuming the sysvm router was created before you created the new instance, it makes sense tha this would of worked. The sysvm router was up and running and the DNS Server IP address the new instance would of acquired would of been that of a valid sysvm router.

Thay are running on the same server, when they does not Work...

what does not Work, i i can not ping/browse the internet, i still get my IP.

hello erikgo,

Thank you for the reply, but my CP environment is running great now.
It was the two lines, that exits in Citrix Cloud Platform Installation manual.

Kind regards
Gert